Stuart McCulloch wrote: > On 21/12/2007, Stuart McCulloch <[EMAIL PROTECTED]> wrote: >> On 21/12/2007, Richard S. Hall <[EMAIL PROTECTED]> wrote: >>> So, do we have POM files that need to be patched? >> > OK, just committed a round of pom patches so that the main build now only > uses the 1.1.0-SNAPSHOT of the bundleplugin, which fixes the extra file > issue > > when I have time, I'll look into centralizing the bundleplugin version by > setting > it in a pluginManagement section - that should make it much easier to switch > versions in the future... > Many thansk Stuart for fixing this!
Now, I don't think we should always use the latest and greatest of a module in the other modules. If we are thinking of separate releases of the various sub projects, this will sooner or later fail to work. So, I think its better to stay with a released version for a sub project until there is a reason to go to the latest snapshot. And for instance, with a release of bundleplugin 1.1.0, we should have a pretty stable and very usable release. So we shouldn't update the other modules to use 1.2.0-SNAPSHOT of this plugin after the release. The same is true for the parent pom - projects can easily depend on the 1.0.0 version of the parent pom if that version is sufficient. Like we avoid using snapshots of third party libs we should also try to avoid using snapshots of our own artifacts whereever possible. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
