I have cycles this week. At a minimum, I'll take care of JCR and JMS. If anyone else has any modules they need help with let me know.<br><br>John<br><br><div class="gmail_quote">On Mon, Aug 22, 2011 at 5:48 AM, Shane Bryzak <span dir="ltr"><<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Guys and girls,<br>
<br>
In the interest of moving things forward, I'm going to shortly start<br>
working on the beta 2 release. There are still some issues that we're<br>
working through with the multi-container testsuite configuration,<br>
however with some help I've been able to resurrect the existing tests in<br>
Solder to run in the latest version of Arquillian and I'm confident that<br>
I can get the tests in the other modules passing successfully without<br>
too much trouble. I would still like us to press on with the test suite<br>
work, however I don't want it to hold up the release schedule.<br>
<br>
Since the Beta1 release there have been a couple of important changes,<br>
which I'll quickly summarise here:<br>
<br>
1) seam-parent is now at the top of the food chain and no longer<br>
inherits its configuration from weld-parent. This change is good for a<br>
couple of reasons, first of all the disassociation from the Weld project<br>
will help to reinforce that Seam is CDI implementation-independent.<br>
Secondly it gives us total control over configuration for the Maven<br>
plugins that we use, allowing us to update the plugin versions (which<br>
I've already done, to the latest version of each plugin) and fine tune<br>
the plugin configuration parameters for Seam.<br>
<br>
2) I've decided against moving the logging feature out of Solder and<br>
into its own module for now, as I discovered that it was too tightly<br>
coupled to Solder to "de-tangle" it easily. I have however refactored<br>
the logging API classes into their own package, org.jboss.seam.logging<br>
which I think will be more intuitive for our users. I believe that the<br>
Solder reference documentation still needs to be updated in response to<br>
the changes made for SOLDER-102<br>
(<a href="http://issues.jboss.org/browse/SOLDER-102" target="_blank">http://issues.jboss.org/browse/SOLDER-102</a>) - Ken, could you please<br>
confirm? If so, would you be willing to update the reference docs to<br>
reflect the logging changes?<br>
<br>
I am aiming for the Beta2 release this coming weekend, which means with<br>
our 20+ modules now I need to get started pretty soon. If anyone has<br>
any spare cycles and is able to help out with this, it would be greatly<br>
appreciated. Each module needs to have its tests fixed, logging<br>
refactored to use the new logging API package, and its distribution<br>
thoroughly checked for correctness/completeness. If you'd like to<br>
volunteer for a module or two, please catch me on IRC and we can work it<br>
out there.<br>
<br>
Thanks,<br>
Shane<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote></div><br>