Community
Participate
Working Groups
Build Identifier: 3.6 Seems the bug 23969 is back in 3.6. When I running the pde build script with 3.6, I got [java] BUILD FAILED [java] C:\build\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\scrip ts\build.xml:36: The following error occurred while executing this line: [java] C:\build\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\scrip ts\build.xml:105: The following error occurred while executing this line: [java] C:\build\customTargets.xml:12: The following error occurred while ex ecuting this line: [java] C:\build\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\templ ates\headless-build\allElements.xml:16: The following error occurred while execu ting this line: [java] C:\build\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\scrip ts\genericTargets.xml:114: The following error occurred while executing this lin e: [java] C:\build\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\scrip ts\genericTargets.xml:119: The following error occurred while executing this lin e: [java] [java] Total time: 14 seconds BUILD SUCCESSFUL Total time: 17 seconds When I running the pde build script with 3.5, I got [java] C ompile failed; see the compiler error output for details. [java] [java] Total time: 15 seconds BUILD FAILED C:\build\build.xml:9: Java returned: 13 Reproducible: Always Steps to Reproduce: Run standard PDE build script with eclipse 3.6 Build id: I20100312-1448. Set the javaconfailerror=true in the build.properties file
java version "1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b07) Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
Not sure of what happened, but the 3.6.1 works all right now.
We made no code changes in Ant for 3.7 that would affect this. Could be related to bug 321386 (why it stopped and started working again). Resolving as WORKSFORME
Yes, looks this could be fixed by the patch of bug 321386. Thanks for the information! (In reply to comment #3) > We made no code changes in Ant for 3.7 that would affect this. > > Could be related to bug 321386 (why it stopped and started working again). > > Resolving as WORKSFORME