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

Lincoln Baxter III (JIRA) issues at jboss.org
Wed May 14 12:13:56 EDT 2014


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

Lincoln Baxter III commented on JBIDE-16954:
--------------------------------------------

Yes, this requires addition of a custom CdTokenHandler from Eclipse:

This may require a little bit more work on the Forge side since this SPI is purely a Furnace service based solution - no manual registration is provided. Unless we created an addon that allowed dynamic service registration and used that from Eclipse:

{code}
ServiceRegistrar.addService(ServiceType.class, instance);
{code}

This service-registrar addon would need to depend on `core` addon.


> 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
>             Fix For: 4.2.0.Beta2
>
>
> 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.3#6260)


More information about the jbosstools-issues mailing list