[seam-dev] [forge-dev] Seam 2 -> Seam 3 Migration Strategy

[Jason Porter]

Sure, anything we can do that's more automated would sure help them out
though.

On Thu, Aug 11, 2011 at 17:06, Dan Allen <dan.j.allen at gmail.com> wrote:

> On Thu, Aug 11, 2011 at 18:48, Jason Porter <lightguard.jp at gmail.com>wrote:
>
>> Step 1 then is going to be migrate to maven, then we can let forge do some
>> work.
>>
>
> That's not necessarily step 1 of the guide though. The guide should focus
> on the programming model.
>
> -Dan
>
> --
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://www.google.com/profiles/dan.j.allen#about
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-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/20110811/5170455d/attachment.html