Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] M6 in danger

Hi all,

Our Buckminster-based build keeps failing with varying errors that all seem to be caused by mismatches between/within Buckminster and p2. And maybe because the repo contains old versions of p2. But this is all guessing. In the end I have no clue what's going on.

Here's a new error that seems to indicate a problem between different parts of p2 (publisher and core):

     [java] org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;
[java] Caused by: java.lang.NoSuchMethodError: org.eclipse.equinox.internal.p2.core.helpers.CollectionUtils.emptyMap()Ljava/util/Map;
     [java] 	at org.eclipse.equinox.p2.publisher.AdviceFileAdvice.loadAdviceMap(
     [java] 	at org.eclipse.equinox.p2.publisher.AdviceFileAdvice.<init>(
     [java] 	at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.createAdviceFileAdvice(
     [java] 	at org.eclipse.equinox.p2.publisher.eclipse.FeaturesAction.generateFeatureIUs(
     [java] 	at org.eclipse.buckminster.pde.tasks.FeaturesAction.generateFeatureIUs(

I can't spend more time on this tonight. I'm aware that EMF Compare seems to push me to contribute an M6 that uses their new APIs. But at this point I can not guarantee that my M5 will be replaced tomorrow.

All ideas are welcome!



Back to the top