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

You are correct, features can still carry a URL (note that the feature editor is the same one that you've always known and has not been adapted to support p2 metadata, which explain why this field and many others are still here). The thing that differs from UM is what happens to those URLs. In UM they were known from the system as soon as the feature was "configured". Consequently the only way to get rid of feature URL was to either get rid of the feature or have the policy.xml.
In p2, those URLs are not added automatically to the repo managers just because the feature is installed. Instead, those URLs are transformed into site references listed into the p2 repository where the feature is accessible. Therefore, since those URLs are listed explicitly in the p2 repo, editing the content.xml is enough to control what you make available.

I think that for the features you are in control of, it is a good practice to get rid of the URL in the features.

PaScaL

Inactive hide details for "Mark Melvin" ---05/09/2009 10:34:49 AM---It's possible I'm having a brain fart but isn't the update "Mark Melvin" ---05/09/2009 10:34:49 AM---It's possible I'm having a brain fart but isn't the update site URL still encoded in the features (in feature.xml), or is that


From:

"Mark Melvin" <Mark.Melvin@xxxxxxxxxx>

To:

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

Date:

05/09/2009 10:34 AM

Subject:

RE: [p2-dev] policy.xml Replacement?




It's possible I'm having a brain fart but isn't the update site URL still encoded in the features (in feature.xml), or is that ignored by P2? I recall seeing an update id in the metadata, usually the same as the IU id. I guess that's all you need, and your update site can be anywhere.

What should I do about the URL in feature.xml? Leave it out completely, or point to a dummy location?

Thanks for the replies,
Mark.


From: Nick Boldt [mailto:nickboldt@xxxxxxxxx]
Sent:
Sat 09/05/2009 3:52 AM
To:
P2 developer discussions
Cc:
Mark Melvin
Subject:
Re: [p2-dev] policy.xml Replacement?

See also http://wiki.eclipse.org/Using_Policy_Files

Pascal Rapicault wrote:
> 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
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev

--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
Release Engineer :: Eclipse Modeling & Dash Athena_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

GIF image

GIF image