Community
Participate
Working Groups
I20030903 The jdtCompilerAdapter seems to not be correctly dropping invalid classpath entries anymore. For example, using the org.eclipse.ant.core/buildfiles/buildExtraJAR.xml compiles fine on I200308281813. With the -debug attribute set for the build both builds claim: [javac] Using JDT compiler dropping C:\0702\org.eclipse.core.runtime\bin from path as it doesn't exist but on I20030903 you get: [javac] incorrect classpath: C:\0702\org.eclipse.core.runtime\bin
I don't think we changed anything. I will double check. How can I easily reproduce the problem?
Run org.eclipse.ant.core/buildfiles/buildExtraJAR.xml with org.eclipse.core.runtime as a binary plugin (and specify -debug for the full output).
When I try this in self-hosting workspace, it cannot find the jar file containing the ant adapter.
Using 200308281813, I also get these errors: [javac] incorrect classpath: D:\workspaces\test42097 \org.eclipse.core.runtime\bin This should not stop the build. It is simply a message logged to the system err. It doesn't stop the compilation. The build failed because some classes are not found using the remaining classpath. So I don't see anything wrong.
You are correct...the compile does succeed. I cannot get the error message on I20030828. As well this output differs from the "standard" javac and seems strange when you also get output that claims that entry is dropped from the path?
I don't know how you got this in the log: [javac] Using JDT compiler dropping C:\0702\org.eclipse.core.runtime\bin from path as it doesn't exist but on I20030903 you get: I could not get it.
specify -debug as an argument for the Ant build.
Ok, I didn't see it. I think this message is an ant message. I will investigate. The other message incorrect classpath: D:\workspaces\test42097\org.eclipse.core.runtime\bin is from the Eclipse compiler. For me, this is fine. If we drop it, then the batch compiler (outside of ant) won't warn the user anymore and I believe this is a good warning, because: 1) if the compilation fails, you know what entry in the classpath you should fix 2) allow to remove useless entries from the classpath if the compilation succeeds.
The message "dropping...." comes from ant. See public void addExisting(Path source) in the org.apache.tools.ant.types.Path class (line 272). So I would close it as WONTFIX. Ok to close?
Fine by me. FYI Olivier we have this entry to handle both cases of if you have runtime as source or if you have runtime as binary.
You are logging it as a warning and not an error...another case for bug 37265.
We log it to the System.err. Now it depends what is passed as the System.err to the compiler.
I might see this as a problem. I think it really should only be a warning.
So you mean that we should log it to System.out? No problem for me as long as we log it. The idea to log it to System.err is that you can get the message inside the log file if you have one and this could be helpful to get the message afterwards.
System.out would map to an info entry for Ant and that would be more consistent with the "standard" javac output (you would only see it with -verbose or -debug)
Ok, I changed it to System.out instead of System.err. Philippe, please reopen if you disagree.
Verified.
