I just wanted to mention that defining two plugin sections of the same
plugin (exec-maven-plugin in your case) is incorrect. I believe there is a
bug in som Maven versions that allow that, but it's not te corredt way of
doing things. Instead, you should specify two execution sections in the same
plugin section.

/Anders

On Mon, Dec 14, 2009 at 17:36, jabba <k...@soebes.de> wrote:

>
> Hi,
>
> i'm testing a setup with Maven and a combination of Java/Non Java Projects
> (using RPM plugin etc.)...
>
> I'm using a parent to bind some calls to exec plugin to particular phases:
>
> <build>
>   <plugins>
>      <plugin>
>               <groupId>org.codehaus.mojo</groupId>
>                <artifactId>exec-maven-plugin</artifactId>
>                <version>1.1.1</version>
>                <executions>
>                    <execution>
>                        <id>initialize</id>
>                        <phase>initialize</phase>
>                        <goals>
>                            <goal>exec</goal>
>                        </goals>
>                        <configuration>
>                            <executable>cmake</executable>
>                            <arguments>
>                                <argument>....</argument>
>                                <argument>.</argument>
>                            </arguments>
>                        </configuration>
>                    </execution>
>                </executions>
>            </plugin>
>
>            <plugin>
>                <groupId>org.codehaus.mojo</groupId>
>                <artifactId>exec-maven-plugin</artifactId>
>                <version>1.1.1</version>
>                <executions>
>                    <execution>
>                        <id>compile</id>
>                        <phase>compile</phase>
>                        <goals>
>                            <goal>exec</goal>
>                        </goals>
>                        <configuration>
>                            <executable>make</executable>
>                        </configuration>
>                    </execution>
>                </executions>
>            </plugin>
>   </plugins>
> </build>
> ...
> Using the rpm-plugin in modules is working like a charm...so far so
> good....
>
> but now i reached a little problem, cause i have a piling project which
> does
> not need any calls to the above exec parts...but based on my configuration
> they are of course called as defined....
>
> Is there a way to prevent calling the exec's in a sub-module which inherits
> the parent pom information....
>
> Kind regards
> Karl Heinz Marbaise
> --
> View this message in context:
> http://old.nabble.com/Maven-Exec---Inheritance---Multi-Module-Build-tp26779913p26779913.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to