[jbosstools-issues] [JBoss JIRA] (JBIDE-17645) Initial context in Forge Console appears to be incorrect

Max Rydahl Andersen (JIRA) issues at jboss.org
Wed Jun 25 15:30:24 EDT 2014


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

Max Rydahl Andersen updated JBIDE-17645:
----------------------------------------

    Assignee: George Gastaldi


> Initial context in Forge Console appears to be incorrect
> --------------------------------------------------------
>
>                 Key: JBIDE-17645
>                 URL: https://issues.jboss.org/browse/JBIDE-17645
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>    Affects Versions: 4.2.0.Beta2
>         Environment: Mac OS X Mavericks 10.9.3, JBDS 8 Beta 2, Oracle JDK 7u60
>            Reporter: Vineet Reynolds
>            Assignee: George Gastaldi
>
> When I launch the Forge console for the first time (or restart it), the initial context appears to be incorrectly set. Although the console shows that, Forge does not seem to recognize it.
> As an example, the following console output shows different responses to the {{ls}} command without changing the current working directory:
> {noformat}
> [JDF]$ cd <TAB> 
> hs_err_pid1248.log               jbdevstudio.ini                  
> hs_err_pid1372.log               org.jboss.tools.vpe.browsersim/  
> jbdevstudio                      
> [JDF]$ pwd
> /Users/vineet/workspaces/JDF
> [JDF]$ cd <TAB>
> .metadata/  RemoteSystemsTempFiles/  
> {noformat}
> This seems to affect path autocompletion mainly, but is also likely to affect Forge command execution that relies on the current working directory, since paths seem to be computed from JBDS root instead of the current workspace root for the very first time.



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


More information about the jbosstools-issues mailing list