[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Buckminster builds completely broke when moving from M6 to RC1

I found the packages. Apparently they moved to a pde bundle. After that, only three problem remained:

1. The FeatureManifestParser parse() method apparently changed signature. It now takes an additional URL argument. This is an internal class so I guess that kind of change is OK even after M6.

2. The AdviceFileAdvice moved from package o.e.e.p2.publisher.eclipse to o.e.e.p2.publisher. The packages are not internal.

3. I had to introduce a dependency to a new bundle in order to build, o.e.e.p2.publisher.eclipse.

I found the magnitude of those post M6 changes somewhat surprising given what I perceived last year as very strict rules. The changes were easy to accommodate but it makes me wonder why we for instance had to keep the completely empty query bundle around. Did the rules change?

Thomas Hallgren

On 2011-05-14 09:27, Thomas Hallgren wrote:

Our builds are completely broken. Things that built just fine in 3.7M6 no longer builds. The reason seems to be that the org.eclipse.equinox.p2.publisher.eclipse package and it's internal counter part can no longer be found.

So, where did they go?

Thomas Hallgren
p2-dev mailing list