On Tue, Dec 15, 2009 at 7:09 AM, Qureshi,Shahzad [Ontario] <[email protected]> wrote: > Hi all, > > I wanna know the standard and the reasons behind it. > > I want to find out if I should specify a version for a maven plugins, lets > say maven-javadoc-plugin, or not to specify it and in which case the default > one will be used. At this point, I don't specify versions > > I recently setup Nexus at my work and started seeing all these errors where > Nexus wouldn't find snapshot version for plugins, maven-javadoc-plugin being > one of them. The maven-javadoc-plugin is at 2.6.2-SNAPSHOT right now, but my > settings.xml is not setup to take care of this scenario.
In general, you NEVER want to work with snapshots. You would only use a snapshot of a plugin if you wanted to test that a critical bug has been fixed and then you would request that the plugin get officially released (and if you can't wait for that, build an internal release). If you start including snapshots in your build process your build can suddenly break and your build is not reproducible (since SNAPSHOTS by definition change over time) That said, as others have pointed out, the best pracitce is to create an organizational parent pom and declare versions there and have your project poms use this parent pom. That way you have control over when to upgrade. If you are lazy (we are) then you can leave off the version and use whatever the latest released version gets pulled down and only if the build breaks to set the version to one that works. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
