[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] policy.xml Replacement?

p2 can do without the policy.xml file because the metadata is location agnostic, whereas features always had a pointer back home.
Consequently you simply control what is accessible by controlling the list of repositories available to the user.
That said, you also have to be careful to the repositories referred to from within the repositories listed because some of them may include references to additional repos. This is especially true when the repository you are accessing results from the transformation of an old style update site where features listed URL of repos (this addition of reference repo is done for backward compatibility reasons).

HTH

PaScaL
Inactive hide details for "Mark Melvin" ---05/08/2009 10:21:33 AM---Hi Everyone,"Mark Melvin" ---05/08/2009 10:21:33 AM---Hi Everyone,


From:

"Mark Melvin" <Mark.Melvin@xxxxxxxxxx>

To:

<p2-dev@xxxxxxxxxxx>

Date:

05/08/2009 10:21 AM

Subject:

[p2-dev] policy.xml Replacement?




Hi Everyone,

Is there a replacement or equivalent workflow for the old policy.xml
file that was available in the old update manager?  This made it really
easy to test update scenarios for installed, immutable features
referencing an external URL by re-wiring all URLs to locally accessible
resources.

Thanks,
Mark.
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


GIF image

GIF image