<div class="gmail_quote">On Sun, Apr 19, 2009 at 11:13 PM, Shane Bryzak <span dir="ltr"><<a href="mailto:shane.bryzak@jboss.com">shane.bryzak@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ok, so now we have the following structure:<br>
<br>
/seam<br>
/docs<br>
/trunk<br>
/examples<br>
/trunk<br>
/booking<br>
/modules<br>
/trunk<br>
/captcha<br>
/debug<br>
/drools<br>
/excel<br>
/framework<br>
/international<br>
/interop<br>
/ioc<br>
/jms<div class="im"><br>
/mail<br>
/pdf<br>
/remoting<br>
/resteasy<br>
/rss<br>
/security<br></div>
/ui<br>
/version-matrix<br>
/wicket<br>
/sandbox<br>
/trunk<br>
/seam-gen<br>
/trunk<br>
<br></blockquote></div><br>Should we qualify the term modules? Meaning instead of modules and sandbox we have something like<br><br>modules<br>sandbox-modules<br>thirdparty-modules<br><br>Modules (I'm open to a qualifier like official-modules) would be official modules in Seam...stuff that is going into EAP. sandbox would be modules we want to put into core, but they just aren't ready yet or may never be. thirdparty would be modules we are hosting for a community member but we don't want to maintain. For instance, perhaps the host the tapastry integration module or whatever. I'd be interested in doing that with examples too.<br>
<br>examples<br>sandbox-examples<br>thirdparty-examples<br><br>Thoughts? This should be easy to add without affecting what you have setup already.<br><br>On another topic, we should definitely have tests confined to each module. That's sort of obvious given they are each their own project now. I would also like to see more tests. The biggest obstacle to test writing today is that it is just too much of a time sink to create a test and get it to pass. It takes me 5 times as long to do a test as to fix the problem. I really want to see us make testing easy so that we get tests when we get patches. It's not so much for us as it is for the community and getting them to help/participate.<br>
<br>-Dan<br><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>