Re: [m2 plugins] Maven2 Builder Annotations

2008-06-16 Thread [EMAIL PROTECTED]
Matthias Wessendorf schrieb: hi, is there a special reason why the mentioned plugin is requiring maven 2.0.6 ? I think it is b/c of a weird maven dependency. The kinda usual dance: maven-plugin-a - maven-plugin-b - maven-plugin-c - maven-plugin-d ... Just curious if there is a real reason

Re: [m2 plugins] Maven2 Builder Annotations

2008-06-16 Thread Matthias Wessendorf
On Sun, Jun 15, 2008 at 11:58 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: hi, is there a special reason why the mentioned plugin is requiring maven 2.0.6 ? I think it is b/c of a weird maven dependency. The kinda usual dance: maven-plugin-a - maven-plugin-b -

Re: [m2 plugins] Maven2 Builder Annotations

2008-06-16 Thread simon
On Mon, 2008-06-16 at 08:56 -0700, Matthias Wessendorf wrote: I have for some reasons still maven 2.0.4. When I run the mentioned build, it says 2.0.6 is needed. That may have two reasons: -choosing a special plugin / feature that is depending on 2.0.6 -random. Since maven has

Re: [m2 plugins] Maven2 Builder Annotations

2008-06-16 Thread Matthias Wessendorf
Looks like one of those plugins does need a newer version of maven, either because of a newer feature, or it needs a bugfix in the core. Sounds reasonable to me; stuff does improve. true, but there is a bug in a special settings env. with offline build. The bug is a new feature from 2.0.5 or

[m2 plugins] Maven2 Builder Annotations

2008-06-15 Thread Matthias Wessendorf
hi, is there a special reason why the mentioned plugin is requiring maven 2.0.6 ? I think it is b/c of a weird maven dependency. The kinda usual dance: maven-plugin-a - maven-plugin-b - maven-plugin-c - maven-plugin-d ... Just curious if there is a real reason :-) Thanks! Matthias --