heapifyman wrote:

> Since yesterday several of my maven builds are failing. E.g. the
> install:install goal fails [...]
> some genius uploaded to the central repo some stub-xy versions of all
> maven-xyz-plugins which don't do anything.

These stub plugins have been deployed to our snapshot repository, not to
central. For instance, there is no stub version of the Maven Install Plugin
here:
 
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/
If you really find a stub plugin out on central, please tell us where as
this would need to be fixed.

Let me emphasize that the snapshot repository is meant for "testing purposes
only" and not for production usage as described in [0].

> The only workaround for this seems to be to add group artifact and
> version elements for all the plugins used in a normal maven lifecycle to
> the pom.
> This is tedious

The usual way of specifying the plugin versions is to use a corporate parent
POM that all your projects (directly or indirectly) inherit from. This way,
you can specify (default) plugin versions once in a central place,
independently of the Maven version you currently use.

> and should not be necessary in my opinion at least not for the "official"
> maven plugins.

Please consider locking down plugin versions a recommended practice, for all
plugins you use. Despite our best efforts to deliver good releases, there
could always be bugs or other behaviour changes in a plugin that might break
your build. Therefore, you should not base a production build on
auto-updates of plugins (at random times) but rather first try a new version
locally before using it throughout your build. Using LATEST for a plugin
version and the idea of a reproducible/stable build just do not fit
together.


Benjamin


[0]
http://maven.apache.org/guides/development/guide-testing-development-plugins.html
-- 
View this message in context: 
http://www.nabble.com/-MAVEN-CORE-IT-LOG--tp20033891p20036205.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to