Jerome Lacoste wrote:
I never add the scm element when I inherit properly.
help:effective-pom shows me that the <scm> element gets properly
identified.
As long as you inherit from a snapshot parent, yes, everything looks good
because the snapshot version's <scm> element points to trunk.
Is the issue caused by the fact the release plugin releases POM with that
tag version ?
Yepp, mojo-17.pom has
scm:svn:http://svn.codehaus.org/mojo/tags/mojo-17
So we lose all benefits to POM inheritance in that case, right ?
Seems like, partly because the plugins are loosely coupled to the Mojo
parent, i.e. they have distinct release cycles and are tagged at different
times.
Goal parameters have no @since annotation.
Does one use released alpha/beta version or just stable versions there ?
Honestly, not sure by myself what the right procedure here is.
Alpha/beta/stable or whatever are all distinct releases. IMHO from a user's
point of view, it's always nice to know that release n+1 has something that
release n had not, hopefully avoiding confusion why some feature might not
work.
Benjamin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
