Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328455 - Built kernel fails to start because of multiple build stamps
Summary: Built kernel fails to start because of multiple build stamps
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: virgo-build (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.0.0.M01   Edit
Assignee: Steve Powell CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-22 07:35 EDT by Glyn Normington CLA
Modified: 2011-02-28 10:34 EST (History)
2 users (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 Glyn Normington CLA 2010-10-22 07:35:04 EDT 
Recent changes in virgo-build run each kernel project in a separate ant step and each project therefore gets its own build stamp. The result is that some parts of the kernel cannot address other parts.

To reproduce, build the kernel with "ant clean clean-integration jar package" and then try to start the result in target/package-expanded:

bin/startup.sh
Exception in thread "main" org.osgi.framework.BundleException: An error occurred trying to read the bundle
	at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:94)
	at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:921)
	at org.eclipse.osgi.framework.internal.core.Framework$1.run(Framework.java:837)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:888)
	at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:832)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:167)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:161)
	at org.eclipse.virgo.osgi.launcher.FrameworkBuilder.installAndStartBundles(FrameworkBuilder.java:164)
	at org.eclipse.virgo.osgi.launcher.FrameworkBuilder.start(FrameworkBuilder.java:155)
	at org.eclipse.virgo.osgi.launcher.Launcher.main(Launcher.java:53)
Caused by: java.io.FileNotFoundException: lib/kernel/org.eclipse.virgo.kernel.core-2.1.0.BUILD-20101022105850.jar (No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.<init>(FileInputStream.java:106)
	at java.io.FileInputStream.<init>(FileInputStream.java:66)
	at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
	at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
	at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:56)
	... 10 more
Comment 1 Glyn Normington CLA 2010-10-22 07:43:36 EDT 
Since we are nearing release of 2.1.0, please switch 2.1.x back to virgo-build 1.29 to avoid this *and* any related problems.

Please then fix the problem and switch master to use it.
Comment 2 Steve Powell CLA 2010-10-22 07:53:15 EDT 
I have reverted 2.1.x branches to use virgo-build 1.29 temporarily.

Problem is that the timestamp was not propagated down to the ant runs of each
sub-project. (This used to be propagated to the subant task.)

I am going to make the appropriate change and test it on kernel master before
committing and pushing changes to virgo-build.
Comment 3 Steve Powell CLA 2010-10-22 08:12:58 EDT 
SHA:	7fab5884b2195f31eaa3f015cffecb9001176b01
Author:	Steve Powell <spowell@vmware.com>
Date:	Fri Oct 22 2010 13:12:05 GMT+0100 (BST)
Subject:	Fix build stamp issue with sub-builds.

Fixes this issue -- set to version 1.36
Comment 4 Steve Powell CLA 2010-10-22 08:19:52 EDT 
Version 1.36 adopted by master branches.
Comment 5 Steve Powell CLA 2010-10-22 08:32:20 EDT 
Fixed, but not adopted by 2.1.x branches until after release of 2.1.0 (for safety).

Do not close this bugzilla until then.
Comment 6 Steve Powell CLA 2010-11-03 06:55:26 EDT 
Changed virgo-build version at branches 2.1.x/1.1.x to 1.36.  This is safe after the 2.1.0/1.1.0 releases.