Community
Participate
Working Groups
I upgraded today from Eclipse 3.1RC3 to final Eclipse 3.1. Unfortunately, just like the former 3.1x Versions ANT is not working again. This time, when I double click an ANT target, the little progress bar in the bottom right corner of Eclipse just displays "Launching: ..." for a short time and then ends. The console view stays empty - no error, no indication if it run or not.
I notice that this might be a problem of the Console view as it doesn't show anything at all anymore ... ??? I tried to close the Console view and open a new one, but it never shows anything (Compilation, Run, etc.).
In addition, when I start a project (which seems to run as the applications log file is written properly) I also don't see it anymore in the debug view. I browsed the preferences to find some indication what changed in 3.1 but I can't believe that this is a new behaviour. Eclipse doesn't show anything of running applications!
This is all pretty surprising behavior which I have never seen nor have any idea how you are in this state. I have been using Eclipse 3.1 daily for Ant and Java development since it was released. Lets start with any indication in the log file?
I have the same problem on all versions of 3.1 that I've tried (including final). The PDE logs the following: Error logged from Ant UI: java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at java.net.ServerSocket.implAccept(ServerSocket.java:450) at java.net.ServerSocket.accept(ServerSocket.java:421) at org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:97) This works correctly on 3.0.2. This works correctly on a different computer on 3.1.
I get a similar problem since switching from 3.0.2 to 3.1 on Windows 2000. When using right-click/Run as/Ant Build on my build.xml, I get a popup saying "Could not find the main class. Program will exit". In the Error log view, I get: Message: Error logged from Ant UI: Exception Stack Trace: java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:97)
I have the same problem as well in 3.1 final. Error logged from Ant UI: java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at java.net.ServerSocket.implAccept(ServerSocket.java:449) at java.net.ServerSocket.accept(ServerSocket.java:420) at org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:97) However- it only appears in one project of mine. It happens in that project consistently. I was running ant builds in that project all day yesterday until this appeared (probably 40+ builds). Today I can run ant builds in other projects in the exact same Eclipse instance and workspace (so far). Try running a particular build a gajillion times and see if that makes it eventually conk out.
Ensure to check that the Ant runtime classpath is not pointing to the old Eclipse Ant plugin (1.6.4 instead of 1.6.5 for example).
My Ant runtime classpath is pointing to eclipse-3.1\plugins\org.apache.ant_1.6.5 for both the projects that will build and the one that won't.
My Ant runtime is pointing to the instance in the 3.1 final plugins directory of Eclipse. I don't know if this is relevant, but I also get this error every time I start 3.1: A workspace crash was detected. The previous session did not exit normally. No stack trace is available. I also verified that 3.0.2 still works correctly on the same computer building the same project. I also tried "-clean" on startup with 3.1, to no avail. I also created a new workspace and imported the projects and still get the same error/problem with 3.1.
On Windows XP SP2, I get the same type of problem. Console shows "a console is not available" and that's all. It was OK with prior Eclipse version (3.0) and I did not change anything but updated Eclipse... Ant run ok in DOS command. Jacques
I see the same problem as well going from 3.0.2 to 3.1. Worked find previously. One additional piece of information. I have an older version of ant installed on the system (1.6.2) and my ANT_HOME environment variable (in windows, no eclipse) points to this directory. I know that ANT really wants this variable set or it will not run. Is having this point to the ant outside of eclipse a problem? Does eclipse create the environment wrong when calling out to ant?
Dan, I don't think it's the point. Because ant seems running but we have no log. Am-I wrong ? Jacques
You are correct Jacques. I just did an experiment. My project does build correctly when invoking the ant task from Eclipse, there is just no log.
Can you all please check that there is no firewall etc. interferring with socket communication on your computers. Do same JRE ant builds provide output (no socket communication)? This can be set on the JRE tab for any particular Ant build.
Setting it to use the same JRE does in fact allow the output to display! As for the firewalls question; there is nothing that I know of.
No software firewall on my XP machine. All is done by my router. "Run in the same JRE as the workspace" was not a solution for me :( Jacques
I do have a firewall on my machine -- corporate mandate. I believe it is "RealSecure Desktop Protector". OS is Windows XP/PRO. Matching or mis-matched JRE makes no difference, I still get no output. And, my ant tasks are not actually running at all. That is, if I do an "ant clean" from the command line to clean things up, then, in Eclipse, select the "test" target, I get a "jvm terminated" on the "heading" line of the console, and no output directories are built.
On my box (Suse Linux 9.1) I encounter a simular problem. The output of Ant is shown in the console, but as soon as the compiling starts, nothing is shown anymore (even though the Ant task still continues to work fine). I am using J2ME Polish (http://www.j2mepolish.org) for building J2ME applications. Internally J2ME Polish uses a Javac task for compiling. In the 3.1 final no output is shown anymore from the momenet the Javac task is executed. In Eclipse 3.0.x, other IDEs as well as on the commandline, the complete output is shown. When the "Run in the same JRE" option is activated, all is well. Best, Robert
"Run in the same JRE" is a successful workaround for me.
> I am using J2ME Polish (http://www.j2mepolish.org) for building J2ME > applications. Internally J2ME Polish uses a Javac task for compiling. In the 3.1 > final no output is shown anymore from the momenet the Javac task is executed. In > Eclipse 3.0.x, other IDEs as well as on the commandline, the complete output is shown. Most likely this is bug 102300...check your log
My apologies. After reading more replies and checking the referring bug, I realize I wasn't correctly setting "run in same JRE". When I set this, I now get output correctly in the console window.
Sorry to mass poll but I am trying to still grok the real root problem causing the bug (I have not been able to reproduce): Does anyone on this bug report NOT have success if they set to run the Ant build in the same JRE?
(In reply to comment #20) > > In Eclipse 3.0.x, other IDEs as well as on the commandline, the complete output > > is shown. > Most likely this is bug 102300...check your log Nope, there is nothing to be seen in workspace/.metadata/.log
In reply to Comment #22 From Darin Swanson, Yes I still have the message "A console is not available" if I set "Run in the same JRE as the workspace". Fortunately the ant task run, and I can see its end in the status bar as I also set "Refresh ressources upon completion". Windows XP SP2, with was OK before in Eclipse 3.0.2 I run eclipse with java jre1.5.0_02 But I have j2sdk1.4.2_05 installed because I need it to work on my project (OFBiz) (+ j2re1.4.2_03 and j2re1.4.2_06 BTW) Outside I run ant with j2sdk1.4.2_05 Jacques Thanks for your commitment ! Here are some of the "Configuration details" : *** Date: Tue Jul 19 21:04:04 CEST 2005 *** Platform Details: *** System properties: ant.home=c:\Program Files\Eclipse\plugins\org.apache.ant_1.6.5 ant.library.dir=c:\Program Files\Eclipse\plugins\org.apache.ant_1.6.5\lib awt.toolkit=sun.awt.windows.WToolkit eclipse.application=org.eclipse.ui.ide.workbench eclipse.buildId=I20050627-1435 eclipse.commands=-os win32 -ws win32 -arch x86 -launcher C:\Program Files\Eclipse\eclipse.exe -name Eclipse -showsplash 600 -exitdata 2f4_2c -data d:\workspace -vm C:\WINDOWS\system32\javaw.exe eclipse.product=org.eclipse.platform.ide eclipse.startTime=1121799499421 eclipse.vm=C:\WINDOWS\system32\javaw.exe eclipse.vmargs=-Xms40m -Xmx256m -jar C:\Program Files\Eclipse\startup.jar eof=eof file.encoding=Cp1252 file.encoding.pkg=sun.io file.separator=\ java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment java.awt.printerjob=sun.awt.windows.WPrinterJob java.class.path=C:\Program Files\Eclipse\startup.jar java.class.version=49.0 java.endorsed.dirs=C:\Program Files\Java\jre1.5.0_02\lib\endorsed java.ext.dirs=C:\Program Files\Java\jre1.5.0_02\lib\ext java.home=C:\Program Files\Java\jre1.5.0_02 java.io.tmpdir=C:\DOCUME~1\JACQUE~1\LOCALS~1\Temp\ java.library.path=C:\WINDOWS\system32;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\workspace\Neogia\Utilitaires\apache-ant-1.6.2\bin;D:\workspace\Neogia\Utilitaires\CVS;D:\workspace\Neogia\Utilitaires\SSH;D:\workspace\Neogia\Utilitaires\Patch\bin;D:\workspace\Neogia\Utilitaires\Subversion\bin;D:\workspace\Neogia\Utilitaires\Maven-1.0.2\bin;C:\Java\j2sdk1.4.2_05\bin;C:\PROGRA~1\ULTRAEDT;D:\workspace\Neogia\Utilitaires\Diff\bin;C:\Program Files\Executive Software\Diskeeper Home Edition\;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual Studio\VC98\bin java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition java.runtime.version=1.5.0_02-b09 java.specification.name=Java Platform API Specification java.specification.vendor=Sun Microsystems Inc. java.specification.version=1.5 java.vendor=Sun Microsystems Inc. java.vendor.url=http://java.sun.com/ java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi java.version=1.5.0_02 java.vm.info=mixed mode, sharing java.vm.name=Java HotSpot(TM) Client VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Sun Microsystems Inc. java.vm.specification.version=1.0 java.vm.vendor=Sun Microsystems Inc. java.vm.version=1.5.0_02-b09 line.separator= org.eclipse.jdt.debug.ui.scrapbookActive=false org.osgi.framework.bootdelegation=* org.osgi.framework.executionenvironment=J2SE-1.5 org.osgi.framework.language=fr org.osgi.framework.os.name=WindowsXP org.osgi.framework.os.version=5.1 org.osgi.framework.processor=x86 org.osgi.framework.system.packages=javax.accessibility,javax.activity,javax.crypto,javax.crypto.interfaces,javax.crypto.spec,javax.imageio,javax.imageio.event,javax.imageio.metadata,javax.imageio.plugins.bmp,javax.imageio.plugins.jpeg,javax.imageio.spi,javax.imageio.stream,javax.management,javax.management.loading,javax.management.modelmbean,javax.management.monitor,javax.management.openmbean,javax.management.relation,javax.management.remote,javax.management.remote.rmi,javax.management.timer,javax.naming,javax.naming.directory,javax.naming.event,javax.naming.ldap,javax.naming.spi,javax.net,javax.net.ssl,javax.print,javax.print.attribute,javax.print.attribute.standard,javax.print.event,javax.rmi,javax.rmi.CORBA,javax.rmi.ssl,javax.security.auth,javax.security.auth.callback,javax.security.auth.kerberos,javax.security.auth.login,javax.security.auth.spi,javax.security.auth.x500,javax.security.cert,javax.security.sasl,javax.sound.midi,javax.sound.midi.spi,javax.sound.sampled,javax.sound.sampled.spi,javax.sql,javax.sql.rowset,javax.sql.rowset.serial,javax.sql.rowset.spi,javax.swing,javax.swing.border,javax.swing.colorchooser,javax.swing.event,javax.swing.filechooser,javax.swing.plaf,javax.swing.plaf.basic,javax.swing.plaf.metal,javax.swing.plaf.multi,javax.swing.plaf.synth,javax.swing.table,javax.swing.text,javax.swing.text.html,javax.swing.text.html.parser,javax.swing.text.rtf,javax.swing.tree,javax.swing.undo,javax.transaction,javax.transaction.xa,javax.xml,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stream,javax.xml.validation,javax.xml.xpath,org.ietf.jgss,org.omg.CORBA,org.omg.CORBA_2_3,org.omg.CORBA_2_3.portable,org.omg.CORBA.DynAnyPackage,org.omg.CORBA.ORBPackage,org.omg.CORBA.portable,org.omg.CORBA.TypeCodePackage,org.omg.CosNaming,org.omg.CosNaming.NamingContextExtPackage,org.omg.CosNaming.NamingContextPackage,org.omg.Dynamic,org.omg.DynamicAny,org.omg.DynamicAny.DynAnyFactoryPackage,org.omg.DynamicAny.DynAnyPackage,org.omg.IOP,org.omg.IOP.CodecFactoryPackage,org.omg.IOP.CodecPackage,org.omg.Messaging,org.omg.PortableInterceptor,org.omg.PortableInterceptor.ORBInitInfoPackage,org.omg.PortableServer,org.omg.PortableServer.CurrentPackage,org.omg.PortableServer.POAManagerPackage,org.omg.PortableServer.POAPackage,org.omg.PortableServer.portable,org.omg.PortableServer.ServantLocatorPackage,org.omg.SendingContext,org.omg.stub.java.rmi,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.events,org.w3c.dom.ls,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers org.osgi.framework.vendor=Eclipse org.osgi.framework.version=1.3.0 org.osgi.supports.framework.extension=true os.arch=x86 os.name=Windows XP os.version=5.1 osgi.arch=x86 osgi.bundles=org.eclipse.core.runtime@2:start, org.eclipse.update.configurator@3:start osgi.bundlestore=c:\Program Files\Eclipse\configuration\org.eclipse.osgi\bundles osgi.configuration.area=file:/c:/Program Files/Eclipse/configuration/ osgi.framework=file:/c:/Program Files/Eclipse/plugins/org.eclipse.osgi_3.1.0.jar osgi.framework.beginningstartlevel=1 osgi.framework.shape=jar osgi.framework.version=3.0.0 osgi.install.area=file:/c:/Program Files/Eclipse/ osgi.instance.area=file:/d:/workspace/ osgi.instance.area.default=file:/C:/Documents and Settings/Jacques Le Roux/workspace/ osgi.logfile=d:\workspace\.metadata\.log osgi.manifest.cache=c:\Program Files\Eclipse\configuration\org.eclipse.osgi\manifests osgi.nl=fr_FR osgi.os=win32 osgi.splashLocation=c:\Program Files\Eclipse\plugins\org.eclipse.platform_3.1.0\splash.bmp osgi.splashPath=platform:/base/plugins/org.eclipse.platform osgi.syspath=c:\Program Files\Eclipse\plugins osgi.ws=win32 path.separator=; sun.arch.data.model=32 sun.boot.class.path=C:\Program Files\Java\jre1.5.0_02\lib\rt.jar;C:\Program Files\Java\jre1.5.0_02\lib\i18n.jar;C:\Program Files\Java\jre1.5.0_02\lib\sunrsasign.jar;C:\Program Files\Java\jre1.5.0_02\lib\jsse.jar;C:\Program Files\Java\jre1.5.0_02\lib\jce.jar;C:\Program Files\Java\jre1.5.0_02\lib\charsets.jar;C:\Program Files\Java\jre1.5.0_02\classes sun.boot.library.path=C:\Program Files\Java\jre1.5.0_02\bin sun.cpu.endian=little sun.cpu.isalist= sun.desktop=windows sun.io.unicode.encoding=UnicodeLittle sun.jnu.encoding=Cp1252 sun.management.compiler=HotSpot Client Compiler sun.os.patch.level=Service Pack 2 user.country=FR user.dir=C:\Program Files\eclipse user.home=C:\Documents and Settings\Jacques Le Roux user.language=fr user.name=Jacques Le Roux user.timezone=Europe/Paris user.variant= *** Features: net.sf.colorer (0.6.1) "Eclipse Colorer Library Plugin" org.eclipse.emf (2.0.3.M200505311255) "Eclipse Modeling Framework (EMF)" org.eclipse.emf.doc (2.0.3.M200505311255) "Eclipse Modeling Framework (EMF) Programmers Guide" org.eclipse.emf.ecore.sdo (2.0.3.M200505311255) "EMF Service Data Objects (SDO)" org.eclipse.emf.ecore.sdo.doc (2.0.3.M200505311255) "EMF Service Data Objects (SDO) Programmers Guide" org.eclipse.emf.ecore.sdo.source (2.0.3.M200505311255) "EMF Service Data Objects (SDO) Source" org.eclipse.emf.source (2.0.3.M200505311255) "Eclipse Modeling Framework (EMF) Source" org.eclipse.gef (3.0.1) "Graphical Editing Framework" org.eclipse.gef.sdk (3.0.1) "Graphical Editing Framework Developer Resources" org.eclipse.gef.source (3.0.1) "Graphical Editing Framework Developer Resources" org.eclipse.jdt (3.0.2) "Eclipse Java Development Tools" org.eclipse.jdt.source (3.0.2) "Eclipse Java Development Tools SDK" org.eclipse.jem (1.0.2.1) "Java EMF Model" org.eclipse.jem.sdk (1.0.2.1) "Java EMF Model SDK" org.eclipse.jem.source (1.0.2.1) "Java EMF Model Source" org.eclipse.pde (3.0.2) "Eclipse Plug-in Development Environment" org.eclipse.pde.source (3.0.2) "Eclipse Plug-in Development Environment Developer Resources" org.eclipse.platform (3.1.0) "Eclipse Platform" org.eclipse.platform.source (3.0.2) "Eclipse Platform Plug-in Developer Resources" org.eclipse.rcp (3.1.0) "Eclipse RCP" org.eclipse.sdk (3.0.2) "Eclipse Project SDK" org.eclipse.sdk.examples (3.0.1) "Eclipse SDK Examples" org.eclipse.team.extras (3.0.0) "Eclipse FTP and WebDAV Support" org.eclipse.ve (1.0.2.1) "Visual Editor" org.eclipse.ve.sdk (1.0.2.1) "Visual Editor SDK" org.eclipse.ve.source (1.0.2.1) "Visual Editor Source" org.eclipse.xsd (2.0.2.M200505311255) "XML Schema Infoset Model (XSD)" org.eclipse.xsd.doc (2.0.2.M200505311255) "XML Schema Infoset Model (XSD) Programmers Guide" org.eclipse.xsd.source (2.0.2.M200505311255) "XML Schema Infoset Model (XSD) Source" org.tigris.subversion.book (1.1.1) "Version Control with Subversion" org.tigris.subversion.subclipse (0.9.31) "Subclipse" *** Current Install Configuration: Install configuration: Last changed on 15 juil. 2005 Location: file:/c:/Program Files/Eclipse/configuration/org.eclipse.update/platform.xml Configured sites: platform:/base/ Configured features: ID: com.ibm.wtp.emf.integration.core, Version: 1.0.1.2 ID: org.eclipse.jdt.source, Version: 3.0.2 ID: org.eclipse.emf.ecore.sdo.source, Version: 2.0.3.M200505311255 ID: org.eclipse.pde.source, Version: 3.0.2 ID: org.eclipse.sdk, Version: 3.0.2 ID: com.simontuffs.eclipse.jarplug.feature, Version: 0.6.0 ID: com.simontuffs.eclipse.jarlaunch.feature, Version: 0.5.0 ID: org.eclipse.emf.ecore.sdo.doc, Version: 2.0.3.200505261142 ID: org.eclipse.team.extras, Version: 3.0.0 ID: org.eclipse.platform, Version: 3.1.0 ID: org.visigoths.freemarker.feature, Version: 0.3.1 ID: org.eclipse.emf.source, Version: 2.0.3.M200505311255 ID: org.eclipse.gef.source, Version: 3.0.1 ID: org.tigris.subversion.book, Version: 1.1.1 ID: org.eclipse.jdt, Version: 3.0.2 ID: org.eclipse.jem, Version: 1.0.2 ID: org.eclipse.ve.source, Version: 1.0.2.1 ID: org.eclipse.gef, Version: 3.0.1 ID: org.eclipse.sdk.examples, Version: 3.0.1 ID: org.eclipse.gef.source, Version: 3.0.1 ID: org.eclipse.emf, Version: 2.0.3.200505261142 ID: org.eclipse.jem.source, Version: 1.0.2.1 ID: org.eclipse.ve.sdk, Version: 1.0.1 ID: org.eclipse.rcp, Version: 3.1.0 ID: org.eclipse.platform.source, Version: 3.0.2 ID: org.eclipse.emf.sdk, Version: 2.0.3.M200505311255 ID: org.eclipse.ve, Version: 1.0.1 ID: org.eclipse.xsd.doc, Version: 2.0.2.200505261142 ID: org.eclipse.xsd.source, Version: 2.0.2.M200505311255 ID: com.ibm.wtp.common.utilities, Version: 1.0.1 ID: org.eclipse.pde, Version: 3.0.1 ID: org.eclipse.emf.ecore.sdo, Version: 2.0.3.200505261142 ID: org.eclipse.xsd, Version: 2.0.2.200505261142 ID: org.eclipse.emf.doc, Version: 2.0.3.200505261142 ID: org.eclipse.jem.sdk, Version: 1.0.1 ID: org.tigris.subversion.subclipse, Version: 0.9.31 ID: net.sf.colorer, Version: 0.6.1
Finally I'm not sure that even the ant task run correctly. When I launch a sub ant task (a build.xml file deep in the tree of directories) It seems not to work. I have to launch ant externally to get it done. Before it was 2 o 3 seconds for a such task, now it's 20 or 30, rather annoying :( Jacques
(In reply to comment #19) > "Run in the same JRE" is a successful workaround for me. I tried the "Run in the same JRE", and I recv'd a different error: java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException. That prompted me to check my ant home - which at the time was "plugins/org.apache.ant_1.6.5". It looked okay, so I click the Ant Home button and browsed to the same directory (plugins/org.apache.ant_1.6.5), then clicked OK. That must have done somthing because it worked after that. -Matt
I too have this problem. Sometimes it is fixed by restarting eclipse, sometimes not. The Ant task does appear to be running anyway, at least for simple tasks (such as a clean). For more complex tasks, it appears to work at least part way through the task but then dies silently. I encountered this bug by trying to research another issues that I'm working on, wherein Ant will show some output to the console but stops partway through the output even though the Ant task is still running.
Scott, the stopping of output is likely a different bug...you don't happen to be running on linux? See bug 102300.
(In reply to comment #28) > Scott, the stopping of output is likely a different bug...you don't happen to > be running on linux? See bug 102300. Nope, Windows for me. I discovered that the issue seems to have something to do with inclusion of other build.xml files over a network. When I copy them locally, the build works fine. But when I include them via an UNC file path, it stops partway through.
I also have seen that particular behaviour: ANT target freeze, error log shows a 'Error logged from Ant UI: java.net.SocketTimeoutException: Accept timed out' message. My config: eclipse3.2M2 launched with a jdk1.5_05, eclipse using a jre1.4.2_09, on WXPSP1. Launching ant using "the same jre than the workspace" does work though. In my case, the cause was the recent installation of Permeo e-border5.1, a proxy SOCKS programs which obviously has fiddled a little too muck with the socks layer... If I remove it, all returns to normal If I install an older version of e-border (4.2), ANT works also just fine... To summarize, it seems this behavious should always been associated with a network communication problem (firewall, socks proxy, ...)
We have the same problem with the same exception noted in comment #4 & #5 Some tests showed that running the project builder in a separate VM caused the ant tasks to fail silently, where as running in the same VM still failed but opened a dialog box in the workspace warning (as in comment #26) that the ant taskdef class (xmlc in this case) could not be found. We tested the targets as external tools and they ran successfully, it was only defined as a project builder that it failed, and identical targets on other projects did not fail. A workaround that worked here was to find the .launch file containing the failing builders config, delete it and replace it with a similar one from another project that works. Then go into the project builder options window and reconfigure it to the correct values for that project. Attempting to manually modify the original broken .launch config did not have the same affect. running: win XP pro SP2 eclipse 3.1 j2sdk1.4.2_07 ant 1.6.5 (eclipse 3.1 default)
I had the same problem as in comment #4 and comment #5 after an upgrade from Eclipse 3.0.2 on Windows. I tried recreating my workspace, but the same problem occurred. I finally managed to work around the problem... I had been setting "env.HOME" in Preferences->Ant Runtime->Properties as our build scripts look for $HOME (they're really meant for *NIX rather than Windows). However, when this is set, the problem occurs. Removing the setting of this property, and instead setting the HOME environment variable in Windows and restarting Eclipse solved the problem. Perhaps the problem is related to the setting of custom Ant properties?
I had the same problem. When I called ant, no output was produced in the console. However the error log got the "java.net.SocketTimeoutException: Accept timed out". This problem started after I modified an ant runtime property in Windows.Preferences. It disappeared when I used the "restore defaults" button, but reappeared when I reentered the properties containing windows paths. I could solver the problem by replacing the backslashes in the paths by normal slashes
Comments #32 and #33 (at least) seem to be manifestations of bug #102641. Is anyone experiencing this problem *without* having custom Ant properties set with backslashes in them? If not, this can probably be set as a dupe.
(In reply to comment #34) > Comments #32 and #33 (at least) seem to be manifestations of bug #102641. Is > anyone experiencing this problem *without* having custom Ant properties set > with backslashes in them? If not, this can probably be set as a dupe. > Like Alistair, the only way I have been able to produce symptoms similar to this bug report is from bug 102641. A more general description of the problem is that we are generating an incorrect commandline for the Ant execution. If others do not have Ant properties set as indicated above, please attach your commandline to this bug report. To get the commandline, go to the Debug view, right click on the Process>Properties>Command Line Without further input from the reporters I will be closing this bug as a duplicate in the near future. Thanks for your help.
(In reply to comment #35) > Like Alistair, the only way I have been able to produce symptoms similar to > this bug report is from bug 102641. I had similar symptoms, but it turns out to be because I moved my entire eclipse installation to a new location on the filesystem. The core ant home was still set to the old location. After fixing this in prefereces -> ant -> runtime life is good again. If you've overridden the defualt ant home in your launcher then I imagine fixing the ant home there will give similar results.
With nothing specific in this bug report I am going to close it marking wontfix as I believe it is handled by fixes to various other bugs in the 3.2 cycle. For 3.2 we have implemented bug 101090 which allows the user to set the default timeout for the Ant socket communication (and the default has been increased from 5 to 20 seconds)...this may have been a factor. A timeout would result in: java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at As well we have fixed bug 102641 which would give similar symptoms.
Created attachment 175872 [details] Image for eclipse
Created attachment 175873 [details] image from eclipse
I had the same problem as in description upgraded eclipse and ANt is not working when I double click an ANT target, the little progress bar in the bottom right corner of Eclipse just displays "Launching: ..." for a short time and then ends. The console view stays empty - no error, no indication if it run or not. Solution :-1)Check eclipse.ini in C:\eclipse directory If it has entry like this then it should point to JRE that you are using for Eclipse Check eclipse JRE go to windows-preferences-java - Installed JRE's both should match -vm C:\Progra~1\Java\jdk1.6.0_21\jre\bin\javaw 2) go to windows-preferences-ant - runtime- classpath -add ant home C:\eclipse\plugins\org.apache.ant_1.7.1.v20100518-1145 (this should be any version of ant ) but ant home should point to whatever version you have in C:\eclipse\plugins\ In case of upgrade some time it will point to older version of ant from older version of eclipse.
I was experienceing the same problem but option two fixed the probelm. "2) go to windows-preferences-ant - runtime- classpath -add ant home C:\eclipse\plugins\org.apache.ant_1.7.1.v20100518-1145 (this should be any version of ant ) but ant home should point to whatever version you have in C:\eclipse\plugins\"
