[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [p2-dev] ecf feature?
- From: "Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
- Date: Wed, 1 Apr 2009 18:00:59 +0200
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acmy4pg+7sJW8sBUSBGn6zmPptesIwAAENFQ
- Thread-topic: [p2-dev] ecf feature?
Hi Scott :)
I think we are fine with the setup as-is, sounds like p2 got it all
I guess I was thinking in p1 terms here, where only included plug-ins
would be considered part of a feature, and the dependencies were a
slightly different matter..
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Scott Lewis
Sent: Wednesday, April 01, 2009 5:57 PM
To: P2 developer discussions
Subject: Re: [p2-dev] ecf feature?
We could, upon request, create an ECF feature for distributing just the
filetransfer bundles (i.e. those used by p2/SDK). But we're only going
to do it if it's something people actually want as it means extra
Galileo releng work for us (and we have enough already).
Haigermoser, Helmut wrote:
> Ciao Pascal :)
> So, in order to get a group that requires ecf one could either
> - include the ecf plug-in in a feature or
> - include a dependency on the plug-in in the feature ?
> Also, there is no ECF group then, right, ecf will appear below the
> p2.ui group only?
> I'm totally fine with the solution, just curious... :) Helmut
> -----Original Message-----
> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Pascal Rapicault
> Sent: Wednesday, April 01, 2009 5:00 PM
> To: P2 developer discussions
> Cc: P2 developer discussions; p2-dev-bounces@xxxxxxxxxxx
> Subject: Re: [p2-dev] ecf feature?
> The ECF plug-ins are required with a range (versus being included) by
> the p2 feature.
> Therefore the dependencies are here and p2 will properly bring down
> the necessary pieces.
> We did that to avoid blocking the ECF team with one particular
> That said we are still looking at expressing an optional dependency on
> our favorite version of ECF. We would likely do this using a p2.inf.
> Inactive hide details for "Haigermoser, Helmut" ---04/01/2009 10:14:57
> AM---Ciao Guys :) Just had a look at M6, looks like ther"Haigermoser,
> Helmut" ---04/01/2009 10:14:57 AM---Ciao Guys :) Just had a look at
> M6, looks like there is no feature listing ecf, is
> "Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
> "P2 developer discussions" <p2-dev@xxxxxxxxxxx>
> 04/01/2009 10:14 AM
> [p2-dev] ecf feature?
> Ciao Guys :)
> Just had a look at M6, looks like there is no feature listing ecf, is
> this OK or should I raise a bugzilla?
> The p2.ui feature has a dependency on ecf plug-ins but that's the only
> point where ecf is mentioned in any feature.xml in the SDK...
> This leads to a more general question, features translate into groups
> in p2, how do we maintain this knowledge if not by keeping features as
> a whole concept around for the time being, is p2.inf gonna fill this
> blank maybe?
> Ciao, hh
> p2-dev mailing list
> p2-dev mailing list
p2-dev mailing list