AppFuse 2.0 M3 Released
The AppFuse team is pleased to announce the release of AppFuse 2.0 M3! This release marks a milestone in our documentation efforts. We've completed all of the web framework tutorials and ensured that all the archetypes work properly. Turkish language support was added and native2ascii was integrated so all i18n bundles should work properly.
The major things missing from this release are code generation (AppGen) and web services (XFire) support. We hope to add both of these before the final release.
AppFuse 2.0 is available as a Maven archetype. For information on creating a new project using this release, please see the QuickStart Guide.
The 2.0 series of AppFuse has a minumum requirement of the following specification versions:
- Java Servlet 2.4 and JavaServer Pages (JSP) 2.0
- Java 2 Standard Platform Edition (J2SE) 5.0
For more information, please see the 2.0 M3 Release Notes.
We appreciate the time and effort everyone has put toward contributing code and documentation, posting to the mailing lists, and logging issues. We also greatly appreciate the help from our sponsors, particularly Atlassian, Cenqua, Contegix, JetBrains, Java.net and KGBInternet. Without them, working on this project wouldn't be nearly as much fun.
Posted by Marco on February 07, 2007 at 10:06 AM MST #
Posted by blabla on February 07, 2007 at 01:25 PM MST #
Posted by blabla on February 07, 2007 at 01:34 PM MST #
blabla - we're moving to Maven because it makes sense for a project like AppFuse - especially from a maintenance perspective. It's much easier to change a version number in an XML file than to add a JAR, remove a JAR and update 2-3 XML files like we did in AppFuse 1.x. The nice thing about AppFuse 2.x is we've fixed most "mavenisms" - for example, JARs not being in the central repo.
Lines of XML in AppFuse 1.x's build.xml: 1375
Lines of XML in an AppFuse 2.x pom.xml: ~500
That being said, I agree with you that Ant is an excellent build tool. For those folks who prefer Ant over Maven, there's always AppFuse 1.9.x. Since we only have a few point releases left in 1.9.x, my hope is to support it with its current features until we hit 1.9.9. That being said, there's something we can probably do for those we-can't-use-Maven folks.
1. Create a tutorial that shows how to "Build Your Own AppFuse". Because everything is modular and well-structured in Subversion, it should be easy to build your own stack - with source and such. If there's enough interested, we could create an version of AppFuse that uses Ant. However, if folks are simply using it because "I tried Maven and it sucked", I believe we can fix that problem.
2. Running "mvn ant:ant" will create Ant files for you - but I don't know if they support multi-module projects.
If we do support Ant in the future, we'll still use a dependency downloading mechanism like Ivy or Maven's Ant Tasks. One thing I think is possible (but I haven't tried) is distributing AppFuse with a "lib" directory that Maven looks in for dependencies. I've also thought about distributing my local repo after building AppFuse. Users could download, extract and be able to work immediately offline.
Then again, maybe AppFuse should be Opinionated Software. If you don't like it - don't use it. ;-)
Posted by Matt Raible on February 07, 2007 at 04:50 PM MST #
Posted by blabla on February 07, 2007 at 08:04 PM MST #
Posted by 165.254.69.190 on February 07, 2007 at 09:28 PM MST #
Posted by Matt Raible on February 07, 2007 at 09:31 PM MST #
Posted by Rene on February 08, 2007 at 10:14 AM MST #
Posted by Rich on February 26, 2007 at 09:47 AM MST #
Posted by Rich on February 28, 2007 at 01:45 PM MST #
Posted by Matt Raible on February 28, 2007 at 03:25 PM MST #
Posted by Rich on March 02, 2007 at 10:50 PM MST #
Posted by Daniel on March 08, 2007 at 09:30 PM MST #
Posted by Matt Raible on March 08, 2007 at 09:57 PM MST #
Posted by 69.209.222.159 on October 16, 2009 at 02:18 AM MDT #
Posted by Matt Raible on October 16, 2009 at 03:17 AM MDT #