[jbosstools-issues] [JBoss JIRA] (JBDS-2402) ensure BYOE feature provides URL from which to update, and cleans up URLs when uninstalled

[Nick Boldt (JIRA)]

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

Nick Boldt resolved JBDS-2402.
------------------------------

    Resolution: Done


Resolving. To be closed after QE verification as noted in previous comment.
                
> ensure BYOE feature provides URL from which to update, and cleans up URLs when uninstalled 
> -------------------------------------------------------------------------------------------
>
>                 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_v2.txt, JBDS2402-40x.patch_v3.txt, JBDS2402-JBDS2371.patch_v2.txt, JBDS2402-JBDS2371.patch_v3.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