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 things: 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 them.) 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 http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

On Thu, Aug 11, 2011 at 18:08, Jason Porter <lightguard.jp(a)gmail.com&gt;wrote: > 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. > There is already a lot of work that's been done to create a POM for a Seam 2 project (that you can then migrate into a Seam 3 project). Marek is the right person to talk to for references (links, examples, etc). -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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

On Thu, Aug 11, 2011 at 18:48, Jason Porter <lightguard.jp(a)gmail.com&gt;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 _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

On Thu, Aug 11, 2011 at 18:08, Jason Porter <lightguard.jp(a)gmail.com&gt; wrote: 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. There is already a lot of work that's been done to create a POM for a Seam 2 project (that you can then migrate into a Seam 3 project). Marek is the right person to talk to for references (links, examples, etc). -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 _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev