Matt Raible wrote:
On 1/31/07, *Dale Newfield* wrote: I guess that means you intend to continue supporting the old ant based tool even after your fancy-schmancy maven one is finished?Yes, IMO - there's no reason to discontinue a successful product. ;-) Do you agree?
I do, but it seems the general nature of software that once the authors find a shiny new toy, spending time back-porting updates to the old version becomes a drag, and eventually doesn't happen.
However, I don't plan on upgrading AppFuse 1.x to Java 5, annotations, etc.
There are definitely gray areas here--some back ports are worth the effort but others are not? Struts2 is a java5 product. Do you plan on putting in a struts2 module (in addition to/instead of webwork) in AppFuse1? Do you use the java4 or java5 version of struts2 in that? If the latter, then really isn't it just a matter of adding generics into the templates to get the java5 based tool? You've got to draw the line somewhere...
It's a bunch of work to keep backporting everything, but it's also lots of work to backport some things and not others, and can get quite confusing. If you go this route I bet you will eventually freeze the versions of certain components in AppFuse1... (for example, to java4?)
I don't know if this is possible, but I'd expect an easier solution would be to use AppFuse2 to generate a fully expanded codebase, and then manually add the build scripts and package as an AppFuse1-like tool that can be run completely with ant. Of course, what the appgen replacement looks like will definitely impact the feasibility of an approach like this.
-Dale --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
