[
http://jira.codehaus.org/browse/MCHANGES-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201436#action_201436
]
Sebastian Hoß commented on MCHANGES-188:
----------------------------------------
Ok I think this is more of a language related issues. I'll try again with a
more complete example:
{code:xml}
<project>
<properties>
<changes.version>2.2</changes.version>
</properties>
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>{${changes.version}}</version>
<configuration>
<onlyCurrentVersion>true</onlyCurrentVersion>
<generateJiraAnnouncement>true</generateJiraAnnouncement>
</configuration>
</plugin>
...
</plugins>
</build>
<reporting>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>{${changes.version}}</version>
<configuration>
<onlyCurrentVersion>true</onlyCurrentVersion>
</configuration>
<reportSets>
<reportSet>
<reports>
<report>jira-report</report>
</reports>
</reportSet>
</reportSets>
</plugin>
...
</plugins>
</reporting>
</project>
{code}
So what I was trying to do was to set the version of the maven-changes-plugin
itself via the changes.version property. I did not know that this property sets
the version parameter of the maven-changes-plugin (again not the version of the
plugin itself) and did not find anything regarding the changes.version property
anywhere in the plugin documentation. On a closer look though the information
is right there, yet slightly hidden[1]. I never paid much attention to those
expressions since I don't like to specify properties via the command line but
rather have them all in my POM and never "collided" with any other plugin
specific expression before. Lesson learned I guess :-)
[1]:
http://maven.apache.org/plugins/maven-changes-plugin/announcement-generate-mojo.html#version
> Announcement collides with ${changes.version} property
> ------------------------------------------------------
>
> Key: MCHANGES-188
> URL: http://jira.codehaus.org/browse/MCHANGES-188
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
> Affects Versions: 2.2
> Reporter: Sebastian Hoß
>
> When you set the ${changes.version} property manually (e.g. to specify the
> version of the changes plugin itself) the changes-plugin uses the given value
> as the projects version and fails if you don't have a matching release with
> the exact same version number.
> This behavior is AFAIK not documented anywhere and should either be changed
> or documented. I stumbled upon this yesterday and wrote an mail with further
> information and a stack trace for this here:
> http://maven.markmail.org/message/mg2qfnd4lw53larn
> The plugins documentation[1] itself says that ${project.version} is the
> default value for the version field, however the code[2] tells that version
> is set to the expression="${changes.version}" with a
> default-value="${project.version}". So this "bug" only affects people who
> have defined a ${changes.version} property. Changing the name of the property
> resolves this.
> This only affects the announcement goals, jira-report along mvn site runs
> fine which may be a little confusing for users who have a running mvn site
> configuration and now want to add announcement mails but run into this
> problem (like myself in this case).
> [1]:
> http://maven.apache.org/plugins/maven-changes-plugin/announcement-generate-mojo.html
> [2]:
> http://maven.apache.org/plugins/maven-changes-plugin/xref/org/apache/maven/plugin/announcement/AnnouncementMojo.html#82
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
