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 <hstaudacher@xxxxxxxxxxxxxxxxx>
To:
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>,
Date:
06/13/2012 04:45 PM
Subject:
Re: [cross-project-issues-dev]
Status and Outlook for Juno!
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
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.huebner@xxxxxxxxx>
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_Arthorne@xxxxxxxxxx>
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@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Holger Staudacher
Follow me: @hstaudacher
Innoopract Informationssysteme GmbH
hstaudacher@xxxxxxxxxxxxxxxxx
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@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
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 ====================================================================
|