Manfred Moser wrote:
>
> What about using dependency management in a parent pom?
>
I'm not sure I understand what you're suggesting. Do you mean all
dependency versions are provided by a common parent POM? Doesn't that
present the problem of needing to constantly release the parent POM which
w
My organization has been using Maven and CI for a few years now. Although we
have a process in place that works for us, it has always been difficult to
come up with a successful approach to dependency version management in Maven
at release-time. We use the release plugin extensively, are familiar
For now, my plan is to :
1. Build the DependencyNode tree with the maven DependencyTreeBuilder for
the top-level POM
2. Traverse the tree and find each war Node
3. Serialize the node tree to disk
4. Separately run the dependency node serializer on each of the war projects
found in step 2.
5. Deser
I don't think I can do that easily since that would require rebuilding and
redeploying the modified projects as the new packaging type. Maybe I could
fetch all of the dependency POMs with something like go-offline and modify
them in my local repository? Yuck. I hope there is a nicer way, but I'
I'm trying to perform an analysis of the entire dependency tree for a large
set of projects with deep transitive dependencies. Some of the dependencies
at various levels are war type projects. The dependency plugin appears to
stop at war projects as if they have no dependencies of their own. Do
