+1 for that! On 4/11/07, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:
>> "they need to specify versions for all of their plugins in the POM" > > We can't do this in 2.0.x but it needs to be mandatory in 2.1. > Good! :) In my experience with spring-richclient most of the problems of an instable build went away the day I locked down all versions. However you could do 2 things to make our lives easier: 1) Bundle a bunch of plugins together in a version so we can just specify that bundle. Say for example "we use plugin-bundle 2.0.6" (which means we use assembly 2.0, site 2.0-beta5, ...). Of course it should be possible to make an exception on a single plugin in that bundle to give it another version anyway. Plugin-bundles would allow you to test more thoroughly if all plugins work together nicely. 2) A site report (and maybe also a mvn cmd) to receive a list of all plugins which can be updated. (This would be very welcome for dependencies too btw.) With kind regards, Geoffrey De Smet --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
