2011/11/8 Guo Du <[email protected]>: >> too error prone as you have to keep the plugin configuration and the >> dependency list in sync. It doesn't sound like a hard task first, but > What about only configure the dependency list with additional field as > plugin configuration such as: > <configuration> > <bundles> > <bundle> > <groupId>foo</groupId> > <artifactId>bar</artifactId> > <version>x.y.z</version> > <startLevel>1</startLevel> > </bundle> > </bundles> > </configuration> > > Yes, that's basically a variant of what we came up with, but in this case the dependencies are not considered when maven is calculating a build order for a multi project build, so you end up with a "wrong" order when you are using snapshot dependencies. We had cases where the snapshot dep was built after the assembly causing an old snapshop to end up in the application. And other plugins like the versions plugin don't see this either.
But today we learned about the AbstractMavenLifecycleParticipant which hopefully allows us to use above configuration without the above problems. Regards Carsten > -Guo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Carsten Ziegeler [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
