[jbosstools-issues] [JBoss JIRA] (JBIDE-17996) Server Runtime Environment wizard says "C:standalone" even if corrected

Rob Stryker (JIRA) issues at jboss.org
Wed Jul 30 03:24:30 EDT 2014


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

Rob Stryker commented on JBIDE-17996:
-------------------------------------

The display is taking two IPaths and performing the following:

path1.removeFirstSegments(path2.segmentCount()).toString();

This is insufficient, because the toString() will also include the device, in this case c:

The proper solution is to do a substring. Pushed to cr1

> Server Runtime Environment wizard says "C:standalone" even if corrected
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-17996
>                 URL: https://issues.jboss.org/browse/JBIDE-17996
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta3
>         Environment: Eclipse Luna
> JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70
> Windows 7 x64
> Java 8u11
>            Reporter: Karl Pietrzak
>             Fix For: 4.2.0.CR1
>
>
> h3. What
> For some reason, the Server Environment Runtime wizard for Wildfly (probably JBoss too) auto-detects the "Configuration Base Directory" as "C:standalone".
> Even if I try to overwrite it to just "standalone", it overwrites it to "C:standalone".
> h3. Screencast
> http://screencast.com/t/1wC8B2loj4H
> h3. Found Bug location?
> My guess is {{org.jboss.ide.eclipse.as.core.util.ServerUtil::makeRelative}}, but I'm not sure why.
> At first I thought it had something to do with the fact that I originally put my Wildfly install into {{c:\program files}} (note the space), but then I moved it to a location that does not have spaces and the same thing occurred.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the jbosstools-issues mailing list