[
https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3525:
----------------------------------
OK so I've found a workflow that seems to work.
1. Install JBDS 9.0.0.CR1 (from
http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-stan... as
seen on
http://www.jboss.org/products/devstudio/download/ )
2. Install Arquillian 1.2.0.CR1 from
https://devstudio.redhat.com/9.0/development/updates/discovery.earlyacces...
3. After install & restart of JBDS, go to Window > Preferences > Install/Update
> Available Software Sites and delete or disable the above CR1 site. Leave only the
https://devstudio.redhat.com/9.0/stable/updates/ site enabled.
(this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1.
There's another way to achieve this using -D flags but it requires more cold starts of
JBDS.)
4. Now fire up Central and look for Arquillian. Yep, it's unavailable.
5. So, check the box for *Enable Early Access*. Still unavailable?
6. Now, check the box for *Show installed*. Voila! It's available and installable.
Alternate method (didn't try this but it should work if you don't like the above
method):
1. Install JBDS 9.0.0.CR1 (from
http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-stan... as
seen on
http://www.jboss.org/products/devstudio/download/ )
2. Add these to your jbdevstudio.ini or use them on the commandline when launching JBDS:
{code}
-Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/devstudio-directory.xml
-Djboss.discovery.site.url=https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/
-Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/{code}
3. Install Arquillian 1.2.0.CR1 from Central using the -D flag settings above.
4. Instead of restarting when prompted, shut down JBDS and remove the above -D flags to
revert to normal /stable/ settings and to see the latest updates from JBDS 9.0.0.CR1 ->
GA.
5. Now fire up Central and look for Arquillian. Yep, it's unavailable.
6. So, check the box for *Enable Early Access*. Still unavailable?
7. Now, check the box for *Show installed*. Voila! It's available and installable.
This feels like a workflow bug since you shouldn't be notified of available updates,
but then have Central hide those updates from you until you explicitly *Show installed*.
[~mickael_istria] [~fbricon] [~akazakov] WDYT? Something we should change in JBDS 9.x?
Problems updating Early Access content between milestones (eg.,
Arquillian from Beta1 -> CR1, CR1 -> GA)
--------------------------------------------------------------------------------------------------------
Key: JBDS-3525
URL:
https://issues.jboss.org/browse/JBDS-3525
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: arquillian
Affects Versions: 9.0.0.Beta2
Environment: Version: 9.0.0.CR1
Build id: CR1-v20150912-1100-B100
Build date: 20150912-1100
Enabled Early Access
Reporter: Marek Novotny
Assignee: Nick Boldt
Fix For: 9.0.1.GA, 10.0.0.Alpha1
JBDS notified me about a new update for Arquillian, but then after going into update it
complains about:
{noformat}
An error occurred while collecting items to be installed
session context was:(profile=jbds,
phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing:
osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19
No repository found containing:
osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19
No repository found containing:
osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19
No repository found containing:
org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)