Mvn integration

The should be a option to mark mvn module as main one, in a big projects there could be many modules with the cros referrenced classes and resources from other modules that they are not dependent on and only main module has all the necessary dependency at run time e.g.
A (Main) has dependency on B and C
B refers classes from C but doesn't have dependency on C

If C is not included in the project but A and B are included all references to C in B are red

2 comments
Comment actions Permalink

Take a look at Maven Inheritance.  That sounds like the real solution.

http://maven.apache.org/pom.html#Inheritance

0
Comment actions Permalink

Thanks, I know about inheritance but out project is really big, and we have a reason to assemble the app at the top level e.g. webapp pom.xml another reason not everything in out control and we cannot refractor legacy maven dependency that come from the different teams

0

Please sign in to leave a comment.