java - Maven: Does project inheritance or aggregation better support this scenario? -


i porting project ant maven. project consists of core set of classes gets jar'd , used 3-4 other subprojects. importantly (i think?), core jar has own configuration gets set @ build time, , each subproject has configuration set @ build time. in old ant system, anytime built 1 of subprojects like...

ant -dconfiguration=stage clean dist 

...it build core jar using same (stage) configuration, , copy classes dir of subproject's build. i'd duplicate functionality using maven. reading i've done, seems maven can handle using either project inheritance or aggregation. chief differences between 2 methods, , recommend use case i've described?

inheritance used sharing common things between projects, such 3rd party library dependency or properties, or scm locations. aggregation used build projects group. want aggregation, doesn't mean won't using inheritance factor out common stuff.

update: keep in mind maven not building (unlike ant), dependency management, create dependencies on core , not use aggregation @ all. depend on particular version of core. doesn't satisfy requirement of building @ once.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -