]
Max Rydahl Andersen commented on JBDS-3360:
-------------------------------------------
no, the user exposed updatesite(s) should have the combined content, but the discovery
site would be what is in jbds 8.1 I would think. Since that is not actually listing
updatesite nor specific versions it should be fine imo.
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 :)