[
https://jira.codehaus.org/browse/MCHANGES-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361137#comment-361137
]
Thomas Scheffler commented on MCHANGES-333:
-------------------------------------------
I noticed the same behaviour. We switched from SourceForge to JIRA and therefor
from changes.xml to JIRA, too. But I cannot get the announcement to work. Here
are some numbers:
- Issues count: *667*
- Issues fixed in the current release: *2*
- Issues fetched from JIRA to accidentally get the current release name: *25*
- Fields fetched to get the fixVersion field: *all*
You see I have to configure: {{<maxEntries>666</maxEntries>}} (which is a bad
number) for {{changes:announcement-generate}} to work.
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.11:announcement-generate
(default-cli) on project mycore: No releases found in any of the configured
issue management systems. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.11:announcement-generate
(default-cli) on project mycore: No releases found in any of the configured
issue management systems.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
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:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: No releases found in
any of the configured issue management systems.
at
org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:580)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{noformat}
Instead of querying *all* issues with *all* fields to get a list of all
versions, it would be better to use
*_[/rest/api/2/project/\{projectIdOrKey\}/versions|https://docs.atlassian.com/jira/REST/latest/#d2e231]_*.
> announcement-generate for JIRA doesn't query for relevant issues
> ----------------------------------------------------------------
>
> Key: MCHANGES-333
> URL: https://jira.codehaus.org/browse/MCHANGES-333
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
> Affects Versions: 2.9
> Reporter: Richard Barnett
> Attachments: MCHANGES-333.patch
>
>
> {{announcement-generate}} for JIRA submits a JQL query eg
> {code}
> Address: https://palomamobile.atlassian.net/rest/api/2/search
> ...
> Payload: {"jql":"project = PCSV AND status in (5, 6) AND resolution in (1,
> 8)","maxResults":25,"fields":["*all"]}
> {code}
> and then selects issues from the response which were fixed in the current
> version. If no issues are selected the goal fails, eg:
> {code}
> Couldn't find the release '1.0.76' among the supplied releases:
> [Release[version='1.0.73.1', date='null', description='null', actionsSize=2],
> Release[version='1.0.73', date='null', description='null', actionsSize=3],
> Release[version='1.0.72', date='null', description='null', actionsSize=2],
> Release[version='1.0.75', date='null', description='null', actionsSize=5],
> Release[version='1.0.74', date='null', description='null', actionsSize=4],
> Release[version='1.0.74.1', date='null', description='null', actionsSize=1],
> Release[version='1.0.71.2', date='null', description='null', actionsSize=1],
> Release[version='1.0.71.1', date='null', description='null', actionsSize=1]]
> {code}
> By contrast, {{jira-report}} uses a JQL query with a constraint on
> {{fixVersion}}; eg when {{onlyCurrentVersion=true}} for the same pom as above
> the query is:
> {code}
> Address: https://palomamobile.atlassian.net/rest/api/2/search
> ...
> Payload: {"jql":"project = PCSV AND fixVersion = \"1.0.77\" AND status in (5,
> 6) AND resolution in (1, 8) ORDER BY priority DESC, created
> DESC","maxResults":100,"fields":["*all"]}
> {code}
> It seems like {{announcement-generate}} should use the same JQL query that
> {{jira-report}} does in this case.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
