Adding seam-dev.<br><br><div class="gmail_quote">On Wed, May 25, 2011 at 16:50, Paul Bakker <span dir="ltr">&lt;<a href="http://paul.bakker.nl">paul.bakker.nl</a>@<a href="http://gmail.com">gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hey all,<div><br></div><div>Just a thought. Should we create one large plugin project for the Seam 3 related plugins? Now we split them per Seam3 module. This is nice on a development perspective, but not as nice for an end user because you need to install 10 different plugins in Forge... So we should either think about a packaging mechanism that keeps the code split in different projects on github, but still be able to install them in a single command or just put them all together in one project. </div>


<div>What are your thoughts?</div><div><br></div><font color="#888888"><div>Paul</div>
</font><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><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>

<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>