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. 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. Regards, Simon
