> You don't need an exclusion, you need to specify tapestry-core as a dependency in your own pom. Nearest version resolution Ah... I'd never taken the time to figure out what maven did in these cases. Thanks for the heads up.
"Dependency mediation - this determines what version of a dependency will be used when multiple versions of an artifact are encountered. Currently, Maven 2.0 only supports using the "nearest definition" which means that it will use the version of the closest dependency to your project in the tree of dependencies. You can always guarantee a version by declaring it explicitly in your project's POM. Note that if two dependency versions are at the same depth in the dependency tree, until Maven 2.0.8 it was not defined which one would win, but since Maven 2.0.9 it's the order in the declaration that counts: the first declaration wins." -- View this message in context: http://tapestry.1045711.n5.nabble.com/updating-from-5-3-1-to-5-3-5-tp5716200p5716220.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
