Hi I have fixed this on trunk.
On Thu, Sep 15, 2011 at 4:51 PM, bvahdat <babak.vah...@swissonline.ch> wrote: > Hi Andreas, > > That's indeed true, and that's why no problem occurs concerning > jetty-version property on other modules having parent/pom.xml as the parent > (either directly or indirectly) like the camel-web module. > > However having that jetty-version definition in parent/pom.xml doesn't help > on the problem existing in Camel build POM I mentioned by my previous post. > Please note that Camel build POM's parent is org.apache:apache:9, that's > > http://repo1.maven.org/maven2/org/apache/apache/9/apache-9.pom > > So it has no idea of that jetty-version property in parent/pom.xml, right? > > If you're also an eclipse user as well, could you please confirm if you have > the same problem with eclipse plugin like me. Just as a quick check could > you please go to > > https://svn.apache.org/repos/asf/camel/trunk/buildingtools > > on you local trunk copy and do a: > > mvn eclipse:eclipse > > Don't you see any warnings? > > Regards, Babak > PS: I use maven 3.0.3 on windows > > -- > View this message in context: > http://camel.465427.n5.nabble.com/mvn-eclipse-clean-eclipse-eclipse-not-being-happy-with-jetty-version-tp4806907p4807115.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
