Bug 257568 - Builds
Summary: Builds
Status: RESOLVED FIXED
Alias: None
Product: JWT (Archived)
Classification: SOA
Component: Yearly Release (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 critical (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 252801 257569
  Show dependency tree
 
Reported: 2008-12-04 11:19 EST by Mickael Istria CLA
Modified: 2008-12-19 07:43 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2008-12-04 11:19:26 EST
+++ This bug was initially created as a clone of Bug #252801 +++

Projects must have build process maturity: scripted, repeatable, and executable by others.
Comment 2 Mickael Istria CLA 2008-12-06 08:29:15 EST
Works on my machine.
Needs to be tested on Eclipse build server, and then this bug can be closed. 
Comment 3 Florian Lautenbacher CLA 2008-12-15 10:05:17 EST
Works on the Eclipse build server, the only thing that is still not integrated is the sign-process; that's why I leave this bug open for the moment.
Comment 4 Mickael Istria CLA 2008-12-15 10:19:58 EST
I patched the customTargets.xml so that pack200, signing and generation of update site should now be automatic. (Actually I simply uncommented lines in SOC customtargets.xml), but it is impossible to test it on desktop machine - since it uses the /usr/bin/sign script that can only be found on Eclipse build server.

However, the generation of update site is wrong since JWT plugins versionning does not conform to Eclipse standard whereas the update site generation does.

To make it work, it seems like we only have to add ".qualifier" to plugins versions (eg 0.5.0.qualifier). More details on bug dedicated to version numbering.

Thus, I think you just only have to check whether the signing works to close this bug ;)
Comment 5 Mickael Istria CLA 2008-12-19 07:43:37 EST
See http://wiki.eclipse.org/JWT_Automatic_Build