Community
Participate
Working Groups
I converted from Neon to Oxygen and started having lots of build failures (java exceptions) with Ant builds If I run Ant builds in the current JRE, all is good. But if I run a build under a separate JRE, I get errors like the one below. This is even when the separate JRE is the same as the current JRE, but I want to run it in a different thread so I can run multiple tasks at the same time. Every time I run an ANT task in a separate JRE I get about 10 such errors, all referencing different sub-directories under C:/Program Files/eclipse/plugins/org.eclipse.pde.build_3.9.300.v20170515-0912 ------------- Error eclipse.buildId=4.7.1.M20171009-0410 java.version=1.8.0_121 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product org.eclipse.pde.build Error Tue Oct 24 11:20:20 PDT 2017 Illegal character in path at index 16: file:/C:/Program Files/eclipse/plugins/org.eclipse.pde.build_3.9.300.v20170515-0912/./ java.net.URISyntaxException: Illegal character in path at index 16: file:/C:/Program Files/eclipse/plugins/org.eclipse.pde.build_3.9.300.v20170515-0912/./ at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.<init>(Unknown Source) at java.net.URL.toURI(Unknown Source) at org.eclipse.pde.internal.build.properties.PDEProperties.getAntPropertyValue(PDEProperties.java:54) at org.eclipse.ant.core.Property.getValue(Property.java:123) at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.generateCommandLine(AntLaunchDelegate.java:440) at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:243) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) at org.eclipse.core.externaltools.internal.model.ExternalToolBuilder.launchBuild(ExternalToolBuilder.java:183) at org.eclipse.core.externaltools.internal.model.ExternalToolBuilder.doBuildBasedOnScope(ExternalToolBuilder.java:171) at org.eclipse.core.externaltools.internal.model.ExternalToolBuilder.build(ExternalToolBuilder.java:90) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:487) at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:399) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
