Plugins IU directly in category.xml [message #868734] |
Wed, 02 May 2012 13:14 |
|
Hi all,
I want to put directly plugins in my category.xml (I don't want to use
features for those plugins, that I don't own, I just want to mirror
them, they are available in Orbit without feature).
I know p2 can publish directly plugins. I noticed category.xml editor
does not provide entry for Plugins,
So, simple question:
Is there a way (independently of category editor) to add plugins in
category.xml ?
The goal, ultimately, would be to support it also in Tycho.
Thanks in advance.
Mickael
|
|
|
|
|
Re: Plugins IU directly in category.xml [message #868787 is a reply to message #868768] |
Wed, 02 May 2012 14:35 |
|
>> I think it's also possible to list units directly. But I'm not sure
>> if/where it's documented properly. I discovered the query feature by
>> looking at the source code.
>
> Will have a look at source then.
I found the UI part in org.eclipse.pde.internal.core.idite, but nothing
related to Queries or bundles as IU.
Which class gave you hints for queries?
|
|
|
Re: Plugins IU directly in category.xml [message #868843 is a reply to message #868787] |
Wed, 02 May 2012 16:09 |
|
Found org.eclipse.equinox.internal.p2.updatesite package.
The <iu id="bundle.name"> element looks promising, but it looks like
CategoryPublisher application only works on existing repository and is
only good at organizing an already existing repo.
What I want is to create a repo and publish some plugins in it, without
making them part of a feature.
But I also found that Tycho seems to use its own implementation, based
on ContextValue "TychoConstants.CTX_PUBLISHED_ROOT_IUS", use by
AssembleRepositoryMojo, to invoke MirrorAppicaiton and
MirrorApplicationServiceImpl....
Both Headless command and Tycho Mojo rely on the CategoryXMLAction and
SiteXMLAction for that. SiteXMLAction seems to perform some cool stuff
for <iu> but I can't get it to work.
Any help on its usage would be very welcome.
|
|
|
|
Re: Plugins IU directly in category.xml [message #869420 is a reply to message #868843] |
Thu, 03 May 2012 11:24 |
|
Hi Mickael,
Am 02.05.2012 18:09, schrieb Mickael Istria:
> The <iu id="bundle.name"> element looks promising, but it looks like
> CategoryPublisher application only works on existing repository and is
> only good at organizing an already existing repo.
That's how it works. The p2 category Ant task (and application) takes
any existing p2 repository and adds categories to it (depending on a
given category.xml).
> What I want is to create a repo and publish some plugins in it, without
> making them part of a feature.
So you don't need categories for this. You can simply mirror or publish
any plug-in to any repository. Features are really just a way to group
bundles. My understanding was that you wanted to have categories as a
way to use "groups" of bundles in a Target Platform (or so).
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxx
http://wagenknecht.org/
|
|
|
Re: Plugins IU directly in category.xml [message #870771 is a reply to message #869420] |
Wed, 09 May 2012 15:15 |
|
On 05/03/2012 01:24 PM, Gunnar Wagenknecht wrote:
>> What I want is to create a repo and publish some plugins in it, without
>> making them part of a feature.
>
> So you don't need categories for this. You can simply mirror or publish
> any plug-in to any repository. Features are really just a way to group
> bundles.
But there is no way to do it by editing a category.xml file, isn't
there? I'll need to use p2 tasks or scripts (which I tried to avoid as
much as possible in our Tycho-based build process).
> My understanding was that you wanted to have categories as a
> way to use "groups" of bundles in a Target Platform (or so).
Sorry if I was not clear. What I want is to give a category.xml
containing a bundle that is not part of a feature to Tycho and get as
result a repository which contain the IU for this bundle.
--
Mickael Istria
JBoss, by Red Hat
My blog: http://mickaelistria.wordpress.com
My Tweets: http://twitter.com/mickaelistria
|
|
|
|
Powered by
FUDForum. Page generated in 0.03679 seconds