On Thu, Jul 3, 2008 at 5:12 PM, André Kelpe <[EMAIL PROTECTED]> wrote: > Hi Jan! > >> I'm running Maven 2.0.9 on Windows JDK 1.5 through Cygwin. We have set >> up Proximity as a corporate proxy and I have followed the guide in the >> Sonatype book to configure repositories and mirrors in my settings. >> >> Adding this block to my POM: >> >> <pluginManagement> >> <plugins> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-clean-plugin</artifactId> >> <version>[2.2]</version> >> </plugin> >> </plugins> >> </pluginManagement> >> > > Removing the brackets from the version, if you do not use ranges > should do the trick. >
Yes, it does build if I remove the brackets. However, my understanding was that I needed the brackets to truly "lock down" the plugin versions. Maybe I've just misunderstood previous discussions and that this type of lock down is not needed/supported for plugins and that a plain, single version number is indeed enough. However, I did perform an additional test to check what happened if I did want to use "real" version ranges for plugins. This scenario breaks as well while it work perfectly well with dependencies. So maybe I did miss some part of the docs where it says ranges are not to be used for plugins... -- - Jan Fredrik Wedén --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
