Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » PDE Build, P2 metadata: Category setup, site.xml
PDE Build, P2 metadata: Category setup, site.xml [message #43096] Thu, 29 January 2009 20:09 Go to next message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1341
Registered: July 2009
Senior Member
I promise this is the last one today -- didn't want to get threads
confused. :D Any thoughts/hints on the following would be greatly
appreciated..even the url for a good example build as the one's I'm
coming up w/ only build raw features:

I can't grok how to get categories created properly. I can generate the
update site just fine using the built in p2 support, but there don't
appear to be any hooks for specifying categories. To be clear, here I'm
talking about the broad categories that show up under p2 Install, e.g.
"Models and Model Development" "OpenArchitectureWare", etc..

My reading of newsgroup and wiki traffic is that that has to happen
through a site.xml file. (Which I thought was a p1 mechanism, but
anyway..) OK, but I'm also seeing that the site.xml file is *not*
produced by the PDE Build p2 generator. So that means that we have to
create and synchronize the site.xml file manually? But the site file
isn't finding the artifacts created in the target PDE Build P2 site.
Does this mean that we actually need to edit the site.xml file by hand
with the new version information every time we do a release?
Re: PDE Build, P2 metadata: Category setup, site.xml [message #44300 is a reply to message #43096] Tue, 03 February 2009 19:20 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Try M5, generation from site.xml is a little shaky and still needs work.

We introduced a property "p2.category.site" (starting in pde.build
v20090105) which is a url to a site.xml to generate categories from.
However, build has never managed site.xml files and doesn't touch
versions in them.

The metadata.generator starting in v20090203 can handle .qualifier so
you wouldn't need specific versions in the site.xml (the category will
get versions based on the features it has seen.

-Andrew

Miles Parker wrote:
>
> I promise this is the last one today -- didn't want to get threads
> confused. :D Any thoughts/hints on the following would be greatly
> appreciated..even the url for a good example build as the one's I'm
> coming up w/ only build raw features:
>
> I can't grok how to get categories created properly. I can generate the
> update site just fine using the built in p2 support, but there don't
> appear to be any hooks for specifying categories. To be clear, here I'm
> talking about the broad categories that show up under p2 Install, e.g.
> "Models and Model Development" "OpenArchitectureWare", etc..
>
> My reading of newsgroup and wiki traffic is that that has to happen
> through a site.xml file. (Which I thought was a p1 mechanism, but
> anyway..) OK, but I'm also seeing that the site.xml file is *not*
> produced by the PDE Build p2 generator. So that means that we have to
> create and synchronize the site.xml file manually? But the site file
> isn't finding the artifacts created in the target PDE Build P2 site.
> Does this mean that we actually need to edit the site.xml file by hand
> with the new version information every time we do a release?
>
Re: PDE Build, P2 metadata: Category setup, site.xml [message #46383 is a reply to message #44300] Tue, 10 February 2009 22:18 Go to previous message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1341
Registered: July 2009
Senior Member
Thanks Andrew, the 0205 build handled qualifiers perfectly. I think I
may actually have an honest-to-goodness automated build solution now!

On 2009-02-03 11:20:11 -0800, Andrew Niefer <aniefer@ca.ibm.com> said:

> Try M5, generation from site.xml is a little shaky and still needs work.
>
> We introduced a property "p2.category.site" (starting in pde.build
> v20090105) which is a url to a site.xml to generate categories from.
> However, build has never managed site.xml files and doesn't touch
> versions in them.
>
> The metadata.generator starting in v20090203 can handle .qualifier so
> you wouldn't need specific versions in the site.xml (the category will
> get versions based on the features it has seen.
>
> -Andrew
>
> Miles Parker wrote:
>>
>> I promise this is the last one today -- didn't want to get threads
>> confused. :D Any thoughts/hints on the following would be greatly
>> appreciated..even the url for a good example build as the one's I'm
>> coming up w/ only build raw features:
>>
>> I can't grok how to get categories created properly. I can generate the
>> update site just fine using the built in p2 support, but there don't
>> appear to be any hooks for specifying categories. To be clear, here I'm
>> talking about the broad categories that show up under p2 Install, e.g.
>> "Models and Model Development" "OpenArchitectureWare", etc..
>>
>> My reading of newsgroup and wiki traffic is that that has to happen
>> through a site.xml file. (Which I thought was a p1 mechanism, but
>> anyway..) OK, but I'm also seeing that the site.xml file is *not*
>> produced by the PDE Build p2 generator. So that means that we have to
>> create and synchronize the site.xml file manually? But the site file
>> isn't finding the artifacts created in the target PDE Build P2 site.
>> Does this mean that we actually need to edit the site.xml file by hand
>> with the new version information every time we do a release?
Re: PDE Build, P2 metadata: Category setup, site.xml [message #591197 is a reply to message #43096] Tue, 03 February 2009 19:20 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Try M5, generation from site.xml is a little shaky and still needs work.

We introduced a property "p2.category.site" (starting in pde.build
v20090105) which is a url to a site.xml to generate categories from.
However, build has never managed site.xml files and doesn't touch
versions in them.

The metadata.generator starting in v20090203 can handle .qualifier so
you wouldn't need specific versions in the site.xml (the category will
get versions based on the features it has seen.

-Andrew

Miles Parker wrote:
>
> I promise this is the last one today -- didn't want to get threads
> confused. :D Any thoughts/hints on the following would be greatly
> appreciated..even the url for a good example build as the one's I'm
> coming up w/ only build raw features:
>
> I can't grok how to get categories created properly. I can generate the
> update site just fine using the built in p2 support, but there don't
> appear to be any hooks for specifying categories. To be clear, here I'm
> talking about the broad categories that show up under p2 Install, e.g.
> "Models and Model Development" "OpenArchitectureWare", etc..
>
> My reading of newsgroup and wiki traffic is that that has to happen
> through a site.xml file. (Which I thought was a p1 mechanism, but
> anyway..) OK, but I'm also seeing that the site.xml file is *not*
> produced by the PDE Build p2 generator. So that means that we have to
> create and synchronize the site.xml file manually? But the site file
> isn't finding the artifacts created in the target PDE Build P2 site.
> Does this mean that we actually need to edit the site.xml file by hand
> with the new version information every time we do a release?
>
Re: PDE Build, P2 metadata: Category setup, site.xml [message #591797 is a reply to message #44300] Tue, 10 February 2009 22:18 Go to previous message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1341
Registered: July 2009
Senior Member
Thanks Andrew, the 0205 build handled qualifiers perfectly. I think I
may actually have an honest-to-goodness automated build solution now!

On 2009-02-03 11:20:11 -0800, Andrew Niefer <aniefer@ca.ibm.com> said:

> Try M5, generation from site.xml is a little shaky and still needs work.
>
> We introduced a property "p2.category.site" (starting in pde.build
> v20090105) which is a url to a site.xml to generate categories from.
> However, build has never managed site.xml files and doesn't touch
> versions in them.
>
> The metadata.generator starting in v20090203 can handle .qualifier so
> you wouldn't need specific versions in the site.xml (the category will
> get versions based on the features it has seen.
>
> -Andrew
>
> Miles Parker wrote:
>>
>> I promise this is the last one today -- didn't want to get threads
>> confused. :D Any thoughts/hints on the following would be greatly
>> appreciated..even the url for a good example build as the one's I'm
>> coming up w/ only build raw features:
>>
>> I can't grok how to get categories created properly. I can generate the
>> update site just fine using the built in p2 support, but there don't
>> appear to be any hooks for specifying categories. To be clear, here I'm
>> talking about the broad categories that show up under p2 Install, e.g.
>> "Models and Model Development" "OpenArchitectureWare", etc..
>>
>> My reading of newsgroup and wiki traffic is that that has to happen
>> through a site.xml file. (Which I thought was a p1 mechanism, but
>> anyway..) OK, but I'm also seeing that the site.xml file is *not*
>> produced by the PDE Build p2 generator. So that means that we have to
>> create and synchronize the site.xml file manually? But the site file
>> isn't finding the artifacts created in the target PDE Build P2 site.
>> Does this mean that we actually need to edit the site.xml file by hand
>> with the new version information every time we do a release?
Previous Topic:OSGi running my own embedded Jetty, dependent plugins not starting?
Next Topic:How to test my plugin
Goto Forum:
  


Current Time: Tue Mar 19 03:07:22 GMT 2024

Powered by FUDForum. Page generated in 0.02473 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top