I prefer to hardcode the version because that way everybody uses the
same one and you ensure reproducibility and tracing.
On 1/22/07, mraible <[EMAIL PROTECTED]> wrote:
What's the best way to specify versions for Maven Plugins. In the AppFuse
project, we're distributing archetypes that have plugins pre-defined in the
pom.xml files.
Should we:
1. Have no version
2. Use the latest version in the Maven repo
3. Use <version>LATEST</version>
4. Use <version>RELEASE</version>
We've been using #1 and the downside seems to be that snapshot repositories
are checked for updates. Does this problem go away when we don't depend on
any snapshots?
#2 seems good, but it requires our users to manually update the version
number when a new release comes out.
I'm looking for the method that doesn't cause a slowdown (i.e. checking
repos for updates) in the build process, but auto-upgrades when new releases
come out. We have found issues with some plugins (i.e. Jetty 6.0.1 doesn't
work with JSF), so for those we're willing to hard-code the plugin version.
Thanks,
Matt
--
View this message in context:
http://www.nabble.com/What%27s-the-best-way-to-specify-versions-for-Maven-Plugins--tf3062027s177.html#a8514771
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
