[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [p2-dev] Does the p2 publisher understand OSGi Provide-Capability / Require-Capability ?
|
Hi Tobias,
Thanks for following up. Yes, after some trial and error I got it working and this was my solution:
http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/commit/?id=972ab04adee81615d09beebe9b3798eeb862395c
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberlies, Tobias
Sent: Monday, June 23, 2014 5:08 PM
To: P2 developer discussions
Subject: Re: [p2-dev] Does the p2 publisher understand OSGi Provide-Capability / Require-Capability ?
See below
Martin Oberhuber wrote:
> Thanks Pascal and Tom,
>
> Reading the bug got me pointed to p2.inf :
> https://wiki.eclipse.org/Equinox/p2/Customizing_Metadata
>
> What I really want to accomplish is this:
> - I depend on org.eclipse.cdt.core
> - I want to make sure that besides cdt.core , all its related
> fragments (that match my host) are also installed
> (org.eclipse.cdt.core.win32 and 8 or so others)
> - CDT only just recently added a feature holding the fragments +
> fragment-host, I want a solution that works with older CDT
> - See https://bugs.eclipse.org/bugs/show_bug.cgi?id=435150
>
> It looks like a p2.inf in my bundle with a
> metaRequirements.<#>.matchExp might do the trick, when I require all
> org.eclipse.cdt.core.* IU’s with optional=true and greedy=true. But I
> don’t see the matchExp syntax from the docs …
I suppose you can get help with the syntax here: http://wiki.eclipse.org/Query_Language_for_p2
Note: You do *not* want to use "metaRequirements", but rather regular "requirements". Meta requirements are for requirements on the installer/director and not for requirements of your artifact. When using metaRequirements, your installation will be broken when using a separate runtime for the director.
>
> What do you think, could this idea work and can you point me to
> follow-on docs on matchExp ?
AFAIK, you got this working, right?
Regards
Tobias
>
> Thanks,
> Martin
> --
> Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
> direct +43.662.457915.85 fax +43.662.457915.6
>
> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Thomas Watson
> Sent: Wednesday, May 28, 2014 5:48 PM
> To: P2 developer discussions
> Subject: Re: [p2-dev] Does the p2 publisher understand OSGi Provide-
> Capability / Require-Capability ?
>
> Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=313553
>
> Tom
>
>
>
> Pascal Rapicault ---05/28/2014 10:25:29 AM---No. Contributions or
> contract welcome. On 05/28/2014 10:56 AM, Oberhuber, Martin wrote:
>
> From: Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx>
> To: P2 developer discussions <p2-dev@xxxxxxxxxxx>
> Date: 05/28/2014 10:25 AM
> Subject: Re: [p2-dev] Does the p2 publisher understand OSGi Provide-
> Capability / Require-Capability ?
> Sent by: p2-dev-bounces@xxxxxxxxxxx
> ________________________________________
>
>
>
> No. Contributions or contract welcome.
> On 05/28/2014 10:56 AM, Oberhuber, Martin wrote:
> Hi p2 experts,
>
> I just recently read about the generic OSGi Provide-Capability /
> Require- Capability headers in MANIFEST.MF .
>
> I was wondering whether the p2 publisher understands those and
> translates them into install-time dependencies in the content.jar /
> artifacts.jar of a repository ?
>
> Any insight appreciated !
>
> Thanks,
> Martin
> --
> Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
> direct +43.662.457915.85 fax +43.662.457915.6
>
>
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev