[
https://jira.codehaus.org/browse/MEXEC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280225#comment-280225
]
Dan Rollo edited comment on MEXEC-102 at 9/28/11 11:18 PM:
-----------------------------------------------------------
Thanks for the quick reply. I had tried to use the maven-antrun-plugin, but can
not because the build.xml file I invoke uses the maven-ant-tasks v2.x, which
are not compatible with maven 3.x (which is what I'm running...). Happy to hear
if there's a fix for that (other than waiting for maven-ant-tasks v3).
When I move this call to exec-maven-plugin from the sub-module into the parent
module, the wait no longer occurs.
No change to the build.xml file, nor the ant being invoked, just calling
exec-maven-plugin from a top level pom instead of a sub-module. Does that still
sound like and "Ant-problem"? I realize if ant doesn't end it's process, we're
stuck, but Ant is not the variable here. Where the exec-maven-plugin is called
seems to be the difference.
was (Author: bhamail):
Thanks for the quick reply. I can not use ant-run because the build.xml
file I invoke uses the maven-ant-tasks v2.x, which are not compatible with
maven 3.x (which is what I'm running...). Happy to hear if there's a fix for
that (other than waiting for maven-ant-tasks v3).
When I move this call to exec-maven-plugin from the sub-module into the parent
module, the wait no longer occurs.
No change to the build.xml file, nor the ant being invoked, just calling
exec-maven-plugin from a top level pom instead of a sub-module. Does that still
sound like and "Ant-problem"? I realize if ant doesn't end it's process, we're
stuck, but Ant is not the variable here. Where the exec-maven-plugin is called
seems to be the difference.
> Exec task ant waiting for user input w/ multi-module build
> ----------------------------------------------------------
>
> Key: MEXEC-102
> URL: https://jira.codehaus.org/browse/MEXEC-102
> Project: Maven 2.x Exec Plugin
> Issue Type: Improvement
> Components: exec
> Affects Versions: 1.2.1
> Environment: windows 7
> maven 3.0.3
> Reporter: Dan Rollo
> Priority: Minor
>
> When building a sub-module that uses the exec plugin to run an Ant command,
> the console waits for a user to press enter.
> This wait only occurs when I build from the parent module and only when I run
> the 'site' command.
> I tried adding the "-noinput" argument to the ant command, but the wait still
> occurs when building from the top level project.
> There is no wait when building the sub-module site by itself.
> A snippet from my sub-module pom is below:
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>exec-maven-plugin</artifactId>
> <version>1.2.1</version>
> <executions>
> <execution>
> <id>get-server-jar</id>
> <phase>package</phase>
> <goals>
> <goal>exec</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <workingDirectory>../remoteinstall/</workingDirectory>
> <executable>cmd</executable>
> <arguments>
> <argument>/c</argument>
> <argument>ant</argument>
> <argument>deploy-fitnesse-server</argument>
>
> <argument>-Dfitnesse.dir=${project.build.outputDirectory}/../</argument>
> <argument>-noinput</argument>
> </arguments>
> </configuration>
> </plugin>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
