Maven 2.x Changes Plugin

the generated jira-result.xml contains no jira-items

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Cannot Reproduce
  • Affects Version/s: 2.0-beta-3
  • Fix Version/s: None
  • Component/s: jira
  • Labels:
    None
  • Environment:
    windows maven-2.0.8 jira Professional Edition, Version: 3.11-#288
  • Number of attachments :
    6

Description

when i run the maven site or mvn changes:jira-report the resulting jira-reports doesnot contain jira-issues it only contains the link to the searchrequest.

This results in an empty jira-report.

I have included the jira-reports.xml and the logging from the mvn changes:jira report.

When open the jira-reports.xml in firefox i do have a page with the request jira-issues available. In explorer i just get the representation of the xml file.

Any suggestions why no jira-report is generated.

Attachments

  1. HTML File
    jira-report.html
    18/Mar/08 10:50 AM
    2 kB
    Rene Boers
  2. Text File
    jira-report.log
    20/Mar/08 5:07 AM
    40 kB
    Rene Boers
  3. XML File
    jira-results.xml
    18/Mar/08 10:47 AM
    0.7 kB
    Rene Boers
  4. XML File
    jira-results.xml
    18/Mar/08 10:47 AM
    0.7 kB
    Rene Boers
  5. XML File
    pom.xml
    18/Mar/08 10:47 AM
    6 kB
    Rene Boers
  1. screenshot-1.jpg
    273 kB
    18/Mar/08 10:56 AM

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Rene Boers added a comment -

the empty generated report

Show
Rene Boers added a comment - the empty generated report
Hide
Permalink
Rene Boers added a comment -

This is the result when the link in the jira-reports is entered in the browser. The result is the expected list of closed issues.

Show
Rene Boers added a comment - This is the result when the link in the jira-reports is entered in the browser. The result is the expected list of closed issues.
Hide
Permalink
Dennis Lundberg added a comment -

You didn't include the logging output.

Show
Dennis Lundberg added a comment - You didn't include the logging output.
Hide
Permalink
Rene Boers added a comment -

here the requested output logfile.

Show
Rene Boers added a comment - here the requested output logfile.
Hide
Permalink
Dennis Lundberg added a comment -

There is an xml error in your pom. You should remove the text "</developers>".

Are the usernam/password for a proxy or for the webapp server that runs JIRA?
Do you have anonymous access to JIRA?

Show
Dennis Lundberg added a comment - There is an xml error in your pom. You should remove the text "</developers>". Are the usernam/password for a proxy or for the webapp server that runs JIRA? Do you have anonymous access to JIRA?
Hide
Permalink
Steven De Schepper added a comment -

I'm facing a similar problem:

The pom file has a valid configuration for the proxy and the username/password for the JIRA server are passed using the <webUser> and <webPassword> tags.
I launch the mvn command to generate the reports using the -X flag, to produce debug output and thus the URL the plugin creates for downloading from JIRA.
When I copy/paste the URL in FireFox, the issues that match the filter are visible, but the generated jira-results.xml is empty (and the report page is blank).

Show
Steven De Schepper added a comment - I'm facing a similar problem: The pom file has a valid configuration for the proxy and the username/password for the JIRA server are passed using the <webUser> and <webPassword> tags. I launch the mvn command to generate the reports using the -X flag, to produce debug output and thus the URL the plugin creates for downloading from JIRA. When I copy/paste the URL in FireFox, the issues that match the filter are visible, but the generated jira-results.xml is empty (and the report page is blank).
Hide
Permalink
darren hartford added a comment -

ok, I'm not crazy....

Running into exact same problem, Maven 2.0.9, Fedora 9, Maven Changes Plugin 2.0, and JIRA 3.12.2-#300.

going to the link from the debug shows a list off issues, but jira-results.xml only shows the rss/channel block and no issues.

force/verify maven changes plugin 2.0
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>2.0</version>
</plugin>
</plugins>
</pluginManagement>

Running with -X, it's using:

doxia 1.0-alpha-9
plexux-utils-1.4.5
plexus-velocity 1.1.7
velocity 1.4

Show
darren hartford added a comment - ok, I'm not crazy.... Running into exact same problem, Maven 2.0.9, Fedora 9, Maven Changes Plugin 2.0, and JIRA 3.12.2-#300. going to the link from the debug shows a list off issues, but jira-results.xml only shows the rss/channel block and no issues. force/verify maven changes plugin 2.0 <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-changes-plugin</artifactId> <version>2.0</version> </plugin> </plugins> </pluginManagement> Running with -X, it's using: doxia 1.0-alpha-9 plexux-utils-1.4.5 plexus-velocity 1.1.7 velocity 1.4
Hide
Permalink
Mark Derricutt added a comment -

