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

Luca Tagliani updated MCHANGES-288:
-----------------------------------

    Attachment: jiraPreserveContextLogin.patch

Adding a patch to preserve the context of the Jira installation
                
> JIRA url not fully respected
> ----------------------------
>
>                 Key: MCHANGES-288
>                 URL: https://jira.codehaus.org/browse/MCHANGES-288
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: jira
>    Affects Versions: 2.8
>         Environment: OS XP, maven 3.0.4
>            Reporter: Bruno Marti
>         Attachments: jiraPreserveContextLogin.patch
>
>
> Issue url is not fully used by maven-changes-plugin:2.8
> have following issue url:
> {quote}
> <issueManagement>
>     <system>JIRA</system>
>     <url>https://my.ch/prod/jira/?pid=10000</url>
> </issueManagement>
> {quote}
> with changes-plugin:2.7.1 works well:
> {quote}
> [INFO] Generating "JIRA Report" report    --- maven-changes-plugin:2.7.1
> [DEBUG] JIRA lives at: https://my.ch/prod/jira
> [DEBUG] Login URL: 
> https://my.ch/prod/jira/login.jsp?os_destination=/secure/&os_username=*****&os_password=*****
> [DEBUG] Successfully logged in into JIRA.
> {quote}
> BUT with changes-plugin:2.8, got error:
> {quote}
> [INFO] Generating "JIRA Report" report    --- maven-changes-plugin:2.8
> [DEBUG] JIRA lives at: https://my.ch
> [DEBUG] Login URL: 
> https://my.ch/login.jsp?os_destination=/secure/&os_username=*****&os_password=*****
> [ERROR] Error trying to login into JIRA.
> java.net.SocketException: Connection reset
> {quote}
> Problem is, that the additional context */prod/jira/* gets lost.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to