[jbosstools-issues] [JBoss JIRA] (JBDS-2402) ensure BYOE feature provides URL from which to update

Nick Boldt (JIRA) jira-events at lists.jboss.org
Tue Nov 27 11:02:21 EST 2012


     [ https://issues.jboss.org/browse/JBDS-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBDS-2402:
-----------------------------

    Attachment: JBDS2402-40x.patch.txt
                JBDS2402-JBDS2371.patch.txt


Assumptions:

a) Max would prefer to not have the staging URL in the installed product today (CR1x)

b) GA version should DEFINITELY not reference the staging site, and should in fact REMOVE it should you update from pre-GA to GA

c) we won't likely be dropping CR1x to Early Access since we're in fact doing a CR1b this week instead

d) JBDS-2371 was rejected (but apparently my patch slipped in somehow *in trunk only*)

Therefore, new patches to approve:

Trunk: [^JBDS2402-JBDS2371.patch.txt]
60x branch: [^JBDS2402-40x.patch.txt]

You'll note that now, on installation, the /6.0/ URL is added and the /6.0-staging/ URL is removed. On uninstallation, both URLs are removed (just in case).

                
> 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-40x.patch.txt, jbds2402-add-touchpoints.patch.txt, JBDS2402-JBDS2371.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


More information about the jbosstools-issues mailing list