[forge-issues] [JBoss JIRA] (FORGE-1902) Initial context in Forge Console appears to be incorrect

George Gastaldi (JIRA) issues at jboss.org
Wed Jun 25 15:59:24 EDT 2014


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

George Gastaldi moved JBIDE-17645 to FORGE-1902:
------------------------------------------------

              Project: Forge  (was: Tools (JBoss Tools))
                  Key: FORGE-1902  (was: JBIDE-17645)
    Affects Version/s: 2.6.0.Final
                           (was: 4.2.0.Beta2)
          Component/s: UI - Shell
                           (was: forge)
             Security: Public


> Initial context in Forge Console appears to be incorrect
> --------------------------------------------------------
>
>                 Key: FORGE-1902
>                 URL: https://issues.jboss.org/browse/FORGE-1902
>             Project: Forge
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: UI - Shell
>    Affects Versions: 2.6.0.Final
>         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 forge-issues mailing list