David

Thanks for the status update.  We will look into fixing the dependecy on  
'org.eclipse.help.appserver' .

Wenfeng


________________________________
From: [email protected] 
[[email protected]] On Behalf Of David M Williams 
[[email protected]]
Sent: Sunday, May 06, 2012 12:38 PM
To: [email protected]
Subject: [cross-project-issues-dev] Status and outlook for M7


Yes ... its here, M7 week! And, I'm already giving status!

First thing to note it that we now have a stand-alone 4.2 primary build from 
the Eclipse Project, so for the first time we have a pure and correct 4.2 repo. 
In the past, some things from 3.8 were "slipping in" through aggregation due to 
the way the platform was producing and partially (unknowingly) combining 3.8 
and 4.2. But no more, 4.2 only.

One impact of this, is the bundle 'org.eclipse.help.appserver' is no longer 
available ... it was actually removed in 4.1, but it is being left in the 3.x 
stream, even though 3.8 does not use it. It now correctly does _not_ show up in 
4.2 repo via aggregation.

And, this "broke" BIRT ... so, I disabled that, which rippled across 3 or 4 
others that depend on BIRT charting.
I hope BIRT can live without that old bundle and use the jetty server now 
provided by the platform (and used by the help system, in both 3.8 and 4.2).
http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/porting/4.2/incompatibilities.html?h=R4_HEAD#help-appserver

Then there were the (fairly) usual breakages in RAP runtime and Virgo based on 
assumptions on certain platform specific versions, so I disabled those to get a 
green build, and promote an initial M7 version to staging. Be sure to check the 
reports (based on staging) to get as much cleaned up as possible before M7:
http://build.eclipse.org/juno/simrel/reporeports/

In all, the following files have disabled repositories or features. It looks 
worse than it is, but we need to get in completely "enabled" in the next few 
days (or, remove it, if its some old thing that should not even be there any 
longer).

amp.b3aggrcon
birt.b3aggrcon
emf-compare.b3aggrcon
equinox.b3aggrcon
jetty.b3aggrcon
linuxtools.b3aggrcon
mat.b3aggrcon
mdt-papyrus.b3aggrcon
mft.b3aggrcon
rap.b3aggrcon
riena.b3aggrcon
scout.b3aggrcon
virgo.b3aggrcon

As always questions and clarifications are welcome.

Thanks everyone,

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to