But, if I had to guess (your description
is pretty high level) I suspect you are basically telling b3 aggregator
to combine "all of Kepler" with your repo ... right so far? If
so, then I suspect you are running into the (intentional) "negative
dependencies" that are defined for some "runtime only features",
that are there to explicitly prevent some features from "being installed
together" -- in this case, to prevent some "runtime only"
features, say, from RAP, from being installed into the IDE.
As background on these topics, you might
want to read
This "advanced technique"
was introduced in Kepler. Previously, in Juno, everyone used a "fake"
which only the aggregator knew about with respect to particular category.
With the negative requirements now in use, p2 knows about it too, and you
can specify, for example, as RAP does, "install this feature, or SWT,
but never both together" (or, something like that).
I've had some fights with the b3 aggregator today
and it seems to boil down to the fact that the aggregator cannot consume
the kepler repository, neither releases/kepler, nor one of the children
201306260900 or 201309270900.
To witness: I have a toy aggregation (1 feature with one plugin) that validates
OK, but as soon as I add the kepler repo the aggregator dies with:
org.eclipse.core.runtime.CoreException: Cannot complete the install because
some dependencies are not satisfiable