[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Eclipse 3.4.1 and P2 repository

1) In 3.4, the way we did it is by storing preference files in the configuration folder (take a look at the 3.4 SDK). You may be able to do some tricks with features or sites and their URL but I don't precisely recall. John?
2) If you mean that you don't see the nested features in the installed software list, this is expected. p2 only shows what has explicitly been installed. This is to simplify the user experience. In 3.5 we are now showing the nested things but I'm not a big fan of it.

Inactive hide details for Richard ---04/02/2009 08:12:01 AM---In Eclipse 3.4.1 I've got the P2 repository created from the PDE Richard ---04/02/2009 08:12:01 AM---In Eclipse 3.4.1 I've got the P2 repository created from the PDE headless build. I use the director


From:

Richard <rjkoop@xxxxxxxxx>

To:

p2-dev@xxxxxxxxxxx

Date:

04/02/2009 08:12 AM

Subject:

[p2-dev] Eclipse 3.4.1 and P2 repository




In Eclipse 3.4.1 I've got the P2 repository created from the PDE headless build.  I use the director to install the full RCP app and see the IU in the 'Install/Update' list.  I have 2 questions.
1. How can I automatically populate the 'Update sites' list for the user in Eclipse 3.4.1?
  Looks like the p2.inf 'addRepository' command is not supported until Eclipse 3.5.
2. When installing a feature based product, how come Eclipse/P2 doesn't know that the feature has been installed?
  The only IU I see is the product, not the contained features.  Eclipse/P2 doesn't think that the contained feature has been installed.
 
Richard
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


GIF image

GIF image