[forge-issues] [JBoss JIRA] (FORGE-340) Change default plugin checkout location to use the .forge/plugins-sources directory

Lincoln Baxter III (JIRA) jira-events at lists.jboss.org
Wed Aug 22 14:06:14 EDT 2012


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

Lincoln Baxter III commented on FORGE-340:
------------------------------------------

Yes, I think that makes sense. I would be fine with simply adding an 

{code}@Option(name="checkoutDir") Resource checkoutDir{code}

And let users save the source somewhere if they want. Otherwise just default to /tmp
                
> Change default plugin checkout location to use the .forge/plugins-sources directory
> -----------------------------------------------------------------------------------
>
>                 Key: FORGE-340
>                 URL: https://issues.jboss.org/browse/FORGE-340
>             Project: Forge
>          Issue Type: Task
>          Components: Shell
>    Affects Versions: 1.0.0.Alpha4
>            Reporter: Lincoln Baxter III
>            Assignee: Rodney Russ
>            Priority: Minor
>              Labels: Starter
>             Fix For: 1.0.7.Final
>
>
> {code}$ forge git-plugin git at github.com:repo/etc{code}
> needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily.
> this code lives here:
> https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/forge/shell/plugins/builtin/ForgePlugin.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the forge-issues mailing list