[jira] (MRELEASE-207) Update JavaDoc @versin tags on new release

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

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

Robert Scholte closed MRELEASE-207.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Robert Scholte

You're talking about updating javadoc-tags. There's already a maven-javadoc-plugin with the [fix|http://maven.apache.org/plugins/maven-javadoc-plugin/fix-mojo.html] goal, which can do these things.

                
> Update JavaDoc @versin tags on new release
> ------------------------------------------
>
>                 Key: MRELEASE-207
>                 URL: https://jira.codehaus.org/browse/MRELEASE-207
>             Project: Maven 2.x Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>            Reporter: Roman Cerny
>            Assignee: Robert Scholte
>            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, 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