[ http://jira.codehaus.org/browse/MASSEMBLY-169?page=comments#action_82870 ] Dennis Lundberg commented on MASSEMBLY-169: -------------------------------------------
I tried to solve this in Modello. The downside with that is that the versions available in Modello are for the model and not the plugin, since that part of Modello doesn't even know what a Maven plugin is. Might be confusing for end users. What do you think? Anyway, here's an example showing how it would look for the maven-assembly plugin: - http://people.apache.org/~dennisl/maven-assembly-plugin/assembly.html - http://people.apache.org/~dennisl/maven-assembly-plugin/component.html > Document new elements in the assembly descriptor as "Since 2.2" > --------------------------------------------------------------- > > Key: MASSEMBLY-169 > URL: http://jira.codehaus.org/browse/MASSEMBLY-169 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement > Affects Versions: 2.2 > Reporter: Wendy Smoak > Attachments: assembly-since-2.2.patch > > > The assembly.html page includes elements introduced after the 2.1 release. > These need to be documented as "Since 2.2" to avoid confusion. > (Another option would be for modello:xdoc to generate something based on the > <version> in the model.) -- 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
