The most important asset you have for such a transition is your unit tests. To move all of AppFuse into a Maven 2 directory structure didn't take me too long - about 3 days. The hard part was getting all the Maven plugins (dbunit, hibernate3, etc.) to work properly. The good news is those are pretty stable now, so it shouldn't be too hard to make the transition.
I've entered an issue in JIRA for this so we can make sure it gets into 2.0: http://issues.appfuse.org/browse/APF-560 Matt On 12/28/06, mseritan <[EMAIL PROTECTED]> wrote:
I really like the way Appfuse 2.0 uses Maven to keep all the pieces up to date. I understand this is still work in progress but it is already very promising. One of the related pieces is upgrading existing code to Appfuse 2.0. One can pursue this as a goal in itself but also as an intermediate step to transition to a new framework. For example I may have some code on older 1.x Struts based app and I'd like to try JSF. The only option I see so far is starting with a clean AppFuse and move the code over. Are there tools, checklists to help with this process? Thanks for any pointers :) Marius -- View this message in context: http://www.nabble.com/Thoughts-on-upgrade-path--tf2892731s2369.html#a8081945 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
