Re: [cross-project-issues-dev] Missing release information for some Kepler projects
Hi, we would like to have RTP dropped form the release train. I will delete the b3 aggregator file today. Thansk in advance. Cheers Holger On May 10, 2013, at 7:52 AM, Jacek Pospychała jacek.pospych...@gmail.com wrote: hi, PDT has been building and testing against DLTK-nightly builds for last months, so we prefer DLTK 5.0. thanks, Jacek On Thu, May 9, 2013 at 5:49 PM, Alexey Panchenko alex.panche...@gmail.com wrote: Hi, Unfortunately The DLTK team were quite busy this year with other projects. Initially the previous (4.0, released 2012) version was added to Kepler, with the intent to replace it later with the 5.0 builds from master. So far, that did not happen yet, partly because of source control (- git) build system (- tycho) changes. AFAIK DLTK is used by PDT and Koneki-Lua Development Tools. So the question to these projects: what DLTK version would you prefer in Kepler? Regards, Alex On Thu, May 9, 2013 at 12:26 AM, Wayne Beaton wa...@eclipse.org wrote: I am now only missing the information for the DLTK and Runtime Packaging (RTP) project. I have contacted DLTK via their mailing list; Ian has contacted the RTP project leaders directly (thanks, Ian). I noticed that DLTK is contributing their 4.0 release build (from Juno) to Kepler, despite there being some apparent activity in the project Git repositories. I don't know if there is any specific issue with this, but thought that I'd point it out in case any downstream consumers had any concerns/issues. Thanks, Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. I will not accept review documentation for any release that is not recorded in the project metadata. While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects Mail Attachment.png ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects 480x60.png ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev Holger Staudacher Follow me: @hstaudacher Innoopract Informationssysteme GmbH hstaudac...@eclipsesource.com Tel: +49 721 - 66 47 33 - 0 Fax: +49 721 - 66 47 33 29 = Legal Disclaimer = According to Section 80 of the German Corporation Act Innoopract Informationssysteme GmbH must indicate the following information: Address: Lammstr. 21, 76133 Karlsruhe Germany General Manager: Jochen Krause Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross
Re: [cross-project-issues-dev] Status and readiness for Kepler M1
Hi David, I enabled the rtp contribution. Cheers Holger On Aug 22, 2012, at 11:05 AM, Mickael Istria mist...@redhat.com wrote: I re-enabled GMF-Tooling and changed the content of our milestones/ site to aggregate the latest good build we have. It's the 3.0.0 release, same as what was contributed to Juno. We don't yet have a project plan to know which version will get into the next release and what will be the new features in it. Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev Holger Staudacher Follow me: @hstaudacher Innoopract Informationssysteme GmbH hstaudac...@eclipsesource.com Tel: +49 721 - 66 47 33 - 0 Fax: +49 721 - 66 47 33 29 = Legal Disclaimer = According to Section 80 of the German Corporation Act Innoopract Informationssysteme GmbH must indicate the following information: Address: Lammstr. 21, 76133 Karlsruhe Germany General Manager: Jochen Krause Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Status and Outlook for Juno!
Hi David, the RTP build is done and contributed to the aggregator. The repository is tested and from my point of view everything looks fine. Hope everything works as expected :) Cheers Holger On Jun 13, 2012, at 11:10 PM, David M Williams wrote: Ok, ... about 6:15 PM Eastern? The previous build failed due to emf.query2 problem (bug 381786) so I'll disable that and there will be just about enough time to try a respin before 6:15 ... so, heck ... take till 6:30. :) From:Holger Staudacher hstaudac...@eclipsesource.com To:Cross project issues cross-project-issues-dev@eclipse.org, Date:06/13/2012 04:45 PM Subject:Re: [cross-project-issues-dev] Status and Outlook for Juno! Sent by:cross-project-issues-dev-boun...@eclipse.org Or in an hour and a half. I just landed at the airport. Give me some time until I find a sufficient network connection (eclipse p2 repositories need speed) ;) Sorry for the delay. Cheers Holger On Jun 13, 2012, at 10:10 PM, Ralf Sternberg wrote: The old org.eclipse.rap bundles come from RTP. Holger will update the RTP contribution in about an hour. Regards, Ralf On Wed, Jun 13, 2012 at 4:30 PM, Dennis Hübner dennis.hueb...@itemis.de wrote: Am 13.06.2012 um 16:13 schrieb Ralf Sternberg: For the duplicate org.eclipse.rap.* bundles, 1.5.0.20120612-1458 our RC4 contribution, 20120605-1606 is RC3. I guess someone depending on the rap runtime has not picked up the RC4 yet, could that be EMF? We include any rap bundles or features, therefore we have any prefect match dependencies to rap. Just filter the latest rap version and look which project fails to validate (b3 editor). Or grep for Provided Capabilities org.eclipse.rap* in b3aggr files. Regards, Dennis. The duplicate org.eclipse.jetty.xml bundles come from the rap tools. For some reason, they contain the RC3 version of these bundles. I will re-build the rap tools and contribute them to the aggregator. But since no one depends on them, this should not affect any other project. Thanks for pointing out these problems! Ralf On Wed, Jun 13, 2012 at 3:45 PM, John Arthorne john_artho...@ca.ibm.com wrote: David Williams wrote on 06/12/2012 05:15:26 PM: I appreciate everyone keeping the build green and making progress on the sim rel reports [1], though there are a few serious issues left there. [1] http://build.eclipse.org/juno/simrel/reporeports/ I looked through these, and at this point I think most of them are not blocking the release. Just to save people some time digging through them, these are the remaining issues that I believe are important for Juno (see above report for details): 1) 10 bundles with missing about.html. Six bundles from emf.query2, four from Gemini. 2) 10 features with no license (in particular their license is the string %license). 1 from Virgo, 9 from Gemini. The most common cause of this is missing key in feature.properties file, or the feature.properties file itself is not included in the bin.includes list in the feature's build.properties file. 3) Multiple copies of bundles from eclipse.org projects. These might not be a problem if they are known or understood, but it might mean another project is including old, unreleased versions of another project's bundles. The core.commands dependency seems to be coming from Sapphire, and the remaining dependencies look like they come from RAP. org.eclipse.jetty.xml 8.1.3.v20120522 8.1.3.v20120416 org.eclipse.core.commands 3.6.1.v20120521-2332 3.6.1.v20120521-2329 org.eclipse.rap.jface 1.5.0.20120612-1458 1.5.0.20120605-1606 org.eclipse.jetty.webapp 8.1.3.v20120522 8.1.3.v20120416 org.eclipse.rap.rwt.osgi 1.5.0.20120612-1458 1.5.0.20120605-1606 org.eclipse.rap.rwt 1.5.0.20120612-1458 1.5.0.20120605-1606 John ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev Holger Staudacher Follow me
