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 -> maven-plugin-c -> maven-plugin-d ... >> >> Just curious if there is a real reason :-) >> > > Sorry, don't understand what you mean.
see below > > I build the maven2-plugins directory with maven 2.0.9 and it works fine. > And I cannot see anything requiring maven 2.0.6. 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 dependencies on dependencies on dependencies... and one has a dependency on 2.0.6 Just wondering if somebody did something special to kinda ensure you run with 2.0.6 and not below or (like it looks) it was a typical maven-random-issue > > Regards, Simon > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
