FishEye and Crucible

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release APPFUSE_2.1.0-M1

Use properties in versions for dependencies defined in main pom.xml.

Upgrades to dependencies and plugins thanks to the versions-maven-plugin (http://mojo.codehaus.org/versions-maven-plugin): Plugins: aspectj-maven-plugin 1.1 -> 1.2 dbunit-maven-plugin 1.0-beta-1 -> 1.0-beta-3 maven-eclipse-plugin 2.5.1 -> 2.7 maven-idea-plugin 2.1 -> 2.2 maven-jetty-plugin 6.1.14 -> 6.1.21 Dependencies: aspectj 1.6.2 -> 1.6.6 commons-beanutils 1.8.0 -> 1.8.1 ehcache 1.5.0 -> 1.7.0 myfaces 1.2.6 -> 1.2.7 myfaces-tomahawk 1.1.8 -> 1.1.9 sitemesh 2.4 -> 2.4.2 struts 2.1.6 -> 2.1.8 Also changed default Cargo container back to Tomcat (from Jetty) because of issues with JSF and because Tomcat is taking over the world. Slowly but surely.

Tapestry basic now passing with AMP tests. However, there's still lots of work to do. 1. Fix AppModule so required fields show up with asterisk. 2. Modify *Form.java so fields are required (should fix #1). 3. Write tests in standard web/tapestry module, as well as for AMP.

Fixed archetype generation process

Upgraded to SiteMesh 2.4 (APF-1128) and require Maven 2.1.0 as a minimum version (APF-1101)

Changed web modules to use sources from web-common module instead of using warpath plugin. Archetypes still not working (http://www.nabble.com/Is-it-possible-to-add-files-to-an-archetype-from-other-directories--td23212840.html#a23212840). Would love to get to a state where the archetypes only have a pom.xml and read sources from web modules.

APF-1083: Upgrade to Ant 1.7.1

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release APPFUSE_2.0.2

[maven-release-plugin] rollback the release of APPFUSE_2.0.2

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release APPFUSE_2.0.2

maven-hibernate3-plugin 2.1 requires explicity dependency on log4j

APF-969: Added appfuse:copy-templates to copy templates from SVN into local project

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release APPFUSE_2.0.1

APF-907: Fixed couldn't rename temporary file issue by upgrading to Ant 1.7.0

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release APPFUSE_2.0

Preparing for 2.0 Release

Removing changes from revision 3000 - some files had old code in them

Release 2.0 - with all the versions changed this time. ;-)

[maven-release-plugin] prepare for next development iteration

[maven-release-plugin] prepare release APPFUSE_2.0

APF-876: Fixed full-source on Windows (hopefully)

APF-874: Changed the appfuse-maven-plugin's groupId to org.appfuse. In order to get the appfuse-maven-plugin uploaded to Maven's Central repository, it can't have org.codehaus.mojo as its groupId. The original reason I started using this groupId is because I couldn't get the "appfuse" prefix to work w/o it. Now the prefix seems to work fine (at least locally). http://jira.codehaus.org/browse/MAVENUPLOAD-1701 NOTE: We realize it makes good sense to change the groupIds to be more specific than "org.appfuse" for many of AppFuse's modules. However, it seems somewhat risky to do this late in the 2.0 game. If we do decide to change them, we'll likely do it for 2.1. Please comment on the following thread if you have any opinions on this: http://www.nabble.com/Thinking-out-loud-about-groupIds-tf4387544s2369.html

Change version to 2.0-SNAPSHOT.

AppFuse 2.0 RC1 Release

APF-866: Fixed location of where appfuse-maven-plugin is deployed to.

APF-757: Added support for JPA to AMP. Currently, iBATIS and JPA are only tested against the "gen" goal and not "full-source". The full-source goal should work, but I'm skipping testing because I know it might take quite some time to test/fix and I'd rather get 2.0 RC1 out the door. ;-)

