[ http://jira.codehaus.org/browse/MAVEN-1125?page=comments#action_71100 ]
Andy Jefferson commented on MAVEN-1125:
---------------------------------------
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 :-) Sadly I want to do something more complicated.
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
Caused by: java.lang.NoClassDefFoundError: sun/reflect/ConstructorAccessorImpl
at sun.misc.Unsafe.defineClass(Native Method)
at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45)
at
sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381)
at java.security.AccessController.doPrivileged(Native Method)
at
sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377)
at
sun.reflect.MethodAccessorGenerator.generateConstructor(MethodAccessorGenerator.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:30)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:70)
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
> 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
