Yep, because it needs it as a plugin dependency. Le 11 mai 2012 18:20, "Nestor Urquiza" <nestor.urqu...@gmail.com> a écrit :
> OK I got it. The problem is related to how you look for classes. I believe > you are looking from the running folder. That will work for a simple > project > where you build from the root of that project but it won't where you build > that project from a multipom where you basically build several dependencies > first. Here is how to replicate: > > Consider a core jar and an app war containing the Camel routes. I build > core > before app as app depends on it but to automate I use a project from where > I > called them both (multipom). Folder structure is then: > core > app > multipom > > The multipom pom.xml relevant bits: > ... > <module>../core</module> > <module>../app</module> > </modules> > </project> > > If I build from ../app it works but it won't if I build from ./ > > -- > View this message in context: > http://camel.465427.n5.nabble.com/diagram-generator-tp4375588p5703462.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
