[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[mdt.dev] Re: Fw: [eclipse.org-planning-council] Finally, Bjorn runs the David-o-matic software for Europa
|
Nick,
I'm not sure if it's too late to add the additional EMFT components. I
suspect it's too late because they weren't listed for M4 and whether to add
them really depends on these folks (I've CC'd them) being willing to commit
to following all the Europa rules. If we start dropping these things to
Europa now (Nick, please check if that it's okay!) and that causes any
problems, I'm sure I'll personally be on the hook to answer all the
questions...
Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265 (t/l 969)
Nick
Boldt/Toronto/IBM
To
02/05/2007 05:46 Kenneth Hussey/Ottawa/IBM
PM cc
mdt.dev@xxxxxxxxxxx, Ed
Merks/Toronto/IBM, Paul
Elder/Ottawa/IBM
Subject
Re: Fw:
[eclipse.org-planning-council]
Finally, Bjorn runs the
David-o-matic software for
Europa(Document link: Ed Merks)
1. OCL is now in features-mdt-ocl.xml; I've copied its jars from the old
/technology site over to /modeling/, and updated the site-interim.xml.
features-emft.xml no longer contains OCL.
2. UML2 is now in features-mdt-uml2.xml; UML2 jars are already in the new
place, but site-interim.xml needed to be updated. features-uml2.xml
deleted.
3. EMF is now in features-emf-emf.xml; jars are already in the new place.
features-emf.xml renamed. (MDT XSD is included here.)
4. UML2 Tools, JET, and EODM look fine in MDT, EMFT, and EMFT
(respectively). Query, Validation, and Transaction are all in
features-emft.xml and appear fine.
5. Teneo, CDO, Net4J and JET Editor do not contribute to Europa. Should
they?
--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling :: http://www.eclipse.org/modeling
http://wiki.eclipse.org/index.php/User:Nickb
Kenneth
Hussey/Ottawa/IBM
To
02/05/07 09:28 Nick Boldt/Toronto/IBM@IBMCA
cc
mdt.dev@xxxxxxxxxxx
Subject
Fw: [eclipse.org-planning-council]
Finally, Bjorn runs the
David-o-matic software for
Europa
Nick,
I thought you had put everything in place for MDT? If not, how can I do it?
Thanks,
Kenn Hussey
Senior Software Developer
Rational Software, IBM Software Group
770 Palladium Drive
Kanata, Ontario, K2V 1C8
T: (613) 599-3980 F: (613) 599-3912
----- Forwarded by Kenneth Hussey/Ottawa/IBM on 02/05/2007 09:27 AM -----
Bjorn
Freeman-Benson
<bjorn.freeman-be To
nson@xxxxxxxxxxx> "eclipse.org-planning-council"
Sent by: <eclipse.org-planning-council@eclip
eclipse.org-plann se.org>
ing-council-bounc cc
es@xxxxxxxxxxx
Subject
[eclipse.org-planning-council]
02/05/2007 02:32 Finally, Bjorn runs the
AM David-o-matic software for
Europa
Please respond to
"eclipse.org-plan
ning-council"
<eclipse.org-plan
ning-council@ecli
pse.org>
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.
The update manager in the David-o-matic claims that it cannot
fetch
http://download.eclipse.org/tptp/updates/features/org.eclipse.tptp.platform.sdk_4.3.0.v200611020100-q_J341eFPVPqtDD.jar
, which is true, that file does not exist. What I cannot figure
out is why it is even trying?
The features-tptp.xml file correctly specifies the update site
as file://${user.home}/downloads/tptp/updates/europa/site.xml
This update site has the
features/org.eclipse.tptp.platform.sdk_4.3.0.v200611020100-q_J341eFPVPqtDD.jar
file
Perhaps the problem is that the site.xml has url=
"http://download.eclipse.org/tptp/updates"; when it should be
"http://download.eclipse.org/downloads/tptp/updates"; ? Or maybe
the url attribute should be just left out entirely?
So:
1. 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.
2. Projects that have not entered their feature information should enter
their feature information.
3. I will re-run the build once a day (or more often upon request) until
it all turns green.
4. If the "non-entered" projects have not entered their information by
the end of the week, I will remove them from the build.
5. 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.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
