[forge-dev] How to package/register your own plugin?

Lincoln Baxter, III lincolnbaxter at gmail.com
Wed Jan 5 15:28:47 EST 2011


No problem at all. At this time, you still need to place
*your-plugin.jar*file and all necessary maven dependencies into the
*$FORGE_HOME/lib* directory. This is something we are working on addressing
as we speak.

~Lincoln

PS. forge-users at lists.jboss.org list has been requested and is being set up,
but not active yet.

On Wed, Jan 5, 2011 at 3:21 PM, marijan milicevic
<m.milicevic at onehippo.com>wrote:

> sorry, I see this is a dev list, is there a user list where I can ask usage
> questions?
> cheers,
> /m
>
>
> On Wed, Jan 5, 2011 at 9:12 PM, marijan milicevic <
> m.milicevic at onehippo.com> wrote:
>
>> Hi there,
>> I've  created a simple project/plugin and installed it (mvn install)
>> however, I am not sure how to invoke it.
>> Right now, I have it as a compile depenedency within my own assembly
>> project and I can see that my project jar is included into classpath.
>>
>> Running "list-commands --all"  doesn't reveal my plugin.
>> What are the steps to run / register your own plugins, facets etc.?
>> thx,
>> /m
>>
>> PS: forge project looks really promising ;-)
>>
>>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>


-- 
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20110105/fed9358b/attachment.html 


More information about the forge-dev mailing list