Hi all,
on Feb.5th, I proposed to this list a trick to allow
shipping "combined features"
through Europa but more componentized features through
the project's own
update site -- see below for the original
suggestion.
Unfortunately it turned out that this approach has a
major drawback, which
When the "combined feature" is available on the Europa
site.xml only but
not on the project's own update site, the "Search for
Updates" function does
not work -- because UM tries to find updates for
the topmost features only
but not the included features. This is correct so,
because updating an
included feature without updating the container would
invalidate the container.
Therefore, it is REQUIRED that ALL the features listed
in Europa's site.xml
are ALSO available on the project's own update
site -- at least the one that
is listed in the
feature.xml 's <update> tag.
This gives two potential options of fixing
this:
-
(a) add both combined AND component features to
the update site -- which may seem a bit awkward
-
(b) using the "site-europa.xml" in the <update>
tag but the "site.xml" in the <discovery> tag of
feature.xml
For TM, I have done (a) as a workaround for the M6 time
frame, i.e. I changed our site.xml file to include ALL
the features. For M7 and later, I think I'll be going
with option (b) since our releng build process automatically
generates site-europa.xml out of site.xml anyways --
and I like the idea of having different user-visible
and machine-visible sites.
HTH,
Hi all,
for DSDP-TM the missing entry in site.xml has also been
fixed.
Since I think this is an issue which might apply to other
projects as well, here's what happened:
-
In DSDP-TM, we do the features for Europa not as fine
granular as we do it on our regular update site:
-
On our regular update site we have "runtime-core",
"runtime-ssh", "runtime-ftp", "runtime-dstore"
features.
-
On Europa we only have one "runtime" feature which
includes the four mentioned above.
-
The overall "runtime" feature is available on our
regular update site since it's included in the SDK, but it is not separately
listed in site.xml (since we list the runtime components split up in there).
That's what maded Europa-o-matic choke (it expected site.xml to list the
feature, while I thought it were sufficient to have it on the
disk).
I thought about this quite a while, since I didn't want
to add the "overall runtime" to our regular site.xml. After all,
the same functionality is available by checking the "RSE Runtime"
Category instead of a feature (and it would be weird to have "componentized"
features as well as the overall "including" feature at the same
level).
The solution I finally found might be appliable for
others as well:
-
In addition to our normal site.xml, I do a
"site-europa.xml" file on the same update site
-
site-europa.xml is autogenerated from site.xml by
removing comment lines which are tagged for Europa:
sed -e '/!EUROPA_ONLY!/d' site.xml >
site-europa.xml
-
So I have ONE common site.xml file in the Repository,
with Europa-only stuff tagged as follows:
<!-- !EUROPA_ONLY! Combined Runtime
<feature
url="" id="org.eclipse.rse"
version="1.0.2.qualifier">
<category name="RSE Runtime
only"/>
</feature>
!EUROPA_ONLY!
-->
-
Since the sed
command will remove all lines with !EUROPA_ONLY! tags, the XML comments will
effectively be removed, thus adding the extra feature
reference.
Now I hope that Europa-o-matic likes this fix as well
:-)
Europa Project Leads and Release Engineers,
I've finally run
the David-o-matic software for Europa M4.
The initial build FAILED. The results are here: http://dash.eclipse.org/~bfreeman/europa/
Please
check your own projects and fix the issues.
Unfortunately, I'm also
having trouble with the JVM randomly SIGSEGVing so some of the projects are
not getting complete builds (Platform and Corona are the current victims).
Perhaps it's this
jvm bug. I will try the older JVM 1.5.0_05 to see if the bug goes
away.
For your edification, here are a few of the reasons the various
projects are failing:
- BIRT - specifies com.lowagie.itext version
"1.4.6.v20061212-0842283342-3422" but their site.xml has version
"1.4.6.v20061212------084228344A" instead. (and there are other version
problems for the other features)
- Buckminster - has not entered their feature information...
- Corona - has not entered their feature information...
- DLTK - has not entered their feature information...
- DSDP-TM - the features file specifies a feature if
"org.eclipse.rse" but the interim/site.xml does not contain a feature with
that id.
- DTP - the site.xml has a feature but it's id is
"org.eclipse.datatools.sdk.feature" whereas the features-dtp.xml specifies
the id as "org.eclipse.datatools.sdk".
- ECF - has not entered their feature information...
- Platform - features-ep.xml specifies a version identifier of
"3.3.0.v20061114-0800-87cMN7UcTc-JRPJ.jar" - it shouldn't have the ".jar".
- EMF - features-emf.xml specifies a version identifier of
"2.2.1.v200702010000" but the site-interim.xml has a version of
"2.2.0.v200607131143"
- EMFT-JET - features-emft.xml specifies a version identifier of
"0.7.100.v200612211022" but the site-interim.xml has a version of
"0.7.0.v200606150846"
- GEF - features-gef.xml specifies a version identifier of
"3.3.0.v20061109" but this version does not exist in the site.xml
- BATIK - features-batik.xml specifies a version identifier of
"1.6.0.v20060613-1220-084228285-3442" but the site.xml has
"1.6.0.v20061222-1222-0842283444-3444"
- MDT - has not entered their feature information...
- Eclipse Monkey - has not entered their feature information...
- Mylar - has not entered their feature information...
- STP - has not entered their feature information...
- TPTP - this one I cannot figure out.
So:
- Projects that have a feature-{project}.xml but are not building
correctly, please update the feature-{project}.xml file and/or your update
site's site.xml file.
- Projects that have not entered their feature information should enter
their feature information.
- I will re-run the build once a day (or more often upon request) until
it all turns green.
- If the "non-entered" projects have not entered their information by
the end of the week, I will remove them from the build.
- All projects should update their builds, update sites, and
features-{project}.xml files with the "end-user" and "extender" features
as per our
decision to have two versions per project.
The
explanation/instructions are on the wiki
(copied from David's original version).
- Bjorn
P.S. The
pack200 step also seems to be broken - I'll look into that tomorrow. The
build takes two hours on node4 and the pack200 step has been running for
hours and still isn't finished when I'm sending this email.
