[jbosstools-issues] [JBoss JIRA] (JBIDE-17890) Command 'cd #/projectname' not implemented in Forge2

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-17890:
----------------------------------------

    Description: 
I'm missing 'cd #' command in Forge2.
Would it be possible to make the forge "cd" command aware of the eclipse workspace the same way as it is in Forge1? Especially being able to "cd #/projectname" where projectname is *NOT* inside the physical workspace directory.

Remember our recommendation to users is *NOT* to put their projects inside eclipse workspaces thus having just 'cd #' is not really that useful on its own.

  was:
I'm missing 'cd #' command in Forge2.
Would it be possible to make the forge "cd" command aware of the eclipse workspace the same way as it is in Forge1?



> Command 'cd #/projectname' not implemented in Forge2
> ----------------------------------------------------
>
>                 Key: JBIDE-17890
>                 URL: https://issues.jboss.org/browse/JBIDE-17890
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Pavol Srna
>            Assignee: Lincoln Baxter III
>             Fix For: 4.2.0.Beta3
>
>
> I'm missing 'cd #' command in Forge2.
> Would it be possible to make the forge "cd" command aware of the eclipse workspace the same way as it is in Forge1? Especially being able to "cd #/projectname" where projectname is *NOT* inside the physical workspace directory.
> Remember our recommendation to users is *NOT* to put their projects inside eclipse workspaces thus having just 'cd #' is not really that useful on its own.



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