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 Kepler M4 at end of +1

Yes, this BIRT dependency is invalid due to the ICU4J version increase in Kepler:

org.eclipse.birt.core 4.2.1.v201209121203 depends on: package com.ibm.icu.lang [3.4.4,5.0.0)

It looks like there is already a BIRT bug report for this:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=395365

John




From:        Grégoire Dupé <gdupe@xxxxxxxxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        12/18/2012 02:25 PM
Subject:        Re: [cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




Hello,

When I try to build MoDisco, I get the following error :

[ERROR] Cannot resolve project dependencies:
[ERROR]   Software being installed: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0
[ERROR]   Only one of the following can be installed at once: [com.ibm.icu 4.4.2.v20110823, com.ibm.icu 4.0.1.v20100112, com.ibm.icu 4.2.1.v20100412, com.ibm.icu 50.1.0.v20121116-2]
[ERROR]   Cannot satisfy dependency: org.eclipse.birt.chart.engine 4.2.1.v201209041636 depends on: bundle org.eclipse.birt.core [2.1.0,5.0.0)
[ERROR]   Cannot satisfy dependency: org.eclipse.birt.core 4.2.1.v201209121203 depends on: package com.ibm.icu.lang [3.4.4,5.0.0)
[ERROR]   Cannot satisfy dependency: org.eclipse.e4.rcp.feature.group 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4 depends on: com.ibm.icu [50.1.0.v20121116-2]
[ERROR]   Cannot satisfy dependency: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 depends on: org.eclipse.modisco.java.discoverer.benchmark.feature.feature.group 0.0.0
[ERROR]   Cannot satisfy dependency: org.eclipse.modisco.doc.api.report.eclipsepackage 0.0.0 depends on: org.eclipse.rcp.feature.group 0.0.0
[ERROR]   Cannot satisfy dependency: org.eclipse.modisco.java.discoverer.benchmark 0.10.1.qualifier depends on: bundle org.eclipse.birt.chart.engine 2.5.1
[ERROR]   Cannot satisfy dependency: org.eclipse.modisco.java.discoverer.benchmark.feature.feature.group 0.10.1.qualifier depends on: org.eclipse.modisco.java.discoverer.benchmark 0.0.0
[ERROR]   Cannot satisfy dependency: org.eclipse.rcp.feature.group 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP depends on: org.eclipse.e4.rcp.feature.group [1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4]
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.acceleo.common 3.3.0.v20120131-0422 to bundle com.google.collect 0.0.0.", "Unable to satisfy dependency from org.eclipse.acceleo.engine 3.3.0.v20111213-0806 to bundle com.google.collect 1.0.0.", "Unable to satisfy dependency from org.eclipse.acceleo.engine 3.3.0.v20120131-0422 to bundle com.google.collect 1.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]

I assume that this error is related to the dependency from Birt to com.ibm.icu.lang. I'll have to wait the new build of Birt, I may be late to deliver MoDisco.

Regards,
Grégoire


----- Mail Original -----
De: "David M Williams" <david_williams@xxxxxxxxxx>
À: "Cross project issues (cross-project-issues-dev@xxxxxxxxxxx)" <cross-project-issues-dev@xxxxxxxxxxx>
Envoyé: Lundi 17 Décembre 2012 23h20:28 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: [cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1


We finally got a green build! Though, I did have to disable a few things, either there was a conflict, such as for ICU4J v50 vs 4.2, and many others because something else was disabled.

There's the current status of enabled flag:

Whole contribution disabled ... never enabled for Kepler. I'll remove these if I don't hear something soon.

emf-query2.b3aggrcon - org.eclipse.simrel.build
jwt.b3aggrcon - org.eclipse.simrel.build


These have a feature or repository disabled, some disabled by "owners", since they knew they needed some work still, and a few disabled by me, based on what I could see using the b3 aggregator editor's "validate aggregation" function. Feel free to re-enable if/when you think ready.

amp.b3aggrcon - org.eclipse.simrel.build
birt.b3aggrcon - org.eclipse.simrel.build
dltk.b3aggrcon - org.eclipse.simrel.build (2 matches)
egit.b3aggrcon - org.eclipse.simrel.build
gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build (2 matches)
mat.b3aggrcon - org.eclipse.simrel.build
mdt-papyrus.b3aggrcon - org.eclipse.simrel.build
mmt-qvto.b3aggrcon - org.eclipse.simrel.build
soa-bpel.b3aggrcon - org.eclipse.simrel.build
webtools.b3aggrcon - org.eclipse.simrel.build

I've promoted what we had from this first green build to .../releases/staging.

Don't forget to check the reports occasionally:
http://build.eclipse.org/simrel/kepler/reporeports/

Thanks,

_______________________________________________
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


Back to the top