Try changing the script to something like this: #! /bin/sh $* > /dev/null 2>&1 & exit 0
http://www.xaprb.com/blog/2006/06/06/what-does-devnull-21-mean/ On Thu, Dec 8, 2011 at 9:26 AM, Andreas Sewe < s...@st.informatik.tu-darmstadt.de> wrote: > Hi all, > > in the "pre-integration-test" phase I am trying to start a background > process using exec:exec. While I am aware of the fact that the plugin > does not (yet) support the spawing of background processes directly > [1,2], I was surprised to see that the following workaround doesn't work: > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>exec-maven-plugin</artifactId> > <version>1.2.1</version> > <executions> > <execution> > <id>start-server</id> > <phase>pre-integration-test</phase> > <goals> > <goal>exec</goal> > </goals> > <configuration> > <executable>src/test/scripts/run.sh</executable> > <arguments> > <argument>{server.home}/bin/server</argument> > </arguments> > </configuration> > </execution> > </executions> > </plugin> > > The run.sh script mentioned above is straighforward: > > #! /bin/sh > $* & > exit 0 > > Alas, exec:exec still blocks. Can someone please explain to be why this > happens? The debug output looks OK to me: > > [DEBUG] Executing command line: src/test/scripts/run.sh ./bin/server > > Best wishes, > > Andreas > > [1] <http://jira.codehaus.org/browse/MEXEC-87> > [2] <http://jira.codehaus.org/browse/MEXEC-96> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
