On 7/1/14 11:29 PM, Alan Berezin wrote:
Hi guys
I have a maven exec plugin execution that seems to prevent any future
goals from executing although it doesnt fail the build. Even when I
replace the main method contents with just a Sys.exit(0), I see the same
problem. If i set skip=true, then the lifecycle is not cut short. Any
ideas? Oddly, it seemed to work for me in another project but I can’t
seem to find the problem here.
Can you show a full logging output (best would be mvn -X ...
output)...best would be to open an issue at
http://jira.codehaus.org/browse/MEXEC
of both cases...
You have to create an account here http://xircles.codehaus.org/signup if
not already have..
If there is a System.exit(...) code there currently the
exec-maven-plugin can't catch it...
Kind regards
karl-Heinz Marbaise
If I use the exec:exec instead, I don’t see the problem.
thx
Alan
<plugin>
<!-- Handles creating the db schemas though code in the data project -->
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.3.1</version>
<executions>
<execution>
<phase>pre-integration-test</phase>
<goals>
<!-- java goal is in the same vm as maven as opposed to the exec goal -->
<goal>java</goal>
</goals>
<configuration>
<executable>java</executable>
<mainClass>com.digispoke.data.database.MetaDbFactory</mainClass>
<classpathScope>test</classpathScope>
<includePluginDependencies>false</includePluginDependencies>
<includeProjectDependencies>true</includeProjectDependencies>
<commandlineArgs></commandlineArgs>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>com.digispoke</groupId>
<artifactId>data</artifactId>
<version>0.0.1-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
