[
http://jira.codehaus.org/browse/MRELEASE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl moved MPRELEASE-24 to MRELEASE-207:
-------------------------------------------------
Workflow: Maven New (was: jira)
Key: MRELEASE-207 (was: MPRELEASE-24)
Project: Maven 2.x Release Plugin (was: maven-release-plugin)
> Update JavaDoc @versin tags on new release
> ------------------------------------------
>
> Key: MRELEASE-207
> URL: http://jira.codehaus.org/browse/MRELEASE-207
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Reporter: Roman Cerny
> Priority: Minor
>
> it would be nice to tell the maven-release-plugin, to change ALL the source
> files as well.
> i mean, it would be nice, if the @version javadoc tag would be automatically
> changed for each class.
> For e.g. when releasing version 1.7 and changing to 1.8-SNAPSHOT, all
> @version tags (for each class) should be changed to 1.8 (right after the
> release).
> So what i need would be the plugin to look at the ${pom.version} and the walk
> through all my packages (in my source folder) and change the @version javadoc
> tag in every single java class file.
--
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
