5

We have a multi-module Maven project consisting of a parent POM and 5 or more modules.

Each module can be deployed to a running server as part of the build if we activate our custom "auto-deploy" profile, which is defined explicitly in each module because how/what gets deployed is a little different for each of the modules.

When building from the parent POM though, if I activate the "auto-deploy" profile, Maven will end up deploying all modules, which is almost never what we need to do (based on our dev process etc). But we do want to build from the root as there can be changes across multiple modules and there are dependencies between some modules.

Is there a way, when building from the parent POM, to activate our custom "auto-deploy" Profile for just one of the Modules, but not all of them?

Thanks

yorkw
  • 40,926
  • 10
  • 117
  • 130
Craig S. Dickson
  • 407
  • 6
  • 14

2 Answers2

5

If each of your modules will have it's own "auto-deploy" profile, and profile activation will be triggered by variables passed to mvn command, you will be able to run single mvn command on parent module and decide which modules should be deployed simply by declaring activation variables

<profiles>
    <profile>
        <id>profileId</id>
        <activation>
            <property>
                <name>profileIdEnabled</name>
                <value>true</value>
            </property>
        </activation>
        <properties></properties>
    </profile>
</profiles>

and then

mvn -DprofileIdEnabled=true
TimCO
  • 131
  • 1
  • 1
  • 14
Tomasz Krzyżak
  • 1,087
  • 8
  • 10
3

Check out Maven: The Complete Reference - Section 6.2. Using Advanced Reactor Options.

Starting with the Maven 2.1 release, there are new Maven command line options which allow you to manipulate the way that Maven will build multimodule projects. These new options are:

-rf, --resume-from

   Resume reactor from specified project

-pl, --projects

   Build specified reactor projects instead of all projects

-am, --also-make

   If project list is specified, also build projects required by the list

-amd, --also-make-dependents

   If project list is specified, also build projects that depend on projects on the list

To build only module-b from the root directory:

$ mvn --projects module-b install

yorkw
  • 40,926
  • 10
  • 117
  • 130
  • 2
    What if I want to build all projects, but just `auto-deploy` one of them? Or in my case, skip tests in all of them but one, and still build them all? – Luan Nico Jan 12 '15 at 22:52