|
|
|
Hi,
this was closed in March (didnt receive a notification) and finally came back to the issue. I read the "more succinct report" that it refers to and the "solution" does nothing for me. How am i to use ant:java with fork=false and avoid the xml-apis messages ? How am I to use ant:java with fork=true and get the input ? What do i pass in to the "InputHandler" ? Point me to a doc at least that defines this, please Is this fixed in Maven 1.1-beta-X for ant fork=false ? No, I dont use Maven 2 yet. Would it work there ? 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. Hi Arnaud,
so if i dont want to fork the JVM (and I dont see why I should since I want console input from my sample application), what do i need to do in maven.xml ? or project.xml ? I have (in maven.xml) With fork=false I just tried adding your versions of xml-apis, xml-resolver, xercesImpl to project.xml (previously I had nothing specified for those – just entries for my own app jars) and I get With fork=true, then it never reads the console input. What do i do to get Ant to read from the console when fork=true ? What do I specify in this setInputHandler ? (in the above maven.xml snippet) All I want to do is run a sample (Java) app that uses console input via Maven. It works via an Ant task (using fork=false) so I dont see a good reason why not with Maven. If I take a very simple Java app that accepts input on System.in and reads it using a BufferedReader and does nothing more complicated then using fork=false will work
When I bring in other things (like XML parsing) then I get the xml-apis messages. I then add your jars to the dependencies and they get resolved (why I should have to do this is another issue since I haven't specified ANYTHING in project.xml to impose any restriction on XML parsing. I simply selected to run with JDK1.4.2_11 ... all other choices were made by Maven itself. My project.xml contains entries for log4j, jpox, and javax.jdo/jdo2-api ONLY). I then bring in reflection to my (simple) app. It then gives so Maven (1.0.2) is doing something with the CLASSPATH and basic JDK classes (since they are part of the JDK i am using and that Maven is running with) are no longer found whereas they are by using a plain Ant (1.6.1) run with fork=false. This is the issue. [My current JDK is j2sdk1.4.2_11 on Linux] Let's just forget the fork=true case since I shouldn't have to fork just to get something working Attached jar attempts to reproduce this.
To run with Ant To run with Maven (1.0.2) Either there's something I can add to maven.xml/project.xml to get this to work, or something is incorrect in Maven. Maybe there's something I've got wrong in maven.xml ? |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
MAVEN-1425