Yep, this is a good simple case. I think this is what we are going to start with.<br><br><div class="gmail_quote">On Tue, Oct 11, 2011 at 3:45 PM, Keith Babo <span dir="ltr"><<a href="mailto:kbabo@redhat.com">kbabo@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div><br></div><div>As a first step here, would it make sense to have a binary install option which simply treats a jar as a single module? This seems like a nice feature for plugins which have no external dependencies. It also provides a nice backward compatibility story for existing plugins which use shading to incorporate all dependencies into one jar.</div>
<div><br></div><div>cheers,</div><div>keith</div><div><div></div><div class="h5"><br><div><div>On Oct 11, 2011, at 3:35 PM, Lincoln Baxter, III wrote:</div><br><blockquote type="cite">Hi Tom,<br><br>This was commented out due to the new modules packaging required by plugins when they are installed. In order to support this new packaging, we will need to do something similar to that which is done when building a plugin from sources and installing it. e.g:<br>
<br><ol><li>resolving all dependencies</li><li>building a module and dependencies module<br></li><li>copying that module and dependencies module to the proper directory in ~/.forge/plugins</li><li>registering the plugin in ~/.forge/plugins/installed.xml<br>
</li></ol>It *should be* fairly straight forward, but maven never makes things easy. I need to figure out how best to handle building a zip of the plugin itself (for distributions). I think that would be easy to do via forge, but difficult to accomplish via maven. This definitely needs some thought.<br>
<br>~Lincoln<br><br><div class="gmail_quote">On Mon, Oct 10, 2011 at 11:58 PM, Tom Cunningham <span dir="ltr"><<a href="mailto:tcunning@redhat.com" target="_blank">tcunning@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I'd like to take a look at getting mvn-plugin to work for SwitchYard - I<br>
started taking a look at ForgePlugin.java and noticed that it was<br>
commented out. Is there any project history with regards to<br>
mvn-plugin that would be useful to know? Was it working at some<br>
point and then regressed and then subsequently commented out? Or is<br>
it just in mid-implementation?<br>
<br>
It looks like it has arguments spec'ed out - are these the command line<br>
arguments desired?<br>
<br>
Thanks,<br>
<br>
Tom<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com/" target="_blank">http://ocpsoft.com</a><br><a href="http://scrumshark.com/" target="_blank">http://scrumshark.com</a><br>
"Keep it Simple"<br>
_______________________________________________<br>forge-dev mailing list<br><a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote></div><br></div></div></div><br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>