[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Question concerning feature update site URLs...
|
We recently dropped both <update> and <discovery> from our features in
JBoss Tools, because in order to have the user see these URLs, they have
to first install the feature (from a mirror site or zip), thus negating
the need to advertise where the feature came from.
<discovery> gets added *when the feature is fully installed* as a
_disabled_ update site
<update> gets added *when the feature is fully installed* as an
_enabled_ update site; if it's the same URL as the site from which the
feature was installed, it's therefore redundant.
A better approach, if you want to force the user to get p2 repos added
as associate sites *when reading the repo*, rather than *after
installing the feature*, then read this:
http://divby0.blogspot.com/2010/03/athena-p2-repos-w-associate-sites.html
The actual magic is simply to append some information into the
content.xml file - see "add.associate.sites" task in
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml?root=Technology_Project&view=markup.
Nick
On 04/20/2010 10:56 AM, Eric Gwin wrote:
Hi,
I'd like to ask a few questions to the group regarding P2 repo and
feature generation:
What are the expected values for the repo URLs used in the features?
<url>
<update label="%updateSiteName" url="%primaryUpdateURL"/>
<discovery label="%secondaryUpdateSiteName" url="%secondaryUpdateURL"/>
</url>
From experience it can be any valid URL, and specifically a valid
update site. I'm asking what I should
be putting in there since I am only generating the features once and the
repos are mirrored from our
project update site(s) to our simultaneous release update site.
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
