incubator-droids-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugen Paraschiv (JIRA)" <>
Subject [jira] Commented: (DROIDS-130) Use explicit versions for the Maven plugins
Date Fri, 11 Mar 2011 22:03:59 GMT


Eugen Paraschiv commented on DROIDS-130:

About the default pom provided by Apache, I think there is certainly an advantage of having
a simpler pom, but there are also some disadvantages. 
For one, Maven 3 is still very new, and plugins are being worked on and fixed with every new
release. Not defining our own versions takes away that advantage. 
Second, the upgrade from this version of the Apache pom and the next is going to represent
a leap instead of an incremental improvement, which is not something to be desired. The pom
probably recognizes this, as it says: "Standard versions of plugins are also defined, these
may be overridden by individual projects as well."
Then, with Droids being a relatively small project, the advantage of not having a few version
lines in the pom isn't really that big. 
The decision is likely going to be a balance between advantages and disadvantages. 
In any event, I will first provide a new small(er) patch addressing the plugins that do not
have versions in our pom and also do not exist in the Apache pom. 

> Use explicit versions for the Maven plugins
> -------------------------------------------
>                 Key: DROIDS-130
>                 URL:
>             Project: Droids
>          Issue Type: Improvement
>    Affects Versions: 0.0.2
>            Reporter: Eugen Paraschiv
>             Fix For: 0.0.2
>         Attachments: DROIDS-130_v1.patch, DROIDS-130_v2.patch
> It's best practice to define the Maven plugins by using explicit versions. This improves
the repeatability of the build, as it doesn't depend on the releases of new versions of these
dependencies to Maven central. 

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message