CODEWITHSUNDEEP
maven-2includewebproject
Stijn Geukens
Stijn Geukens

Reputation: 15628

Maven: Combine web projects

I have following Maven projects set up:

Now, this project is used for several clients but for each client there are some small differences: mostly differences in configuration files but some clients also require additional java files (which may not be installed for the other clients).

I've been considering several alternatives on how to support this with maven but am still looking for the perfect solution.

The best solution I can think of is to create a separate maven project for each client (e.g. PM-CLIENT1, ...) which contains only the client specific configuration files and additional java files or jsp's, ... . Next step would be to consider the PM-Web project and the client project as one web project, meaning: have them combined (packaged) into 1 war file with files from the client project having precedence over files from the PM-Web project.

More concrete: running mvn package on PM-Client1 would take everything from PM-Web, add/replace the files from PM-Client1 and then package this into a single war.

So the question is: how to achieve this with maven?

Upvotes: 5

Views: 2879

Answers (3)

Pascal Thivent
Pascal Thivent

Reputation: 570365

Yes, this can be done using Overlays. The sample on the webpage is exactly what you are talking about.

For the project structure, you could have something like this:

.
|-- PM-Core
|-- PM-WebCommon (of type war, depends on core)
|-- PM-Client1 (of type war, depends on webcommon)
`-- PM-Client2 (of type war, depends on webcommon)

And use overlay in PM-Client1 and PM-Client2 to "merge" them with PM-WebCommon and package wars for each client.

UPDATE I won't cover all the details but I think that declaring the war dependency with a scope of type runtime is required when using overlay, this is how overlay do work (actually, the whole overlay thing is a kind of hack). Now, to solve your eclipse issue, one solution would be to create a JAR containing the classes of the PM-WebCommon project. To do so, use the attachClasses optional parameter and set it to true. This will tell maven to create a PM-WebCommon-<version>-classes.jar that you'll then be able to declare as dependency in PM-Client1 (with a provided scope). For the details, have a look at MWAR-73 and MWAR-131. This is also discussed in the FAQ of the war plugin. Note that this is not a recommended practice, the right way would be to move the classes to a separate module (and this is the other solution I wanted to mention).

UPDATE (201001018): I've tried the attachClasses parameter and it works with version 2.1-beta-1 of the plugin.

Upvotes: 4

Dr. Hans-Peter St&#246;rr
Dr. Hans-Peter St&#246;rr

Reputation: 25976

Compare also the answers for question different WAR files, shared resources .

Upvotes: 1

crowne
crowne

Reputation: 8534

You could use profiles see http://maven.apache.org/guides/mini/guide-building-for-different-environments.html and use classifiers to distinguish between the artifacts from the different builds for the same version. In this setup, you could create additional optional modules for each of your clients specific customisations under the parent project i.e.
+ PM
++ PM-Core
++ PM-Web
++ PM-Client1
++ PM-Client2

Or you could look at using use the maven assembly plugin

Upvotes: 1

Related Questions