[
https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3360:
----------------------------------
Per the call today, I've mocked up a composite site with 8.0x/8.1 versions of JBDS AND
all 4 versions of Central, too.
*
https://devstudio.redhat.com/updates/8.0-staging-JBDS-3360/
To use, launch JBDS with thesr commandline params or add them to jbdevstudio.ini.
{code}
-Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-staging-JBDS-3360/
-Djboss.discovery.directory.url=https://devstudio.redhat.com/updates/8.0-staging-JBDS-3360/devstudio-directory.xml
{code}
Today, 8.0 user tries to install HMT w/ Tern 0.8.2 and forces partial install (first
remediation choice) or upgrade to 8.1.Beta1 (second remediation choice); in future we
should not need remediation at all. ( JBDS-3359 )
TODO:
* verify p2 can offer installation of HMT w/ Tern 0.6 on 8.0, or 0.8.2 on 8.1.Beta1
* verify downgrade/uninstall is possible too, including rolling back stuff from
Central
* verify 8.0 user w/ HMT already installed can Help > Check for updates and get all
JBDS & Central stuff upgraded at the same time (not two steps)
* benchmark performance of Check for updates vs. from this composite site
* benchmark performance of reading Central discovery catalogue vs. from this composite
site
* benchmark performance of installing HMT w/ tern 0.6 and 0.82 vs. from this composite
site
Align bits offered in JBoss Central with installed version of JBDS
------------------------------------------------------------------
Key: JBDS-3360
URL:
https://issues.jboss.org/browse/JBDS-3360
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: central, updatesite
Affects Versions: 8.0.2.GA
Reporter: Martin Malina
Fix For: 8.1.0.CR1
The problem in JBDS-3359 shows a broader issue.
(That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2
has already been released and central points to it.)
Currently when you install JBDS 8.0.0, it will contain this update site in Preferences
-> Available Software Sites:
https://devstudio.redhat.com/updates/8.0/
Initially this update site contained JBDS 8.0.0 core + 8.0.0 central.
But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update
was offered to users in Eclipse. And we started to have two groups of users:
1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits
2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits)
Wouldn't it make more sense if central used the same version that is currently
installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0
also.
I'm not sure if this is doable or makes sense at all, so I'm looking forward to
feedback :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)