>IMO the projects themselves should provide the archetypes. What projects? Is there a list of starter projects I can start from?
>This >proves to be more difficult than it sounds... for Struts I didn't go >beyond turning the "Struts Blank" webapp into an archetype, because >after that, how should I know whether you want Hibernate, iBatis, >Spring, etc? Hmmm... well, maven 1.0.2 justed asked a lot of questions. I could go for that. >At that point, it's not an archetype, it's AppFuse. That is not so bad. The problem with AppFuse is that there is no dialog asking you what you want and don't want. For something as complex as AppFuse, one should really have a GUI. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
