[
https://issues.jboss.org/browse/JBDS-2380?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2380:
-----------------------------
Attachment:
jbds2380-install-from-local-build-post-cr1a-after-scan-central-3-sites-shown.png
jbds2380-install-from-local-build-post-cr1a-ootb-only-two-sites-shown.png
Built locally, then using this in jbdevstudio.ini file:
{code}
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable_branch.updatesite/product/devstudio-directory.xml
{code}
OOTB on startup we see this:
!jbds2380-install-from-local-build-post-cr1a-ootb-only-two-sites-shown.png!
After scanning all of Central (except JRebel) we see this:
!jbds2380-install-from-local-build-post-cr1a-after-scan-central-3-sites-shown.png!
Need to verify everything can be *installed* next, using the B137 or later respin.
JBDS Central contains many refs to 3rd party sites after first
install request (checking for deps)
--------------------------------------------------------------------------------------------------
Key: JBDS-2380
URL:
https://issues.jboss.org/browse/JBDS-2380
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: central
Affects Versions: 6.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 6.0.0.CR1
Attachments:
central-does-add-background-sites-to-avail-software-sites-list-after-first-search.png,
central-does-not-add-background-sites-to-avail-software-sites-list-OOTB.png,
jbds2380-install-from-local-build-post-cr1a-after-scan-central-3-sites-shown.png,
jbds2380-install-from-local-build-post-cr1a-ootb-only-two-sites-shown.png,
JBDS2380-JBDS-central-points-to-JBT-site.fix.patch.txt,
jbds2380-notes-features-with-update-tags-JBT-target-platformSR1a.txt,
jbds2380-notes-features-with-update-tags.txt,
JBDS2380-SR1a-after-scanning-all-sites-in-Central-except-JRebel.png, repoDump.txt
See screenshots.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira