[forge-dev] Seam 2 -> Seam 3 Migration Strategy
lightguard.jp at gmail.com
Thu Aug 11 18:08:38 EDT 2011
By and large you'll have to *create* a pom, and the layout of seam-gen is
not that of a typical maven project, not sure if that presents a
unique challenge or not.
On Thu, Aug 11, 2011 at 15:26, Lincoln Baxter, III
<lincolnbaxter at gmail.com>wrote:
> Hi Guys,
> I'd like to start implementing a Seam 2 -> Seam 3 plugin for Forge, so that
> we can give people *Something* to get started with this process. My vision
> at this point is to specify a list of tasks for the plugin to perform, E.g.
> - Updating the POM to include new dependencies
> - Replacing Seam 2 annotations with Seam 3 annotations
> - Getting basic configuration files set up
> - Doing some static code analysis in order to print a list of tasks
> that need to be done by hand (sort of a "what do I have left?")
> In order to accomplish this, having *never* used Seam 2, I need a few
> 1. A list of APIs and which Seam 3 feature replaces it - this includes
> annotations, static classes, and injected interfaces/classes.
> 2. A test project with all of these features (or at least a lot of
> As soon as I have these things, I will get started, and anyone who wants to
> help out and work on this as well is more than welcome to join me!
> Lincoln Baxter, III
> "Keep it Simple"
> forge-dev mailing list
> forge-dev at lists.jboss.org
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...
More information about the forge-dev