On Wed, Jun 13, 2012 at 4: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
