[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Equivalent of Update Policy for P2

The design of p2 obsoletes this UM concept that was needed because each feature had a pointer back home in the feature.xml. In p2 since IUs are repository free, you achieve this by controlling the set of repositories you are making available (IMetadataRepositoryManager and IArtifactRepositoryManager).

Inactive hide details for "Daffin, Miles \(IT\)" ---07/22/2008 07:28:35 AM---Hi All, In 3.3 I could ensure that users could onl"Daffin, Miles \(IT\)" ---07/22/2008 07:28:35 AM---Hi All, In 3.3 I could ensure that users could only update features from our internal mirror sites.


From:

"Daffin, Miles \(IT\)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>

To:

"P2 developer discussions" <p2-dev@xxxxxxxxxxx>

Date:

07/22/2008 07:28 AM

Subject:

[p2-dev] Equivalent of Update Policy for P2




Hi All,

In 3.3 I could ensure that users could only update features from our internal mirror sites. Can anyone explain how I would do this with P2? (This seems like a gaping hole.)

Thanks,

Miles

Miles Daffin
Morgan Stanley | Technology

20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572

Miles.Daffin@xxxxxxxxxxxxxxxxx



NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error._______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


GIF image

GIF image