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

Denis Golovin (JIRA) issues at jboss.org
Fri Dec 18 13:40:00 EST 2015


    [ https://issues.jboss.org/browse/JBIDE-21368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143089#comment-13143089 ] 

Denis Golovin commented on JBIDE-21368:
---------------------------------------

Under windows ~/jboss-runtimes are still not scanned, see test failures http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master_otherOS/ uder windows configuration.

{code}Error Message

expected:<1> but was:<0>
Stacktrace

junit.framework.AssertionFailedError: expected:<1> but was:<0>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)
	at junit.framework.Assert.assertEquals(Assert.java:78)
	at junit.framework.Assert.assertEquals(Assert.java:234)
	at junit.framework.TestCase.assertEquals(TestCase.java:401)
	at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
{code}

> 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.Beta1, 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