Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[orbit-dev] Progress on having just one build assembly feature


FYI, beginning with I200703220322, all our bundles are now in one feature ... "set 1".

Thanks to all the improvements Pascal has made and fixed in PDE build ... and using the slighly-pre-M6 version of the base
builder that Kim provided (the one tagged v20070321), I was able to move all the set 2 bundles to set 1.

So .... please check extra close that I200703220322 (or later) is correct and no subtle bugs have been introduced.

I believe we have one or two singleton bundles, but not multiple versions of those. I will leave the "set 2" mechanics
pretty much in place, for when we do need to have multiple versions of singleton bundles.

Also, there's a couple of limitations (still) in having just one feature.

While the set1 feature itself is from HEAD, the releng maps sill have to be from the set 1 branch. To fix this, I'll have
to fix our current build scripts ... and I'm tired of tweaking build scripts for now. (and, doesn't seem as important as some
other fixes needed, such as signing).

Second, it turns out the releng tools we all know and love doesn't handle multiple versions quite right ... both in releasing
and in "load map projects". I've opened bugs 178719 and 178720 for these.  
https://bugs.eclipse.org/bugs/show_bug.cgi?id=178719
https://bugs.eclipse.org/bugs/show_bug.cgi?id=178720

The implication is, though, that you may not be able to use the releng tool if you are working on a mulitple-version bundle ....
and you'll have to version the bundle project, and update the map file with copy/paste or typing. Use care.


Back to the top