Hi Claus! > Why couldn't they wait for Maven 3.1.0 to do this change. Completly agree with you but that's how the real life is going on :-(
> We could @deprecated camel-msv and remove it from Camel 2.11 onwards. I did contact Kohsuke *directly* and asked him to promote a POM 4.0.0 complaint version of his JAXP-Bridge [1] *if* possible. However as he's currently still in Tokyo and "apologies in advance for additional delay in e-mail" [2] I intend to wait a bit longer for his (potential) reply. > Or have someone repackage the *bridge* JAR and maybe host it in the SMX > repo. Yeah exactly, that was my second proposal by this thread which would resolve the problem in case we would not get any help from Kohsuke. So please give me time until March 15th as the deadline and I will go either for one or other approach. But no matter which approach is taken, to avoid any potential problem, the Camel folks should then delete their existing local m2 cache for this bridge before trying Maven 3.0.4. And camel-msv is one of those component denoted by James! So I personally prefer to keep on it, although as you said, probably not too much users make use of it. [1] http://java.net/projects/isorelax-jaxp-bridge/ [2] http://kohsuke.org/2012/02/16/this-week-in-tokyo/ Babak -- View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5527707.html Sent from the Camel Development mailing list archive at Nabble.com.
