Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Indigo site not pre-configured in packages ?

> "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
> BTW I also noticed that some featues still specify a helios update
> site in their feature.xml, e.g. the JSDT feature
>    <url>
>       <update label="%updateSiteName" url=""> > download.eclipse.org/webtools/repository/helios"/>
>    </url>
> My understanding is that this isn't relevant since this setting
> isn't used any more with p2 ?

Right, this is an obsolete concept. The better way to do this is to configure it at the product level, rather than at feature granularity. If a product is consuming/distributing your features, they may want to control where the updates come from. For backwards compatibility the p2 publisher will convert feature update references into repository references in the repository you publish the feature into.

John

Back to the top