MAVEN: Multi-module project, How to add different environments for build -

there complex multi module project working on move ant. things want achieve are:

1. ease of development, , packaging developer.

example: parent project son a

         parent project               son                    grandson                   grandson b               daugter (depends on son)                   grandson c                   grandson d 

what want when developer working on daughter project downloads parent project , son dependency should resolved svn repository. know can done defining dependecy in pom.xml conflict second requirement.

2) download daughters , sons of parent project , compile them build consistently can checked automated build manager jenkins. , in addition release revisions on flag maven repository if build successful. please note revision needs head of each module.

3) in both procedure want create tar file or own style directories contain different jars in different directory per need. (i can achieve adding ant copy command; better idea on same)

what standard approaches in maven achieve it.

in maven hierarchy, leaf projects (the grandchildren in example) actual modules contain code , produce artifact (e.g. jar). internal nodes (parent, son, daughter) used hold common configuration , dependencies shared modules down hierarchy. therefore, daughter cannot depend on son, grandson c can depend on grandson a, instance.

if parent project hierarchy have own life cycle, i.e. poms can released independently, should on over svn module. developers working on submodules not need download these poms, automatically retrieved archiva, if deployed there jenkins. see this answer similar situation.

however, see indicate wish build , release modules same time. in case, can have same pom hierarchy keep projects in same svn repository.