This sounds like the same problem I was just noticing. However, one thing I noticed is that the <jiraUser/> and <jiraPassword/> settings never seem to get passed onto the JiraDownloader instance, so the os_username/os_password URL parameters are never added to the request, so no issues get returned.

I also notice the URL used gets redirected by jira to http://jira-server/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid\x3d10150\x26resolution\x3d1\x26sorter/field\x3dissuekey\x26sorter/order\x3dDESC\x26tempMax\x3d1000 or something equally disgusting. Adding the os_username params to this URL returns issues, but seems to return more issues than desired.

Show
Mark Derricutt added a comment - This sounds like the same problem I was just noticing. However, one thing I noticed is that the <jiraUser/> and <jiraPassword/> settings never seem to get passed onto the JiraDownloader instance, so the os_username/os_password URL parameters are never added to the request, so no issues get returned. I also notice the URL used gets redirected by jira to http://jira-server/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid\x3d10150\x26resolution\x3d1\x26sorter/field\x3dissuekey\x26sorter/order\x3dDESC\x26tempMax\x3d1000 or something equally disgusting. Adding the os_username params to this URL returns issues, but seems to return more issues than desired.
Hide
Permalink
Christophe Lallement added a comment -

I confirm we have the same problem.

The JIRA url dump on the log is
[INFO] Downloading from JIRA at: https://xxxx/jira/secure/IssueNavigator.jspa?view=rss&pid=10236&statusIds=6&resolutionIds=1&tempMax=25&reset=true&decorator=none

this request return an empty list of release/issue. Te same think when i make this request into a browser (with authentication or not)

we use JIRA Version: 3.12.1-#299

Regards

Show
Christophe Lallement added a comment - I confirm we have the same problem. The JIRA url dump on the log is [INFO] Downloading from JIRA at: https://xxxx/jira/secure/IssueNavigator.jspa?view=rss&pid=10236&statusIds=6&resolutionIds=1&tempMax=25&reset=true&decorator=none this request return an empty list of release/issue. Te same think when i make this request into a browser (with authentication or not) we use JIRA Version: 3.12.1-#299 Regards
Hide
Permalink
Dennis Lundberg added a comment -

Is this still an issue with versions 2.1 and 2.2 of the plugin?

If so, then please paste your plugin configuration here, along with a debug log file.

Show
Dennis Lundberg added a comment - Is this still an issue with versions 2.1 and 2.2 of the plugin? If so, then please paste your plugin configuration here, along with a debug log file.
Hide
Permalink
Krashan Brahmanjara added a comment -

I see the same problem connecting over https - maven log shows correct url and download status 'successfull'.
Url pasted to firefox get correct answer but file jira-results.xml is empty with fake <link section>.

Log
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-changes-plugin:2.3:jira-report' -->
[DEBUG] (f) columnNames = Key,Summary,Status,Resolution,Assignee
[DEBUG] (f) jiraPassword = ...
[DEBUG] (f) jiraUser = ...
[DEBUG] (f) jiraXmlPath = ...\target\jira-results.xml
[DEBUG] (f) localRepository = Repository[local|file://..\apache-maven-2.2.1\.m2\repository]
[DEBUG] (f) maxEntries = 100
[DEBUG] (f) onlyCurrentVersion = false
[DEBUG] (f) outputDirectory = D:\...\target\site
[DEBUG] (f) project = MavenProject: p...:0.1-SNAPSHOT @ ...\pom.xml
[DEBUG] (f) resolutionIds = Fixed
[DEBUG] (f) settings = org.apache.maven.settings.Settings@162d950
[DEBUG] (f) sortColumnNames = Priority DESC, Created DESC
[DEBUG] (f) statusIds = Closed
[DEBUG] – end configuration –
[INFO] [changes:jira-report {execution: default-cli}]
[DEBUG] maven-default-skin: resolved to version 1.0 from repository central
[DEBUG] JIRA lives at: https://jira.....pl
[DEBUG] Login URL: https://jira.....pl/login.jsp?os_destination=/secure/&os_username=...&os_password=*****************
[DEBUG] Successfully logged in into JIRA.
[DEBUG] download jira issues from url https://jira.....pl/secure/IssueNavigator.jspa?view=rss&pid=10080&statusIds=6&resolutionIds=1&sorter/fiel
d=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none
[INFO] Downloading from JIRA at: https://jira....pl/secure/IssueNavigator.jspa?view=rss&pid=10080&statusIds=6&resolutionIds=1&sorter/field=cre
ated&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none
2010-06-18 10:24:06 org.apache.commons.httpclient.HttpMethodBase getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

Show
Krashan Brahmanjara added a comment - I see the same problem connecting over https - maven log shows correct url and download status 'successfull'. Url pasted to firefox get correct answer but file jira-results.xml is empty with fake <link section>. Log [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-changes-plugin:2.3:jira-report' --> [DEBUG] (f) columnNames = Key,Summary,Status,Resolution,Assignee [DEBUG] (f) jiraPassword = ... [DEBUG] (f) jiraUser = ... [DEBUG] (f) jiraXmlPath = ...\target\jira-results.xml [DEBUG] (f) localRepository = Repository[local|file://..\apache-maven-2.2.1\.m2\repository] [DEBUG] (f) maxEntries = 100 [DEBUG] (f) onlyCurrentVersion = false [DEBUG] (f) outputDirectory = D:\...\target\site [DEBUG] (f) project = MavenProject: p...:0.1-SNAPSHOT @ ...\pom.xml [DEBUG] (f) resolutionIds = Fixed [DEBUG] (f) settings = org.apache.maven.settings.Settings@162d950 [DEBUG] (f) sortColumnNames = Priority DESC, Created DESC [DEBUG] (f) statusIds = Closed [DEBUG] – end configuration – [INFO] [changes:jira-report {execution: default-cli}] [DEBUG] maven-default-skin: resolved to version 1.0 from repository central [DEBUG] JIRA lives at: https://jira.....pl [DEBUG] Login URL: https://jira.....pl/login.jsp?os_destination=/secure/&os_username=...&os_password=***************** [DEBUG] Successfully logged in into JIRA. [DEBUG] download jira issues from url https://jira.....pl/secure/IssueNavigator.jspa?view=rss&pid=10080&statusIds=6&resolutionIds=1&sorter/fiel d=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none [INFO] Downloading from JIRA at: https://jira....pl/secure/IssueNavigator.jspa?view=rss&pid=10080&statusIds=6&resolutionIds=1&sorter/field=cre ated&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none 2010-06-18 10:24:06 org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
Hide
Permalink
Edgar Vonk added a comment -

We have the same issue (https, JIRA 3.13) but our workaround is to specify a filter section in the plugin as described here: http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html.

With the filter it does work. It seems the default filter does not for us and if I am not mistaken it has something to do with the 'statusIds=6' parameter in the generated JIRA URL.

Show
Edgar Vonk added a comment - We have the same issue (https, JIRA 3.13) but our workaround is to specify a filter section in the plugin as described here: http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html. With the filter it does work. It seems the default filter does not for us and if I am not mistaken it has something to do with the 'statusIds=6' parameter in the generated JIRA URL.
Hide
Permalink
Dennis Lundberg added a comment -

Edgar, the "statusIds=6" part of the URL is there to make sure that only issues that have been "Closed" in JIRA will be returned. Do you have any "Closed" issues for the current version?

Show
Dennis Lundberg added a comment - Edgar, the "statusIds=6" part of the URL is there to make sure that only issues that have been "Closed" in JIRA will be returned. Do you have any "Closed" issues for the current version?
Hide
Permalink
Dennis Lundberg added a comment -

I am unable to reproduce this issue. I have tried on two secured installations; JIRA 3.13 over http and on JIRA 3.12 over https, using Maven Changes Plugin 2.3. Both of them using <jiraUser> and <jiraPassword>. No proxy is used and no Basic Authentication (i.e. <webUser>/<webPassword>) is used on the web server.

If someone is still having problems like these, please open a new issue for it. Be sure to include the complete plugin and issue management configuration from the POM, as well as a debug output log file running 'mvn changes:jira-report -X'. If you are using a proxy you need to tell us that too.

Show
Dennis Lundberg added a comment - I am unable to reproduce this issue. I have tried on two secured installations; JIRA 3.13 over http and on JIRA 3.12 over https, using Maven Changes Plugin 2.3. Both of them using <jiraUser> and <jiraPassword>. No proxy is used and no Basic Authentication (i.e. <webUser>/<webPassword>) is used on the web server. If someone is still having problems like these, please open a new issue for it. Be sure to include the complete plugin and issue management configuration from the POM, as well as a debug output log file running 'mvn changes:jira-report -X'. If you are using a proxy you need to tell us that too.

People

Vote (6)
Watch (7)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.