You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andrew Murdoch (JIRA)" <ji...@codehaus.org> on 2012/10/09 19:15:38 UTC
[jira] (MCHANGES-292) announcement-mail goal doesn't respect useJql
parameter
Andrew Murdoch created MCHANGES-292:
---------------------------------------
Summary: announcement-mail goal doesn't respect useJql parameter
Key: MCHANGES-292
URL: https://jira.codehaus.org/browse/MCHANGES-292
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Reporter: Andrew Murdoch
When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
Resulting error
[ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Example configuration which causes the issue
<useJql>true</useJql>
<jiraUser>jirauserjiraUser>
<jiraPassword>jirapwd</jiraPassword>
<onlyCurrentVersion>true</onlyCurrentVersion>
<toAddresses>
<toAddress>address@domain.com</toAddress>
</toAddresses>
<smtpHost>hostname</smtpHost>
<smtpPort implementation="java.lang.Integer">25</smtpPort>
<issueManagementSystems>
<issueManagementSystem>JIRA</issueManagementSystem>
</issueManagementSystems>
--
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
[jira] (MCHANGES-292) announcement-mail goal doesn't respect useJql
parameter
Posted by "Luca Tagliani (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luca Tagliani updated MCHANGES-292:
-----------------------------------
Attachment: jiraCreateAnnounceJql.patch
Attaching a proposed patch for enabling jql in announcement-generate
> announcement-mail goal doesn't respect useJql parameter
> -------------------------------------------------------
>
> Key: MCHANGES-292
> URL: https://jira.codehaus.org/browse/MCHANGES-292
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Reporter: Andrew Murdoch
> Attachments: jiraCreateAnnounceJql.patch
>
>
> When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
> Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
> Resulting error
> {noformat}
> [ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
> java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {noformat}
> Example configuration which causes the issue
> {code:xml}
> <useJql>true</useJql>
> <jiraUser>jirauserjiraUser>
> <jiraPassword>jirapwd</jiraPassword>
> <onlyCurrentVersion>true</onlyCurrentVersion>
> <toAddresses>
> <toAddress>address@domain.com</toAddress>
> </toAddresses>
> <smtpHost>hostname</smtpHost>
> <smtpPort implementation="java.lang.Integer">25</smtpPort>
> <issueManagementSystems>
> <issueManagementSystem>JIRA</issueManagementSystem>
> </issueManagementSystems>
> {code}
--
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
[jira] (MCHANGES-292) announcement-mail goal doesn't respect useJql
parameter
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-292:
-------------------------------------
Component/s: jira
announcement
> announcement-mail goal doesn't respect useJql parameter
> -------------------------------------------------------
>
> Key: MCHANGES-292
> URL: https://jira.codehaus.org/browse/MCHANGES-292
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: announcement, jira
> Reporter: Andrew Murdoch
> Attachments: jiraCreateAnnounceJql.patch
>
>
> When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
> Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
> Resulting error
> {noformat}
> [ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
> java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {noformat}
> Example configuration which causes the issue
> {code:xml}
> <useJql>true</useJql>
> <jiraUser>jirauserjiraUser>
> <jiraPassword>jirapwd</jiraPassword>
> <onlyCurrentVersion>true</onlyCurrentVersion>
> <toAddresses>
> <toAddress>address@domain.com</toAddress>
> </toAddresses>
> <smtpHost>hostname</smtpHost>
> <smtpPort implementation="java.lang.Integer">25</smtpPort>
> <issueManagementSystems>
> <issueManagementSystem>JIRA</issueManagementSystem>
> </issueManagementSystems>
> {code}
--
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
[jira] (MCHANGES-292) announcement-mail goal doesn't respect useJql
parameter
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-292:
-------------------------------------
Issue Type: New Feature (was: Bug)
> announcement-mail goal doesn't respect useJql parameter
> -------------------------------------------------------
>
> Key: MCHANGES-292
> URL: https://jira.codehaus.org/browse/MCHANGES-292
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Reporter: Andrew Murdoch
>
> When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
> Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
> Resulting error
> {noformat}
> [ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
> java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {noformat}
> Example configuration which causes the issue
> {code:xml}
> <useJql>true</useJql>
> <jiraUser>jirauserjiraUser>
> <jiraPassword>jirapwd</jiraPassword>
> <onlyCurrentVersion>true</onlyCurrentVersion>
> <toAddresses>
> <toAddress>address@domain.com</toAddress>
> </toAddresses>
> <smtpHost>hostname</smtpHost>
> <smtpPort implementation="java.lang.Integer">25</smtpPort>
> <issueManagementSystems>
> <issueManagementSystem>JIRA</issueManagementSystem>
> </issueManagementSystems>
> {code}
--
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
[jira] (MCHANGES-292) announcement-mail goal doesn't respect useJql
parameter
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311158#comment-311158 ]
Dennis Lundberg commented on MCHANGES-292:
------------------------------------------
Hi
I think that you mean the {{changes:announcement-generate}} goal. All the {{changes:announcement-mail}} goal does is send an email based on a previously generated template.
The {{changes:announcement-generate}} goal does not yet support the {{useJql parameter}}, as can be seen in the plugin documentation:
http://maven.apache.org/plugins/maven-changes-plugin/announcement-generate-mojo.html
> announcement-mail goal doesn't respect useJql parameter
> -------------------------------------------------------
>
> Key: MCHANGES-292
> URL: https://jira.codehaus.org/browse/MCHANGES-292
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Reporter: Andrew Murdoch
>
> When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
> Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
> Resulting error
> {noformat}
> [ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
> java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {noformat}
> Example configuration which causes the issue
> {code:xml}
> <useJql>true</useJql>
> <jiraUser>jirauserjiraUser>
> <jiraPassword>jirapwd</jiraPassword>
> <onlyCurrentVersion>true</onlyCurrentVersion>
> <toAddresses>
> <toAddress>address@domain.com</toAddress>
> </toAddresses>
> <smtpHost>hostname</smtpHost>
> <smtpPort implementation="java.lang.Integer">25</smtpPort>
> <issueManagementSystems>
> <issueManagementSystem>JIRA</issueManagementSystem>
> </issueManagementSystems>
> {code}
--
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
[jira] (MCHANGES-292) announcement-mail goal doesn't respect useJql
parameter
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-292:
-------------------------------------
Description:
When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
Resulting error
{noformat}
[ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
{noformat}
Example configuration which causes the issue
{code:xml}
<useJql>true</useJql>
<jiraUser>jirauserjiraUser>
<jiraPassword>jirapwd</jiraPassword>
<onlyCurrentVersion>true</onlyCurrentVersion>
<toAddresses>
<toAddress>address@domain.com</toAddress>
</toAddresses>
<smtpHost>hostname</smtpHost>
<smtpPort implementation="java.lang.Integer">25</smtpPort>
<issueManagementSystems>
<issueManagementSystem>JIRA</issueManagementSystem>
</issueManagementSystems>
{code}
was:
When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
Resulting error
[ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Example configuration which causes the issue
<useJql>true</useJql>
<jiraUser>jirauserjiraUser>
<jiraPassword>jirapwd</jiraPassword>
<onlyCurrentVersion>true</onlyCurrentVersion>
<toAddresses>
<toAddress>address@domain.com</toAddress>
</toAddresses>
<smtpHost>hostname</smtpHost>
<smtpPort implementation="java.lang.Integer">25</smtpPort>
<issueManagementSystems>
<issueManagementSystem>JIRA</issueManagementSystem>
</issueManagementSystems>
> announcement-mail goal doesn't respect useJql parameter
> -------------------------------------------------------
>
> Key: MCHANGES-292
> URL: https://jira.codehaus.org/browse/MCHANGES-292
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Reporter: Andrew Murdoch
>
> When configured with the useJql parameter such that the changes plugin is able to pull a report from JIRA version 5.1 the announcement-mail goal does not appear to respect this.
> Executing the goal 'jira-report' generates the correct URL and produces the report successfully, however executing the goal 'announcement-mail' fails as if useJql is not specified. This may also be true for jiraUser and jiraPassword but it cant get that far due to the useJql error.
> Resulting error
> {noformat}
> [ERROR] Error accessing http://jira.hostname.com/browse/PROJECTID
> java.lang.RuntimeException: The issue management URL in the POM does not include a pid, and it was not possible to extract it from the page at that URL.
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:238)
> at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:147)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.getJiraReleases(AnnouncementMojo.java:682)
> at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:454)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {noformat}
> Example configuration which causes the issue
> {code:xml}
> <useJql>true</useJql>
> <jiraUser>jirauserjiraUser>
> <jiraPassword>jirapwd</jiraPassword>
> <onlyCurrentVersion>true</onlyCurrentVersion>
> <toAddresses>
> <toAddress>address@domain.com</toAddress>
> </toAddresses>
> <smtpHost>hostname</smtpHost>
> <smtpPort implementation="java.lang.Integer">25</smtpPort>
> <issueManagementSystems>
> <issueManagementSystem>JIRA</issueManagementSystem>
> </issueManagementSystems>
> {code}
--
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