[eclipse.org-planning-council] Finally, Bjorn runs the David-o-matic sof

[Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>]

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="" class="moz-txt-link-rfc2396E" href="http://download.eclipse.org/tptp/updates">"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.