[ 
https://issues.apache.org/jira/browse/MCHANGES-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Fox updated MCHANGES-385:
------------------------------
    Environment: 
OS: Mac
Maven: 3.5.2
Java: 1.8
maven-changes-plugin: 2.12.1
    Description: 
If the issueManagement URL is defined as a JQL query the changes plugin fails 
with
{code:java}
10:24:52 [INFO] Generating "JIRA Report" report --- 
maven-changes-plugin:2.12.1:jira-report
10:24:52 [WARNING]
10:24:52 java.lang.IllegalArgumentException: Invalid browse URL
10:24:52 at org.apache.maven.plugin.jira.JiraHelper.getJiraUrlAndProjectName 
(JiraHelper.java:229)
10:24:52 at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute 
(RestJiraDownloader.java:115)
10:24:52 at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute 
(AdaptiveJiraDownloader.java:45)
10:24:52 at org.apache.maven.plugin.jira.JiraMojo.executeReport 
(JiraMojo.java:346){code}

Example IssueManagement
{code:xml}
<issueManagement>
    <system>JIRA</system>    
    
<url>https://issues.apache.org/jira/issues/?jql=component%20%3D%20changes.xml</url>
</issueManagement>
{code}

In our projects a maven artifact correlates to a JIRA component so for an 
individual issueManagement site URL we want to be able to see all of the issues 
tied to that component. This is only an issue if the jira report is used for 
the changes report this works without issue.

  was:
If the issueManagement URL is defined as a JQL query the changes plugin fails 
with
{code:java}
10:24:52 [INFO] Generating "JIRA Report" report --- 
maven-changes-plugin:2.12.1:jira-report
10:24:52 [WARNING]
10:24:52 java.lang.IllegalArgumentException: Invalid browse URL
10:24:52 at org.apache.maven.plugin.jira.JiraHelper.getJiraUrlAndProjectName 
(JiraHelper.java:229)
10:24:52 at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute 
(RestJiraDownloader.java:115)
10:24:52 at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute 
(AdaptiveJiraDownloader.java:45)
10:24:52 at org.apache.maven.plugin.jira.JiraMojo.executeReport 
(JiraMojo.java:346){code}

Example IssueManagement
{code:xml}
<issueManagement>
    <system>JIRA</system>    
    
<url>https://issues.apache.org/jira/issues/?jql=component%20%3D%20changes.xml</url>
</issueManagement>
{code}

In our projects a maven artifact correlates to a JIRA component so for an 
individual issueManagement site URL we want to be able to see all of the issues 
tied to that component.


> JIRA Report for Changes plugin Invalid browse URL for issueManagement
> ---------------------------------------------------------------------
>
>                 Key: MCHANGES-385
>                 URL: https://issues.apache.org/jira/browse/MCHANGES-385
>             Project: Maven Changes Plugin
>          Issue Type: Bug
>    Affects Versions: 2.12.1
>         Environment: OS: Mac
> Maven: 3.5.2
> Java: 1.8
> maven-changes-plugin: 2.12.1
>            Reporter: John Fox
>            Priority: Minor
>
> If the issueManagement URL is defined as a JQL query the changes plugin fails 
> with
> {code:java}
> 10:24:52 [INFO] Generating "JIRA Report" report --- 
> maven-changes-plugin:2.12.1:jira-report
> 10:24:52 [WARNING]
> 10:24:52 java.lang.IllegalArgumentException: Invalid browse URL
> 10:24:52 at org.apache.maven.plugin.jira.JiraHelper.getJiraUrlAndProjectName 
> (JiraHelper.java:229)
> 10:24:52 at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute 
> (RestJiraDownloader.java:115)
> 10:24:52 at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute 
> (AdaptiveJiraDownloader.java:45)
> 10:24:52 at org.apache.maven.plugin.jira.JiraMojo.executeReport 
> (JiraMojo.java:346){code}
> Example IssueManagement
> {code:xml}
> <issueManagement>
>     <system>JIRA</system>    
>     
> <url>https://issues.apache.org/jira/issues/?jql=component%20%3D%20changes.xml</url>
> </issueManagement>
> {code}
> In our projects a maven artifact correlates to a JIRA component so for an 
> individual issueManagement site URL we want to be able to see all of the 
> issues tied to that component. This is only an issue if the jira report is 
> used for the changes report this works without issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to