Hi! I'm not sure if this behaviour is by design or a bug.
The situation: I have 2 modules in my project 1.) openwebbeans-impl 2.) openwebbeans-tck (there is a reason for having this in a separate module currently) The impl contains test code (e.g. MockManager) which I like to use in the tck module, so I used the maven-jar-plugin:test-jar to additionally create an attached artifact with classifier "tests" Now my problem: The dependencyManagement in the parent pom contains the version for openwebbeans-impl, but this version doesn't work for all attached items of this artifact. So maven is complaining about not finding the version of openwebbeans-impl:tests. I'd expect maven to use the version of the main artifact if no special version is defined for an attached artifact. Otherwise I'd have to maintain the version of impl twice in my dependencyManagement section WDYT? bug or by design? txs and LieGrue, strub --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
