[jbosstools-issues] [JBoss JIRA] (JBIDE-21368) jboss-runtimes are still not scanned under windows

Rob Stryker (JIRA) issues at jboss.org
Wed Dec 23 14:21:00 EST 2015


     [ https://issues.jboss.org/browse/JBIDE-21368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-21368.
---------------------------------
    Resolution: Done


https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master_otherOS/34/

Pushed to master and 4.3.x.  Problem was a missing waitForIdle() at the beginning of the test

> jboss-runtimes are still not scanned under windows
> --------------------------------------------------
>
>                 Key: JBIDE-21368
>                 URL: https://issues.jboss.org/browse/JBIDE-21368
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: runtime-detection
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>             Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> JBDS-2515 requested that ~/jboss-runtimes would be scanned but seem to have ended up being to only add this on new workspaces and *only* if the location exist when creating the new workspace.
> I found no way to have restore defaults or any way to actually have the scan happen.
> Why are we not always adding ~/jboss-runtimes to the list of locations to scan no matter if the location exists or not ?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list