[
https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3360:
----------------------------------
Having a mix of 8.0.0, 8.0.1, 8.0.2, 8.1.0, 8.1.x in the same site will impact performance
(more metadata = slower to parse when looking for updates).
But it would also allow us to empower users to rollback from 8.1 to 8.0, or to install an
older version of Tern/Thym/AngularJS than what's in the latest JBDS 8.1 if they want
something compatible w/ an older release.
So... there are pros and cons here.
Perhaps this question needs to be put to GSS (more support scenarios like "I was
running 8.0, updated to 8.1, then rolled back and now I can't use AngularJS" [for
example]) as well as QE (more testcase scenarios).
OTOH, if there's no reason to upgrade, people won't. So we might end up with lots
of duplicate GSS support questions around problems in Eclipse Luna R or SR1 which were
fixed in SR2. If we encourage/force users to upgrade, they get a better JBDS, and the
reports of problems in old versions SHOULD go away.
I'm not adverse to the idea, I just want everyone to know what COULD be the
consequence of doing so. :D
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
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)