[
https://issues.apache.org/jira/browse/DROIDS-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertil Chapuis updated DROIDS-130:
----------------------------------
Attachment: DROIDS-130_v2.patch
It doesn't really go in the direction of the initial patch. The aim was to
define the plugin versions only when they are not present in the inherited
apache pom project.
The patch also removes the maven-eclipse-plugin definition since the behaviour
defined in the pom can be obtained from the command line: mvn eclipse:eclipse
-DdownloadSources=true -DdownloadJavadocs=true
I also moved the versions from the properties section to the plugin or
dependencies definitions and made some formatting changes.
> Use explicit versions for the Maven plugins
> -------------------------------------------
>
> Key: DROIDS-130
> URL: https://issues.apache.org/jira/browse/DROIDS-130
> 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: http://www.atlassian.com/software/jira
