Remove dependencies from parent pom about hotswapagent HOT 4 CLOSED

Those dependencies are mainly test (junit, jmock). Definition in parent POM is more about convenience. I suppose if we move them to child projects, there is no need to specify common version in parent POM and they should be removed completely. Or do you see any advantage?

from hotswapagent.

This is how I've seen it in many open source projects. Having same versions
across all modules is very convenient.
I also think that parent should not enforce that each module must have some
library on class path.

2014-05-08 7:50 GMT+02:00 Jiri Bubnik [email protected]:

Those dependencies are mainly test (junit, jmock). Definition in parent
POM is more about convenience. I suppose if we move them to child projects,
there is no need to specify common version in parent POM and they should be
removed completely. Or do you see any advantage?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-42515550
.

from hotswapagent.

Ok, I agree.

from hotswapagent.

I don't think this is resolved yet. Dependencies have been moved to new parent, but not to dependencyManagement section.

from hotswapagent.