[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [p2-dev] Proper Way To Install from P2 Zipped Repos
- From: "Mark Melvin" <Mark.Melvin@xxxxxxxxxx>
- Date: Fri, 22 May 2009 14:24:04 -0700
- Delivered-to: email@example.com
- Thread-index: AcnbIWEq/19DhJsyT9iqjS5+k2RykwAAC7Jg
- Thread-topic: [p2-dev] Proper Way To Install from P2 Zipped Repos
> -----Original Message-----
> From: p2-dev-bounces@xxxxxxxxxxx
> [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Nick Boldt
> Sent: May 22, 2009 5:08 PM
> To: P2 developer discussions
> Subject: Re: [p2-dev] Proper Way To Install from P2 Zipped Repos
> > The problem is, I end up with all sorts of messages about not being
> > able to find the Eclipse bundles required by my features
> and bundles.
> > Here is my build output:
> > [p2.mirror] Problems resolving provisioning plan.
> > [p2.mirror] Unable to satisfy dependency from
> > com.signaklara.platform 2.5.0.v00000008 to bundle
> > org.eclipse.core.runtime [3.4.0,4.0.0).
> > [p2.mirror] Messages while mirroring artifact descriptors.
> > It appears that my repository was created successfully
> and these are
> > just warnings. Is this true? Can I hide these warnings?
> I would guess those are bad, but I've never used the mirror
> app... yet.
> Any time I something like that in the context of a build, it
> generally means the build is about to fail due to missing
> runtime deps.
Thanks for the reply, Nick.
I agree the messages look serious - which is why I asked. But why would
P2 care if all of my bundle dependencies aren't present in my P2
repository (and I am referring to my Eclipse *platform* dependencies,
not other bundles I am building and shipping)? Obviously my feature
requires org.eclipse.core.runtime, but I don't plan on shipping it in my
P2 repository. It should be in the platform that the user is running
when they install my feature.
I've basically got all of my features and plugins building again under
P2 and this appears to be just noise as all of my individual builds seem
to be working fine, and consuming each other as dependencies without
issue, but they are all spitting out this noise when I amalgamate the
repositories. My basic install tests appear to work as well, but I
can't run a full-on test as I have not yet managed to prune out all of
my legacy install handlers. That's next...