I agree that dependency insanity could cause problems , as well as
resources.
However, the maven dependencies can be partly resolved because we can also
just analyze the pom to look at those dependencies.
I imagine as long as resources are loaded from /src/test/resources then we
can make ANY
How do you manage/allow dependency changes?
If you are using a parent pom with a dependency management section, you
have a single pom to watch.
We adopted a policy that developers are not able to change dependencies
during a release cycle.
The versions of dependencies are a team decision
Is there an easy way to build the Java dependency tree from the compiler?
I was thinking that if you can get the Java dependency tree built, then you
take take a look at a diff and look at which files have changed.
Then from there you could take say 1000 test and reduce that to only 10
test if
Hi,
You can't do that with javac, but the takari-plugins maintain a fine
grained dependency graph in order to do incremental builds.
With tests, it is a different thing, though. Their runtime behaviour may
depend on more than their class dependency might tell you: property/xml
files, dependency
