Thanks,
I did not left it untagged on purpose. Now I updated the build.cfg to the latest version tag of org.eclipse.orbit.releng.builder, which is after my change, so this version includes it too.
From: orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Wednesday, January 12, 2011 9:14 PM
To: Orbit Developer discussion
Subject: Re: [orbit-dev] Adding a library, which is already a bundle, to Orbit
It is very cool that in addition to prebuilt=true in map file, you also found the "exclude" list in buildutilities.xml to have it excluded from pre-pack-conditioning.
To get that version of the builder to be used during a build, you (someone) needs to tag the org.eclipse.orbit.releng.builder project, and put that tag in the build.cfg file. (That's how we control which version of the builder is used, to make sure we have repeatable builds for maintenance etc.)
Perhaps you were doing leaving it untagged/updated on purpose, to have a "before and after" test case? ... I myself am curious to see if it works! (just because we almost ever change that list). If you don't tag/update the builder, I will later this afternoon, and you can let us know if things do not work as expected in builds subsequent to that.
Thanks,
From: "Kirchev, Lazar" <l.kirchev@xxxxxxx>
To: Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Date: 01/07/2011 10:41 AM
Subject: Re: [orbit-dev] Adding a library, which is already a bundle, to Orbit
Sent by: orbit-dev-bounces@xxxxxxxxxxx
Thanks, now I found the file and will make the change.
From: orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of DJ Houghton
Sent: Friday, January 07, 2011 2:15 PM
To: Orbit Developer discussion
Subject: Re: [orbit-dev] Adding a library, which is already a bundle, to Orbit
Map files are used in Eclipse to specify which version (cvs tag) of a bundle you are contributing to the build. The com.ibm.icu bundles are also pre-built so if you search the bundles.map file for their entries, you will see examples of what it looks like.
This is a good short summary of what needs to be done to add a new bundle:
http://wiki.eclipse.org/Adding_Bundles_To_Orbit_In_5_Minutes
"Kirchev, Lazar" ---2011/01/07 07:08:36 AM---Hello, I have recently added to orbit a new project, org.apache.felix.gogo.runtime, for housing the
From:
| 
"Kirchev, Lazar" <l.kirchev@xxxxxxx>
|
To:
|
"orbit-dev@xxxxxxxxxxx" <orbit-dev@xxxxxxxxxxx>
|
Date:
|
2011/01/07 07:08 AM
|
Subject:
|
[orbit-dev] Adding a library, which is already a bundle, to Orbit
|
Sent by:
|
orbit-dev-bounces@xxxxxxxxxxx
|
Hello,
I have recently added to orbit a new project, org.apache.felix.gogo.runtime, for housing the runtime part of the Gogo shell, which I use in another project. The library in this project is already a bundle. I am reading in the wiki that “libraries that are already bundles, they should be marked "prebuilt=true" in the map files”. I am new to orbit – I am adding content to orbit for the first time – and I would like to ask what are these “map files”.
Thanks for the assistance.
Lazar_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
