[jbosstools-issues] [JBoss JIRA] (JBIDE-16954) Command 'cd #' not implemented in Forge2
Lincoln Baxter III (JIRA)
issues at jboss.org
Thu Jun 26 00:20:24 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lincoln Baxter III resolved JBIDE-16954.
----------------------------------------
Resolution: Done
Requires latest forge sources as of this comment, but fixed. Will be delivered in Beta3. Did not implement `cd #/projectName` support as that is a more complicated issue that must be addressed. Should be opened as a separate issue.
> Command 'cd #' not implemented in Forge2
> ----------------------------------------
>
> Key: JBIDE-16954
> URL: https://issues.jboss.org/browse/JBIDE-16954
> 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?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jbosstools-issues
mailing list