|
|
| Re: Making p2 repos with PDE structured with categories and IUs [message #114669 is a reply to message #114656] |
Fri, 18 July 2008 20:43  |
 Francis Upton IV
Messages: 472
Registered: July 2009
Location: Oakland, CA |
Senior Member |
|
|
Thanks for that, that's what I want. And it occurs to me, I can
probably just build my own content.xml file the way I want it (using my
build environment). One question though, how important are the "size"
attributes? Are they just an optimization or are they required?
Thanks again,
Francis
Pascal Rapicault wrote:
> I have built the attached example manually and it does what you are looking
> for wrt to the nesting.
> However it does not get rid of the uncategorized category
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=227675
> If you feel like hacking something around this last bug please dont'
> hesitate
>
> "Francis Upton (News)" <francisu@ieee.org> wrote in message
> news:g5q28t$5ba$1@build.eclipse.org...
>> I have a headless build, and I want to make a p2 repos to do
>> installations from.
>>
>> I want it to look like this:
>>
>> Category1
>> Product1 IU
>> Product2 IU
>> Category1a
>> Feature1 IU (not an executable product)
>> Feature2 IU (as above)
>> Category1c
>> ...
>>
>> I tried the default p2 metadata generation and was not able to get
>> something like Category1a, I tried making Category1a as a product with
>> the Feature1 and Feature2, but show features did not show through in the
>> categories.
>>
>> It also creates this very unsatisfying "Uncategorized" category where it
>> puts all of the features. I don't want this category at all. And I
>> don't consider most of my features as separate IUs.
>>
>> I guess what I want is some more flexibility in the p2 metadata
>> generation to specify my own categories and specify the IUs that go
>> under them (which may or may not be based on products). As far as I
>> know there does not seem to be a way to do this. I'm considering
>> patching the p2 metadata generator to allow this flexibility.
>>
>> I guess an alternative is to use the old update site stuff and then
>> generate the p2 data from that, but I want to avoid that if possible
>> (when I tried to generate an update site a while ago, I had trouble with
>> that -- I think mainly due to my ignorance).
>>
>> Are there other alternatives?
>>
>>
>> --
>> *new* Common Navigator Framework section in:
>> 3.4RC4 Platform Plugin Developer Guide (Programmer's Guide)
>> http://help.eclipse.org/ganymede/topic/org.eclipse.platform. doc.isv/guide/cnf.htm
>> http://dev.eclipse.org/blogs/francis
>> http://wiki.eclipse.org/Common_Navigator_Framework
>> http://wiki.eclipse.org/Common_Navigator_Framework_Use_Cases
>>
>>
>> You have brains in your head.
>> You have feet in your shoes.
>> - Dr Seuss, Oh the Places You'll Go
>
>
--
*new* Common Navigator Framework section in:
3.4RC4 Platform Plugin Developer Guide (Programmer's Guide)
http://help.eclipse.org/ganymede/topic/org.eclipse.platform. doc.isv/guide/cnf.htm
http://dev.eclipse.org/blogs/francis
http://wiki.eclipse.org/Common_Navigator_Framework
http://wiki.eclipse.org/Common_Navigator_Framework_Use_Cases
You have brains in your head.
You have feet in your shoes.
- Dr Seuss, Oh the Places You'll Go
Platform UI Committer for Common Navigator
http://wiki.eclipse.org/index.php/Common_Navigator_Framework
http://help.eclipse.org/galileo/topic/org.eclipse.platform.d oc.isv/guide/cnf.htm
|
|
|
Powered by
FUDForum. Page generated in 0.03604 seconds
] 
Search
Help
Register
Login
Home
