I'll remove the intentionally disabled entry before the next milestone to avoid confusion. MFT is not planning on shipping a Papyrus integration for Juno.
Steffen On Wed, May 9, 2012 at 9:00 PM, Miles Parker <[email protected]> wrote: > > Thanks for the clarification, Carsten. I vote for removing it to avoid > confusion. At this point we should have functionality locked down for Juno. > > On 2012-05-09, at 11:36 AM, Carsten Reckord wrote: > > Just to avoid any misunderstanding on the MFT aggregation: > > The MFT Papyrus feature is still listed in there as disabled. Since we > currently don't ship this feature, it should stay disabled or be removed. > > Miles Parker <[email protected]> wrote: > > > Hi David, > > > I seem doomed to be involved with projects that are +3 or more. :| > > > I believe that MFT is ready to go and just needed to be enabled, which > > Steffen took care of a couple of days ago. See: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=378601 Steffen, should > > this be working now? > > > Now that BIRT has had their site renamed and fixed some issues, I'm > > going to have another try at getting amp up and running as well. > > > And no, the Virgo one isn't mine in this case. :) (Virgo Tooling isn't > > in Juno train.) > > > cheers, > > > Miles > > > ______________________________ > > Miles T. Parker > > Senior Engineer and Product Manager, Tasktop > > http://tasktop.com > > Committer, Eclipse Mylyn and Virgo > > Project Lead, Model Focussing Tools and AMP > > http://milesparker.blogspot.com > > > On 2012-05-09, at 9:11 AM, David M Williams wrote: > > > Reminder ... it is +3 day! 5 PM this evening (Eastern) will be > > "cut-off" unless someone asks for a few extra hours. > > > I removed the emf compare feature from modeling category, since it > > was cause build to fail. If there is some other one that's supposed to > > be there, please add it back. > > > The following still have disabled repositories or features: > > > amp.b3aggrcon > > equinox.b3aggrcon > > jetty.b3aggrcon > > mft.b3aggrcon > > riena.b3aggrcon > > virgo.b3aggrcon > > > Any word? > > > I can speak to the equinox one. See bug 378735[1]. It is related to > > the org.eclipse.rcp.sdk.id "product". I _think_ I can add it back for > > RC1. But is anyone using it? Can anyone document a use case? It has not > > been working/available for all of Juno, so far, and no one has really > > complained, and no one seems to have a clear id of if or why its > > needed. > > So, I know it'd be short notice to remove it ... but ... would also > > appreciate someone clearly saying why its needed. > > > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=378735 > > > > <graycol.gif>David M Williams---05/09/2012 10:45:14 AM---Thanks for > > replying. But, I'm a little confused, as the be current aggregation > > builds are failing ou > > > From: David M Williams/Raleigh/IBM@IBMUS > > To: [email protected], Cross project issues > > <[email protected]>, > > Date: 05/09/2012 10:45 AM > > Subject: Re: [cross-project-issues-dev] Status and outlook for M7 > > Sent by: [email protected] > > > > > Thanks for replying. But, I'm a little confused, as the be current > > aggregation builds are failing out-of-the-gate saying there is a > > problem with the model, at the emf.compare in the "modeling category" > > does not refer to the right one. And, apparently comes from several > > sources? (at least in past?) so ... is there supposed to be _any_ > > emf.compare in Juno? Or is it completely gone? If the later, I'll just > > remove it from the category. If the the former ... I'll have to hunt > > around for which is "the right one" and use it (so, hoping someone > > knows off the top of their head). > > > FYI, this can be seen by using the b3 aggregator editor, selecting > > the top level "aggregation" note, and then running the "validate" > > command from context menu. (Not even "validate aggregation", just > > "validate" which just validates the XML and EMF model). > > > Thanks, > > > > Laurent Goubet ---05/09/2012 09:02:33 AM---Hi, Sorry about the delay > > before replying, May has a lot of holidays here :). > > > From: Laurent Goubet <[email protected]> > > To: Cross project issues <[email protected]>, > > Date: 05/09/2012 09:02 AM > > Subject: Re: [cross-project-issues-dev] Status and outlook for M7 > > Sent by: [email protected] > > > > > Hi, > > > Sorry about the delay before replying, May has a lot of holidays here > > :). > > > emf-compare.b3aggrcon indeed had one repository "disabled"... that > > was only a leftover from a previous milestone and did not impact M7. > > We've removed that repository from the file. > > > Laurent Goubet > > Obeo > > > On 06/05/2012 21:38, David M Williams wrote: > > > 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 > > > > [attachment "laurent_goubet.vcf" deleted by David M > > Williams/Raleigh/IBM] _______________________________________________ > > cross-project-issues-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > > cross-project-issues-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > _______________________________________________ > > cross-project-issues-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > -- > Sent from my Android phone. Please excuse my brevity. > -- > Carsten Reckord > t +49 (0)561 5743277-33 > f +49 (0)561 5743277-8833 > e [email protected] > > Yatta Solutions GmbH > Sitz der Gesellschaft: Kassel > Amtsgericht Kassel, HRB 14720 > USt-IdNr DE263191529 > > Geschäftsführung: > Johannes Jacop, > Dr. Christian Schneider > > Adresse: > Ludwig-Erhard-Straße 12 > 34131 Kassel > > Kontakt: > t +49 (0)561 5743277-0 > f +49 (0)561 5743277-88 > e [email protected] > > Bankverbindung: > Kasseler Bank eG > BLZ 520 900 00 > Kto-Nr 158 305 > > > ______________________________ > Miles T. Parker > Senior Engineer and Product Manager, Tasktop > http://tasktop.com > Committer, Eclipse Mylyn and Virgo > Project Lead, Model Focussing Tools and AMP > http://milesparker.blogspot.com > skype: milestravisparker > > > -- Steffen Pingel Senior Software Developer, Eclipse Mylyn Mylyn Tasks Lead http://tasktop.com _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
