Community
Participate
Working Groups
Build Identifier: M20110909-1335 B3 Aggregator during build aggregation exits with the following message: ---- Message ---- Build failed! Exception was org.eclipse.core.runtime.CoreException: Cannot complete the install because some dependencies are not satisfiable ---- Message ---- However, it does not give any clues to what dependencies could not be satisfied or provide any hints at how to investigate further. There are no red Xs in the model at all. Full error copied from Eclipse follows. Error Tue Jan 10 11:55:59 GMT 2012 Build failed! Exception was org.eclipse.core.runtime.CoreException: Cannot complete the install because some dependencies are not satisfiable org.eclipse.core.runtime.CoreException: Cannot complete the install because some dependencies are not satisfiable at org.eclipse.b3.aggregator.engine.ValidationSetVerifier.run(ValidationSetVerifier.java:677) at org.eclipse.b3.aggregator.engine.Builder.runRepositoryVerifier(Builder.java:1700) at org.eclipse.b3.aggregator.engine.Builder.run(Builder.java:1631) at org.eclipse.b3.aggregator.presentation.AggregatorActionBarContributor$BuildAggregationAction$1.run(AggregatorActionBarContributor.java:292) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Reproducible: Always Steps to Reproduce: This happens every time we attempt to build with a b3aggr file that has worked in the past.
Just for the sake of it (to make sure we're testing the same thing) can you please attach a failing aggregation?
I get the same "Cannot complete the install because some dependencies are not satisfiable" in the headless aggregator. The model verifies OK in the IDE. I will attach the model and the build log.
Created attachment 217845 [details] b3 aggregator model
Created attachment 217846 [details] build log containing the error
Is there a newer b3 aggregator than http://download.eclipse.org/modeling/emft/b3/headless-3.7/ that might output something useful if this error occurs?
What's interesting is that if I run the validation in my Indigo Eclipse it works, and if I run it in the new Juno it fails. I will attach screens hots for both scenarios.
Created attachment 217888 [details] validation on Indigo - works
Created attachment 217889 [details] validation on Juno - fails
Unfortunately the same unhelpful error message occurs in the IDE, so I have no clue to as what B3 thought went really wrong. P.S. I am running on Linux, so this problem seems to affect any platform.
Created attachment 232192 [details] minimal failing aggregator I've attached another aggregation involving the latest Kepler RC3 repo that fails for me with the same exception using the latest b3 aggregator 0.2.0 (running from the editor, not headless). The stack trace line numbers just have changed a bit in the meantime: org.eclipse.core.runtime.CoreException: Cannot complete the install because some dependencies are not satisfiable at org.eclipse.b3.aggregator.engine.ValidationSetVerifier.run(ValidationSetVerifier.java:686) at org.eclipse.b3.aggregator.engine.Builder.runRepositoryVerifier(Builder.java:1704) at org.eclipse.b3.aggregator.engine.Builder.run(Builder.java:1635) at org.eclipse.b3.aggregator.presentation.AggregatorActionBarContributor$BuildAggregationAction$1.run(AggregatorActionBarContributor.java:292) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) I've debugged around a bit and when it fails it actually has more information on the planner status than is shown in the log. For some reason it can't extract a root cause, so the whole information is just lost in the exception message. Unfortunately, in my case, the (otherwise lost) problem information I dug up during debugging doesn't make much sense to me either. It seems to complain that org.eclipse.ui.views is unavailable, which it clearly isn't...: Software being installed: validationSet_main 1.0.0, Cannot satisfy dependency: mappedRepo_download.eclipse.org_releases_kepler 1.0.0 depends on: org.eclipse.rap.sdk.feature.feature.group 0.0.0, Cannot satisfy dependency: mappedRepo_download.eclipse.org_releases_kepler 1.0.0 depends on: org.eclipse.rse.useractions.feature.group 0.0.0, Cannot satisfy dependency: org.eclipse.rap.sdk.feature.feature.group 2.1.0.20130520-1326 depends on: org.eclipse.ui.views 0.0.0, Cannot satisfy dependency: org.eclipse.rap.sdk.feature.feature.group 2.1.0.20130527-1011 depends on: org.eclipse.ui.views 0.0.0, Cannot satisfy dependency: org.eclipse.rap.sdk.feature.feature.group 2.1.0.20130528-1219 depends on: org.eclipse.ui.views 0.0.0, Cannot satisfy dependency: org.eclipse.rse.useractions.feature.group 1.1.500.201305201712 depends on: org.eclipse.ui.views 0.0.0, Cannot satisfy dependency: validationSet_main 1.0.0 depends on: mappedRepo_download.eclipse.org_releases_kepler [1.0.0] (I got this by putting a breakpoint on the throw statement in ValidationSetVerifier:686 and looking at status.globalRequestStatus.explanation)
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.]
This bug is pretty old, and I think error messages have improved (primarily as a result of p2 error messages improving). If you can reproduce on the latest version of the aggregator, which has been renamed and made to work on "Neon.1" please re-open. To "use the latest" I'd suggest starting fresh with a Neon.1 SDK (version 4.6.1) say from http://download.eclipse.org/eclipse/downloads/ and then install the "cbi aggregator" from http://download.eclipse.org/cbi/updates/aggregator/ide/4.6/ BTW, the file extensions now have to be ".aggr" and some of the "internals" of the files/models have changed, so you may have to regenerate or do some fancy editing. Sorry for the churn. Thanks,
