[forge-dev] Packaging and installing plugins from Maven

Keith Babo kbabo at redhat.com
Wed Apr 25 10:15:59 EDT 2012

Oh, snap.  That's nice.   I can definitely see some interesting possibilities bubbling out from here.

In terms of how we've done things now, there are still a few things I'l like to change.  First, we package all of our independent plugins into a single module for installation into Forge.  We need to change that for this release of SwitchYard.  Once we have that in place, we can look at how the plugin could be pulled down directly from a Maven repository instead of copying directly into ~/.forge/plugins (which is what I think we do today).

BTW, is there a "history" command in Forge right now?  I noticed there is a ~/.forge/cmd_history file, but I didn't see a command which actually lists the content of that file from within forge itself.  You can use the arrow keys to navigate in command history, so I'm sure this is being read for that.


On Apr 25, 2012, at 10:10 AM, Lincoln Baxter, III wrote:

> Hey Keith!
> Regarding instaling plugins from Maven - we'd definitely like to support this. Perhaps we could take what you've done and standardize it as a supported plugin installation mechanism?
> Regarding testing the plugins in a forge release distribution. As of Forge 1.0.3.Final, you can invoke Forge from the command line using:
> forge -e "command or script to run"
> So hopefully that will be of use :) You can install plugins using this feature as well, so with the combination of the two, we should have some good testing options!
> -- 
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120425/f01161d2/attachment.html 

More information about the forge-dev mailing list