>What you're saying sounds reasonable, I agree. Still waiting for
>Enforcer 1.0 release to take advantage of requirePluginVersions,
>though :-) Any updates, Brian?
No, sorry. I am unable to replicate the issue I saw once at a customer
site, so I might just move forward with another beta release.
or a dependency rather then a
> specific version, the plugin can be more easily used in a different poms
> using different versions of dependencies.
>
> I've done a full lock down of plugin versions by specifying the actual
> version and not the version range in the p
; [INFO] Final Memory: 2M/63M
> [INFO]
>
>
>
> Any clues?
>
> --
> - Jan Fredrik Wedén
>
> -
i don't think plugin resolution supports ranges, the brackets are implied for
plugins in that they are all strict versions.
i've have go back and read the code again...
On Fri, 04 Jul 2008 03:12:35 André Kelpe wrote:
> Hi Jan!
>
> > I'm running Maven 2.0.9 on Windows JDK 1.5 through Cygwin. We h
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 setting
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:
>
>
>
>
> org.apache.maven.pl
Greetings,
I'm attempting to follow best practice and lock down plugins in our
parent POM. From what I understand, I should use a version range
instead of a plain version number to accomplish a true lock down for
future reproducibility. E.g. for the clean plugin I would use [2.2]
instead of just 2
