Maven: Two projects with common dependency - recommended project structure?

Question

I have project which consists of two separate sub-projects and some common code, with the sub-projects needing to be built independently.

What would be the recommended Maven project structure for this scenario?

I've already tried something like this:

-project-parent
   -pom.xml
-projectA-parent
   -pom.xml
-projectA
   -pom.xml
-projectB-parent
   -pom.xml
-projectB
   -pom.xml
-common
   -pom.xml

The parents for A and B are responsible for building the modules projectA/common and projectB/common. In the project parent POM I would define some common dependencies.

Is there an alternative that does not use a parent hierarchy? Something that, e.g., uses build profiles which can be used to build either projectA or projectB with their dependencies (common)?

Why does the projectA-parent has the dependency on common, when projectA depends on common? — Absurd-Mind, Jun 10 '14 at 14:35
projectA-parent does not have "common" as a dependency, it only declares it as a module so it gets build whenever projectA is build. — matthjes, Jun 10 '14 at 16:31

score 0 · Answer 1 · edited May 23 '17 at 10:26

0

Take a look at the accepted answer of Maven Modules + Building a Single Specific Module.

So you may need just one parent for all modules an then use the pl-option to select the modules for the build.

edited May 23 '17 at 10:26

Community

1
1

answered Jun 12 '14 at 09:57

Rob

5,353
33
34

Maven: Two projects with common dependency - recommended project structure?

1 Answers1