Yes, I am aware of moving versions out into variables when they need to be
referenced multiple times. I just don't think the repetition is needed; the
artifact is basically chosen by the global dependency management; the
version really becomes irrelevant in my profile usage.
Would this be suitable
You can use a property in your root POM and refer to it in all your
dependencyManagement sections. While this is not perfect, it works. I am
enclosing depMgmt sections in profiles whenever I need to override scope for a
certain dependency. It is not quite what I want, but does the trick.
--
Al
I have a need that (I don't think) Maven supports. But I would like to hear
from the Maven developers on the feature.
My application targets different appservers. I have all my dependencies
specified under , but I use different profiles
(appserver specific) to change which dependencies are provide