APF-861: While working at Checkmate Technologies (http://checkmate-tech.blogspot.com) earlier this year, I did a lot of work to fix Checkstyle issues in the data, hibernate, service and web (Struts 2) layers of AppFuse. They've agreed to donate this code - thanks guys!

APF-842: Upgraded to hibernate3-maven-plugin version 2.0-alpha-2

Fixed path to plugins publishing directory

APF-835: Resolved Dependency Convergence issues

APF-833: Upgraded to Commons IO 1.3.2

APF-822: Upgrade to Maven IDEA Plugin 2.1

Changed version to 2.0-rc1-SNAPSHOT (and 1.0-rc1-SNAPSHOT for maven-warpath-plugin)

AppFuse 2.0 M5 Release

APF-490: Polishing based on PMD Report

APF-490: Documentation for AppFuse Maven Plugin

APF-675: Added "full-source" plugin that pulls AppFuse's source from SVN and replaces AppFuse dependencies with one from the pom.xml's it pulls in. Current only tested with basic projects. Modular support coming in next release. You can test both AMP and the Full Source plugin using Ant targets in plugins/appfuse-maven-plugin/build.xml. Just run "ant -p" in the appfuse-maven-plugin directory to see all the options. Reading the source code of build.xml will show issues that currently exist (amp requires you to copy hibernate.cfg.xml to the "web/src/main/resources" directory on a modular project. Also, the full source plugin has not been modified to work with (or tested on) modular projects.

Began working on "full-source" mojo. It's far from complete - SVN export works, but there's lots of pom.xml manipulation that still needs to happen.

* Added "gen-core" and "gen-web" and renamed "gen-ui" (the motherload) to "gen". The "install" mojo is still not aware of core vs. web, so you'll get errors about missing files if you try to use it with anything but "gen". * Fixed templates and install (non generics-based) install for backend. Remaining items todo: ------------------------- * Add logic to Action/Controller templates that generate different setters/imports for generic/impl * aggregate "gen and install" so they can be run in single call vs. two separate ones (lifecycles?) * get working with other web frameworks (only tested with Struts 2) * get working with other persistence frameworks (only tested with Hibernate) * get working with modular projects * modify install mojo to handle gen-core and gen-web * Call ModelGeneratorMojo from AppFuseGeneratorMojo to generate from db

Removed AMP from Sandbox to eliminate confusion

Override Codehaus locations for distribution

Fixed dependencies: alpha-6 breaks tests

Fixed dependencies: alpha-6 breaks tests

Code generation plugin based on Hibernate3 Plugin, Hibernate Tools and previous AppFuse Maven Plugin (especially for installation code)

Removed Ant-tasks based version of plugin in favor of one based on Hibernate3 (less flexible, but better for initial implementation IMO)

Customized Hibernate Tool's FreeMarker templates to match tutorial code. Lots of beautification and general hacks since Hibernate Tools doesn't work that well with annotations.

Updated to version 2.0-m5-SNAPSHOT

AppFuse 2.0-M3 Release

Update for new generation plan with tasks and java integration to the hibernate tools ant tasks

Fixed issue with missing Hibernate Dialect

add sample of code generation with templates

Update to allow ant based mojos

Polishing

Changed version to 2.0-m4-SNAPSHOT

Changed version to 2.0-m3

added ant-optional jar dependency

Changed version back to SNAPSHOT for M3 development

Preparing for 2.0 M2 Release

removed extract goal

refactored ant script name

revised location of jdbc properties and comments

added mvn extract:extract

APF-554: Configured plugins so sites can be deployed to http://static.appfuse.org/plugins using 'mvn deploy

Synched up Hibernate and MySQL versions

Changed from mojo as a parent to AppFuse as a parent

refactor names, spelling

URI issue with POM schema. Non issue.

fixing documentation for site

Changed "Appfuse" to "AppFuse" ;-)

Moved appfuse plugin from basedir to plugins dir

Initial checkin of code.

Sample data and Spring bean installation complete (only tested with Struts 2)

No need to upgrade FreeMarker

i18n generation now working

Rearranged to be more like AppFuse pom.xml's

Began creating installer plugin (only copies .java files so far, still need to merge XML)

Struts 2 form and view completed, as well as data helper for generating DbUnit sample data.

All templates now generate correctly (except need to figure out how to properly escape JSTL's ${} with FreeMarker). Also added "gen-model" goal for generating POJOs from database tables.

Vegas baby!

Added appfuse-maven-plugin based on hibernate3-maven-plugin to sandbox