Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331739

Summary: jar renamed during build
Product: [Eclipse Project] Equinox Reporter: Jeff McAffer <jeffmcaffer>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: aniefer, pascal
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Attachments:
Description Flags
tweaked compiler adapter bundle none

Description Jeff McAffer CLA 2010-12-02 22:02:08 EST 
Created attachment 184435 [details]
tweaked compiler adapter bundle

using i1116

In exporting the org.eclipse.pde.build.product.feature/product/pdebuild.product the files for one of the bundles is being renamed.  In particular I have a target that includes the new bundle org.eclipse.jdt.core.ant.compiler.adapter 1.0.0. It is in a file called jdtCompilerAdapter.jar that is extracted from the jdt.core bundle.  This bundle is included in a feature and that feature is included in the pdebuild.product.  From the UI I export the product.  Everything goes smoothly but the output repo and assembled install has the compiler adapter bundle in a file called org.eclipse.jdt.core.ant.compiler.adapter_1.0.0.jar.  This is the standard bundle JAR naming format but it is not the original name of the file. It is somewhat less than optimal that input files are renamed during the build.

I'm not sure who along the way would have this effect.  It is possible that putting things in the p2 repo does the trick.  I figured starting the bug at PDE Build would be the best bet though.

Note that the same thing seems to happen to the ECJ bundle that starts out in a file called ecj-...jar and ends up in a bundle symbolic name style JAR file.

Note that due to Bug 327899 the current jdtCompilerAdapter.jar in jdt.core is missing its bundle metadata.  To support debugging this bug, I'll attach a tweaked jar that has the right manifest and can be added to a target.
Comment 1 Andrew Niefer CLA 2010-12-03 10:11:38 EST 
I'll move this over to p2, I would say this comes from the mapping rules used on the artifact repository, not sure if/how you can keep an alternate name.
Comment 2 Pascal Rapicault CLA 2011-06-12 00:16:53 EDT 
This is the expected p2 behaviour. The artifact repository decides on the file name used on disk (e.g. it can use the blobstore and the cryptic names).
Not sure where to go from there. Closing for now.