[
https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2402:
--------------------------------------
[~nickboldt]: I would rather see it put into the BYOE / Core Features
feature, so that anyone who's installed from Marketplace can also get updates from the
site on
devstudio.jboss.com.
Big *+1*. IMO, the product feature should only contain product-related stuff (Id, splash
& co). All other JBDS stuff (URLs for Central, URL for updates...) should go to the
BYOE feature, since it's included in the product.
[~maxandersen]: I dont grok why you want to add any mention of
devstudio.jboss.com staging servers in these p2-infs ?
This patch removes usage of the staging site in GA. We've used the staging site in
Alpha releases since this was the only existing JBDS 6 repo at this time.
Maybe we could have set both site (staging and GA) in all versions, and just ensure we
delete the staging site when we publish the GA site. So in all case, user gets ability to
update from a staging to another staging, or from a staging to a GA.
ensure BYOE feature provides URL from which to update
------------------------------------------------------
Key: JBDS-2402
URL:
https://issues.jboss.org/browse/JBDS-2402
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-b
Fix For: 6.0.0.CR1, 6.0.0.GA
Attachments: jbds2402-add-touchpoints.patch.txt
We recently removed 'org.eclipse.equinox.p2.touchpoint.eclipse.addRepository'
touchpoints from *p2.inf files in JBDS, and the result is that until a user scans
Central's update site, there are no entries listed in the Available Software Sites
pref page.
So, we need to ensure that this is added back in.
Rather than putting it in the JBDS Branded Product feature, however, I would rather see
it put into the BYOE / Core Features feature, so that anyone who's installed from
Marketplace can also get updates from the site on
devstudio.jboss.com. We can also use
this mechanism to replace the 6.0-staging site (currently in Marketplace) by the 6.0 site
(once we go GA) and clean the old site out of users' Eclipse installs so they only get
updates from the official site, not the staging one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira