Description of problem: (Related to https://bugzilla.redhat.com/show_bug.cgi?id=960602) See the attached screenshot - can we clean up the list of available runtimes - either by removing the obsolete runtimes, or presenting them to the users in a list that separates community from product from snapshots? It's a long list right now. Version-Release number of selected component (if applicable): JBDS: jbdevstudio-product-universal-6.0.1.GA-v20130327-2052-B361.jar JBDS SOA Tooling: http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/aggregate/4.0.0/ SOA: http://jawa05.englab.brq.redhat.com/candidate/soa-6.0.0-DR3/ Maven repo: http://jawa05.englab.brq.redhat.com/candidate/soa-6.0.0-DR3/soa-6.0.0-Alpha-maven-repository.zip EAP: http://download.devel.redhat.com/released/JBEAP-6/6.1.0-Beta/ How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 745283 [details] Runtime screenshot
The tools should now only display versions in the users local m2 repository, the default version (latest community release) and the versions installed in any SwitchYard runtimes configured in the user's workspace.
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1738 pushed
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1795 pushed
Created attachment 838412 [details] How it looks in JBDS-IS 7.0.0.CR1
Verified with JBDS-IS 7.0.0.CR1
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1795 to Closed