Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and Outlook for Juno!

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.


On Wed, Jun 13, 2012 at 4:30 PM, Dennis Hübner <dennis.huebner@xxxxxxxxx> wrote:

Am 13.06.2012 um 16:13 schrieb Ralf Sternberg:

For the duplicate org.eclipse.rap.* bundles, 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.


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

Thanks for pointing out these problems!


On Wed, Jun 13, 2012 at 3:45 PM, John Arthorne <John_Arthorne@xxxxxxxxxx>

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.


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 file, or the file

itself is not included in the bin.includes list in the feature's file.

3) Multiple copies of bundles from 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.















cross-project-issues-dev mailing list


cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Holger Staudacher

Follow me: @hstaudacher

Innoopract Informationssysteme GmbH
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

Back to the top