Most plugins seem to be sub-packages of org.apache.maven.plugin; just
a few use org.apache.maven.plugins (e.g. enforcer, shade).
Is there a convention as to which to choose, or are the plugins that
use plugins an anomaly?
-
To
For historical reason this has changed etc..
Use org.apache.maven.plugins (same as groupId)
2013/6/26 sebb seb...@gmail.com:
Most plugins seem to be sub-packages of org.apache.maven.plugin; just
a few use org.apache.maven.plugins (e.g. enforcer, shade).
Is there a convention as to which to
On 26 June 2013 01:13, Olivier Lamy ol...@apache.org wrote:
For historical reason this has changed etc..
Use org.apache.maven.plugins (same as groupId)
OK thanks, I'll stick with plugins for the new ones then.
2013/6/26 sebb seb...@gmail.com:
Most plugins seem to be sub-packages of
