Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 124032 - PDE Packager fails due to "_" to "-" conversion
Summary: PDE Packager fails due to "_" to "-" conversion
Status: RESOLVED DUPLICATE of bug 89428
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-16 16:01 EST by Andrew Irvine CLA
Modified: 2006-01-19 13:32 EST (History)
0 users

See Also:

Attachments
Build scripts to reproduce problem described (5.17 KB, application/zip)
2006-01-16 16:02 EST, Andrew Irvine CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Irvine CLA 2006-01-16 16:01:03 EST 
The attached scripts will attempt to take the Eclipse SDK and repackage without the source plug-ins.  This simulates packaging individual plug-ins of Eclipse for purposes of creating products (a real world exercise).

Prior to converting our build from an Eclipse 3.2M3 code base everything was fine.  When we upversioned our code base to Eclipse 3.2M4 our builds began to fail with the error message:

" C:\tmp\eclipse_3.2M3\plugins\org.eclipse.pde.build_3.2.0.v20051031a\scripts\pack
age.xml:61: The following error occurred while executing this line:
C:\tmp\eclipse_3.2M3\plugins\org.eclipse.pde.build_3.2.0.v20051031a\scripts\pack
age.xml:43: org.eclipse.core.runtime.CoreException: Unable to find plug-in: org.
eclipse.jdt.core_3.2.0.v-631. Please check the error log for more details.
"

This failure has halted our automated builds, forcing us to hand make any 3.2M4 based builds.

Maybe related to bug #89428.  Triggered when the version number from CVS was appended to the plug-in version number.

To run the scripts you will need an Eclipse 3.2M3 install for the main engine.  See the comment in customTargets.xml.  In addition you will need to Eclipse SDK zip files, one for 3.2M3, the other for 3.2M4.  These files go in the base if the releng directory structure in the attached file.

From the releng directory the command to execute is:
java -cp c:/tmp/eclipse_3.2M3/startup.jar org.eclipse.core.launcher.Main -application org.eclipse.ant.core.antRunner -buildfile build.xml -DbuildDirectory=c:/tmp/myBuild4 -DpostingDirectory=c:/tmp/myBuild4 -Dversion=3.2M4

Change the version variable to 3.2M3 for a successful 3.2M3 build.
Comment 1 Andrew Irvine CLA 2006-01-16 16:02:38 EST 
Created attachment 33105 [details]
Build scripts to reproduce problem described
Comment 2 Pascal Rapicault CLA 2006-01-16 17:08:02 EST 

*** This bug has been marked as a duplicate of 89428 ***
Comment 3 Andrew Irvine CLA 2006-01-19 09:10:39 EST 
The provided testcase fails using N20060118-0010 build.
Comment 4 Andrew Niefer CLA 2006-01-19 11:17:27 EST 
This works for me when I use eclipse-SDK-N20060118-0010-win32 as the base.
That is:
java -cp C:/Dev/Platform/eclipse-SDK-N20060118-0010-win32/eclipse/startup.jar ...
Comment 5 Andrew Irvine CLA 2006-01-19 13:32:24 EST 
Apologies, you are correct.  There must have been some left over files from my failed runs.  When I tried a clean install of everything, scripts and all, it worked as promised.

Resolving as duplicate of bug #89428

Thanks.

*** This bug has been marked as a duplicate of 89428 ***