<packaging> is your friend The C++ code should be using a different packaging type, that way it can bind the plugins that your C++ packaging needs to the corresponding lifecycle phases and then...
mvn compile will do just that, irrespective of whether you are in the C++ or the Java module, and likewise for mvn test mvn package mvn install mvn deploy etc On 13 December 2013 12:24, Michael Priess <digitalover...@googlemail.com>wrote: > Hi, > > our projects have the following structure: > > - parent pom > -- pom.xml > ----cpp--pom.xml > ----java--pom.xml > > To build a project like this we must invoke different build steps. For the > CPP build we like to invoke gcc for the java build we like to invoke javac > and many other steps. In our enviroment we have a lot of builds which are > similar. > > Is there a way to define the builds steps in one place to avoid > duplications of the javac and gcc build configuration. I like to inherite > or get the build steps from one central place and use this steps in a multi > module project. Any idea howto resolve this? > > Cheerrs, > > Michael >
