[seam-dev] 3 weeks until Seam 3.1 Beta1

[Jason Porter]

I like that idea quite a bit actually. But it becomes very complicated once
you get into Reports and Cron, and even Mail.

On Mon, Jul 25, 2011 at 16:06, Shane Bryzak <sbryzak at redhat.com> wrote:

> How about having one module that contains all of the API for all
> implementations, and then one implementation for each of the services?
>
> On 26/07/11 01:51, Antoine Sabot-Durand wrote:
> > Hi Shane,
> >
> > Seam social is in alpha1, but API are now stable enough to enter in beta.
> This also necessary to add my OAuth contribution to Seam security.
> >
> > Regarding packaging I'm still wondering if model and controller class for
> a given service (Twitter for instance) shouldn't be put in a sub module to
> separate core functions from specific implementations. It will facilitate
> different lifecycle for each social service support for instance and allow
> users to only include module they need for their development.
> >
> > the only issue with that is it would create 2 submodule per service (API
> and IMPL) and I find it a bit heavy...
> >
> > What is your opinion on that subject ?
> >
> > regard,
> >
> > Antoine SABOT-DURAND
> >
> >
> >
> >
> >
> >
> >
> >
> > Le 25 juil. 2011 à 01:33, Shane Bryzak a écrit :
> >
> >> Just a heads up to everyone that we only have 3 weeks remaining until
> >> the beta 1 release for Seam 3.1.  It would be appreciated if all module
> >> leads could reply to this with a status update for your module, and
> >> whether you foresee any issues with delivering a beta for your module
> >> within this timeframe.
> >>
> >> I'd also like to remind everyone that we are getting rid of the shaded
> >> (combined) jars, so if you need assistance in doing this for your module
> >> please let me know and I can help out.
> >>
> >> Shane
> >> _______________________________________________
> >> seam-dev mailing list
> >> seam-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/seam-dev
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>



-- 
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110725/48727da4/attachment.html