Community
Participate
Working Groups
Created attachment 270288 [details] Screen grab showing error Create a new General Project (new Project -> General -> Project) named, for example, 'btest'. In the top level of the new project, create an Ant build file build.xml containing, for example: <project name="btest" default="hello" basedir="."> <target name="hello"> </target> </project> In the Package Explorer, right click on build.xml and select Run As -> Ant Build The build fails immediately with the error: 'Launching btest build.xml' has encountered a problem. Launch configuration btest build.xml references non-existing project btest. (see attached screen grab). Also fails when run from External Tools menu. This worked as recently as Eclipse 4.6.3.
Thanks for reporting, I am able to reproduce this. Looks like the impact of moving to new Ant version. We are basically getting at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source) at java.net.AbstractPlainSocketImpl.accept(Unknown Source) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at org.eclipse.ant.internal.launching.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:89)
Interesting if related to ant version - ant builds work fine from Java projects, it seems to be the Eclipse project type which is a problem.
I can confirm that this bug occured, when updating from 4.7.1 to 4.7.1a
(In reply to Marcus Storre from comment #3) > I can confirm that this bug occured, when updating from 4.7.1 to 4.7.1a You are using Java 9?
Using Java 8u144
Got the same problem in one of my PHP projects right after updating to 4.7.1a. Reverted to 4.7.1 and it's working again.
As a workaround, you can run the ant file in the "Same JRE as workspace". It works fine.
*** Bug 526539 has been marked as a duplicate of this bug. ***
As we have workaround to run in the same JRE.
*** Bug 526492 has been marked as a duplicate of this bug. ***
New Gerrit change created: https://git.eclipse.org/r/110712
Moving to JDT Debug (Launching).
Gerrit change https://git.eclipse.org/r/110712 was merged to [master]. Commit: http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=1d6a23648eae5c86e51d97ccab0414a7fd14700e
New Gerrit change created: https://git.eclipse.org/r/110782
Gerrit change https://git.eclipse.org/r/110782 was merged to [R4_7_maintenance]. Commit: http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=14f3c86acf31fe752b63f40fc5de3b50270adbbb
Eclipse SDK Version: Oxygen.2 (4.7.2) Build id: M20171108-1700 OS: Windows 7, v.6.1, x86_64 / win32
*** Bug 527220 has been marked as a duplicate of this bug. ***
*** Bug 529440 has been marked as a duplicate of this bug. ***
As an alternative work-around, you can change the project containing the build.xml to a Java project, by adding <nature>org.eclipse.jdt.core.javanature</nature> to the list of <natures> in the .project file, and then restarting Eclipse.