Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of warnero@gmail.com designates
 209.85.217.174 as permitted sender)
MIME-Version: 1.0
Date: Wed, 6 Mar 2013 17:01:17 -0700
Message-ID: 
 <CAJNTuMA1B96iz7kDhyCheUbnQdg7TBro_5CCgq55+KHO55GAyg@mail.gmail.com>
Subject: multi-module lifecycle question
From: Warner Onstine <warnero@gmail.com>
To: users@maven.apache.org
Content-Type: multipart/alternative; boundary=f46d0408d3f7e8121004d74a6776

--f46d0408d3f7e8121004d74a6776
Content-Type: text/plain; charset=ISO-8859-1

Hi all, been working with a multi-module build that has the following
characteristics:
- All sub-modules have the parent pom as their parent
- I have Integration tests setup as their own module
- parent pom has profiles for specific environments setup

In the parent pom I have the a plugin bound to the prepare-package phase
and inherit marked to false (I only want the plugin to run once at the end
of the build, or once before another phase starts). The behavior I am
seeing though is this:
- Run mvn package -D profileName
- it executes my plugin at the top-level first
- Then it proceeds to compile and run the tests on each of the sub-modules
- It never runs my plugin again

What I expected to happen:
- Compile each sub-module
- Run the tests on each sub-module
- See the prepare-package at the root level (because it now hit that phase)
- Run package on each sub-module

I'm not clear as to why the build is doing all the phases within each
module rather than phase-first then module.

Is there an easy/clean way to do this?

The solution I have come up with so far is either
- turn inherit to true and it will run my plugin for each module (bad)
- Move my specific phase stuff into each module that may need it for each
profile (pain in the ass)

Other ideas?

-warner

--f46d0408d3f7e8121004d74a6776--