[mojo-dev] [jira] (MJAXB-129) Mojo params have incorrectly stated 'since' values

[Anders Hammar (JIRA)]

Title: Message Title

Anders Hammar commented on an issue   Re: Mojo params have incorrectly stated 'since' values I don't agree. My take is that the since tag tells the user when, in this case, a parameter was added. As people could use different version of a plugin it helps determining in what version of the plugin it was added. The behavior of a param (or mojo for that matter) shouldn't change, that is just plain bad from an end user's perspective. If you want to change the behavior of a param, deprecate it and create a new one (different name). There are numerous examples of this, have a look in the Maven core plugins for example. As you made a reference to the javadoc spec earlier, I found this in the docs on how to write javadoc comments: If a member changes from protected to public in a later release, the @since tag would not change, even though it is now usable by any caller, not just subclassers. So, they suggest that even if the impl changes the since tag should not change. As I argue. Add Comment   Mojo's JAXB-2 Maven Plugin / MJAXB-129 Mojo params have incorrectly stated 'since' values On most of the params for the mojos, it is stated since "2.0" which is not correct. To simplify for users migrating to this new major version it would be good do clearly indicate which params are new and which existed in v1.x. Even the mojos themselves are stated as since 2.0 which is wrong. This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email