Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 385529 - CBI build should be able to condition the bundle jars it generates
Summary: CBI build should be able to condition the bundle jars it generates
Status: RESOLVED FIXED
Alias: None
Product: CBI
Classification: Technology
Component: prototype (show other bugs)
Version: 1.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CBI Dummy user CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 378234
  Show dependency tree
 
Reported: 2012-07-19 12:11 EDT by Paul Webster CLA
Modified: 2012-07-24 11:26 EDT (History)
1 user (show)

See Also:

Attachments
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 Paul Webster CLA 2012-07-19 12:11:39 EDT 
Our repository output is mostly conditioned to work with pack200, but I don't think the CBI output is.

Would it be possible to tell the bundle build to condition the .jar as it output it?

PW
Comment 1 Igor Fedorenko CLA 2012-07-19 12:18:40 EDT 
This is not exactly correct. CBI build will do pack200 normalization when eclipse-sign profile is enabled (i.e. -Peclipse-sign), but this also implies jarsigning and only works on build.eclipse.org. 

Due to some Maven core limitations, it is not easy to perform pack200 normalization independently of jar signing, so I did not implement this. If you just want to try it locally, you can remove eclipse-jarsigner-plugin from eclipse-parent/pom.xml and run the build with -Peclipse-sign.
Comment 2 Paul Webster CLA 2012-07-24 11:26:21 EDT 
So really it can be done with a slightly modified profile.

PW