I know what changed, but not why it's broken yet. I changed the Java
rule a little to support the build number of java instead of just 3
digits like before. The parsing is correct according to the unit tests,
but perhaps the version ranging isn't doing what I think. 

-----Original Message-----
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Friday, March 30, 2007 3:43 AM
To: Maven Developers List
Subject: Re: maven-enforcer-plugin

I've no idea what is wrong... though I didn't look to hard.  I rolled  
back Geronimo to use 1.0-alpha-1-20070328.035547-9 which is happy.   
Hopefully you can figure out whats hosed and publish a new snapshot  
so I can remove my hack.

--jason


On Mar 30, 2007, at 12:27 AM, Jason Dillon wrote:

> Something is busted in the latest snapshot...
>
> I'm seeing:
>
> <snip>
> [INFO] Detected Maven Version: 2.0.5 is allowed in the range [2.0.5,).
> [WARNING] Rule 0: RequireJavaVersion failed with message: Detected  
> JDK Version: 1.5.0-07 is not in the allowed range [1.5,1.6).
> </snip>
>
> java -version says:
>
> <snip>
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
> Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
> </snip>
>
> Why is "1.5.0-07" not in this range "[1.5,1.6)"?
>
> The exact same configuration was working about 30 minutes ago  
> (before Mvn decided to refresh snapshots).
>
>  * * *
>
> I'll look into it if I have time... but something is broken :-(
>
> --jason
>
>
> On Mar 29, 2007, at 8:58 PM, Brian E. Fox wrote:
>
>> I reimplemented the enforcer plugin along the lines of Jason D's  
>> idea[1]
>> and I think this is a much more extensible solution. The rules now
>> implement a common interface in shared/maven-enforcer-rule-api and  
>> users
>> will be able to inject their own custom rules. By defining the  
>> interface
>> external to the plugin, the Lint idea that JVZ put out[2] should  
>> be able
>> to invoke these rules, as will IDEs.
>>
>> Please take a look at the site to see how the plugin works and  
>> provide
>> any suggestions. I still need to document how to create your own  
>> rules
>> and inject them, but I believe everything else is covered. A  
>> snapshot of
>> 1.0-alpha-1 has also been deployed for testing. (I believe  
>> Geronimo is
>> already using it)
>>
>> http://maven.apache.org/plugins/maven-enforcer-plugin  (just  
>> deployed,
>> may take a while to refresh)
>>
>> [1]
>> http://www.nabble.com/maven-enforcer-plugin- 
>> tf3431452s177.html#a9565974
>> [2] http://www.nabble.com/Maven-Lint-tf3462956s177.html#a9661545
>>
>> -----Original Message-----
>> From: Brian E. Fox [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, March 20, 2007 12:05 AM
>> To: Maven Developers List
>> Subject: maven-enforcer-plugin
>>
>> There is a new plugin that I'd like to get some feedback on,
>> particularly on non-windows os's and the unit tests.
>>
>>
>>
>> The maven-enforcer-plugin picks up where <prerequisites> leaves  
>> off and
>> allows control over the maven, jdk and os versions of a build.
>>
>>
>>
>> This plugin was initially conceived here:
>>
>> http://www.nabble.com/Control-of-maven-using-prerequisites- 
>> tf3231437s177
>> .html#a8979318
>>
>> And here:
>>
>> http://www.nabble.com/Why-is-prerequisites-not-inherited-- 
>> tf3236197s177.
>> html#a9016296
>>
>>
>>
>> 1.0-alpha-1-SNAPSHOT is deployed and the site is here:
>> http://maven.apache.org/plugins/maven-enforcer-plugin/ (just  
>> deployed so
>> give it a little bit to completely update)
>>
>>
>>
>> If all goes well and no major issues are uncovered, then I think it's
>> ready for staging and a vote.
>>
>>
>>
>> Thanks,
>>
>> Brian
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to