[ http://jira.codehaus.org/browse/MAVEN-1125?page=comments#action_71098 ]
Arnaud Heritier commented on MAVEN-1125:
----------------------------------------
Hi andy,
I'm sorry but we need to force maven and its plugin to use a known version
(for us) of the XML APIs (xml-apis 1.3.03 + xml-resolver 1.1 + xercesImpl
2.8.0). For that we are defining these APIs in the endorsed libraries which
create a conflict with your own if you don't fork the JVM.
As said in the issue MAVEN-1425, did you try to use
${pom.getAntProject().setInputHandler(...)} ?
> ant:java fork issues
> --------------------
>
> Key: MAVEN-1125
> URL: http://jira.codehaus.org/browse/MAVEN-1125
> Project: Maven
> Issue Type: Bug
> Affects Versions: 1.0-rc2
> Environment: Linux, JDK1.4.2
> Reporter: Andy Jefferson
>
> I have a Java app that I want to invoke via Maven. The Java app uses stdin
> and stdout.
> If I invoke using ant:java using "fork=true" then stdin doesn not respond
> correctly. That is, the app prompts, but the user can type to their hearts
> content and nothing reaches the app.
> If I invoke using ant:java using "fork=false" then I get strange XML related
> errors about unresolved references org/w3c/dom/Node, org/w3c/dom/Document
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
