[
https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin....
]
Martin Malina commented on JBDS-3360:
-------------------------------------
OK, I take that back. I tried this again now:
1. Start JBDS 8.0.2, install Hybrid Mobile Tools from Central, stop JBDS
2. Add this 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}
3. Start JBDS and add this to the available SW sites:
{code}
https://devstudio.redhat.com/updates/8.0-staging-JBDS-3360/
{code}
Note: At this point, I still have com.jboss.devstudio.core.feature_8.0.2.GA installed.
4. Check for updates. Available Updates window will show up: JBDS will offer Cordova Sim,
Thym, AngularJS and Mobile Browser Sim to be updated.
5. Click Next: Update Details: This will suddenly add JBDS 8.1.0.Beta1 product to the list
(I missed this last time.)
So yeah, after the first update, I will already have everything updated to 8.1.0.Beta1,
including the hybrid tools installed via Central. But [~nickboldt], do you understand why
on the first window (Step 4) JBDS product is not listed to be updated? That confused me.
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
Assignee: Martin Malina
Fix For: 8.1.0.CR1
Attachments: beta1-composite-remediation.png,
JBDS3360_staging_site_contains_Beta1.png
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)