FishEye and Crucible

Archetypes now contain all source from web modules. No more maven-warpath-plugin needed.

Changed to use AppFuse group on Sonatype's Nexus.

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-1121: Upgrade to H2 1.0.79

APF-1046: Upgraded Tomcat version used by Cargo to 6.0.18.

Exclude ApplicationResources*.properties from war overlay (in case the WAR has newer files). Also fixed APF-1073 - replacing ${java.io.tmpdir} with /tmp.

Preparing for next development iteration

Preparing for Release 2.0.2

APF-1046: Reverting to Tomcat 6.0.14 to see if it fixes Bamboo and because 6.0.16 spits out invalid error messages on startup: http://www.mail-archive.com/dev@tomcat.apache.org/msg23389.html

APF-1061: Upgrade to Canoo Web Test R_1702 which has *much* better JavaScript support. APF-946: Upgrade to Scriptaculous 1.8.1

APF-943: Upgraded jMock to 2.4.0

APF-1056: Upgraded to Maven Eclipse Plugin 2.5.1

APF-1055: Upgraded to Spring 2.5.4

APF-1043: Upgrade to Spring 2.5.3

APF-1046: Upgrade to Tomcat 6.0.16

APF-1029: Upgrade to Spring 2.5.2

APF-964: Upgraded h2 database profile to use H2 1.0.62. APF-966: Changed HSQLDB and H2 to use {java.io.tmpdir}/databasename for their jdbc.url so the database will be available across modules/tests

Preparing for next development iteration

Preparing for 2.0.1 Release

APF-666: Changed JPA and Hibernate to use SimpleJdbcTemplate for fetching user's password to avoid duplicate User objects in same session

APF-945: Upgraded to Spring 2.5 and changed to use fine-grained Spring dependencies instead of Spring's uber spring.jar

APF-945: Fixed Spring version in Archetypes

APF-931: Changed to use MySQL5InnoDBDialect by default

APF-926: Upgraded to Spring 2.0.7

Preparing for next development iteration

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. ;-)

APF-718: Changed test data to use negative keys to avoid unique constraint violations on Oracle. Also added "prod" profile to allow loading default data and to serve as a placeholder for other production-related settings. NOTE: I chose to keep the name "sample-data.xml" instead of changing it to test-data.xml. It seems like a pretty risky change this late in the game of releasing 2.0.

APF-874: Changed groupId from org.appfuse back to org.codehaus.mojo. If we want to allow users to type "appfuse:*", they'll need to register the plugin in their ~/.m2/settings.xml with this change. Therefore, I'm reverting to org.codehaus.mojo as its easier for users. We won't be able to upload AMP to Maven's central repo until we move to Codehaus, but that's OK IMO. After more IRC discussions, it appears it *is* possible to distribute this plugin w/o requiring users to modify settings.xml, but the fact that we're already using org.codehaus.mojo causes that one to always be picked up first. Since we're approaching 2.0, I'm going to leave it as org.codehaus.org for now. We can rename it to something else when Maven allows the search order to be configurable or we're ready to remove it completely from AppFuse's repository. Another option is to get everything in Maven's central repository and disable AppFuse's repository so the new one is found instead.

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-868: Added JDBC Driver as a dependency to AMP (for gen-model) as a workaround for not being able to use the JDBC Driver from the project's classpath.

Fixed database names in profiles.

APF-862: Upgraded to JUnit 4.4

APF-818: Upgraded to Spring 2.0.6

APF-851: Upgraded to Canoo WebTest R_1600 as it uses HtmlUnit 1.13 and has much better JavaScript support

APF-826: Upgraded to Wiser version 1.2.

APF-834: Upgrade to Maven Eclipse Plugin 2.4

APF-823: Upgraded maven-jetty-plugin to 6.1.4 and Cargo's Tomcat version to 6.0.13. APF-824: Changed maven-jetty-plugin to use scanTargetPattern instead of scanTarget.

APF-822: Upgrade to Maven IDEA Plugin 2.1

APF-781 and APF-782: Upgraded UrlRewriteFilter to 3.0.4 and changed all references from Maven 2.0.4 to Maven 2.0.6.

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

AppFuse 2.0 M5 Release

APF-756: Configured maven-pmd-plugin for JDK 5

Added configuration settings for AMP (genericCore and fullSource flags)

APF-738 and APF-727: Upgrade to DWR 2.0.1 and Spring 2.0.5

Changed to use appfuse-maven-plugin based on Hibernate3

APF-740: Reverted to version 2.0 of cobertura-maven-plugin since it actually works

APF-594: Changed ${artifactId} to ${artifactId.replaceAll('-','_')} to solve problem when projects are created with dashes.

APF-565: Fixed DAO framework switching problem by excluding appfuse-hibernate (the default) and then adding the dependency back in with a ${dao.framework} variable taht will be read from the local pom.xml. Here's the code to change existing projects: <dependency> <groupId>org.appfuse</groupId> <artifactId>appfuse-${web.framework}</artifactId> <version>${appfuse.version}</version> <type>warpath</type> <!-- This exclusion and the dependency following this one allow DAO framework switching. --> <!-- You only need these if you want to use JPA or iBATIS. See APF-565 for more information. --> <!-- It does no harm to leave it in for Hibernate, but it's not needed. --> <exclusions> <exclusion> <groupId>org.appfuse</groupId> <artifactId>appfuse-hibernate</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.appfuse</groupId> <artifactId>appfuse-${dao.framework}</artifactId> <version>${appfuse.version}</version> </dependency>

Polishing: tabs -> spaces

Updated to version 2.0-m5-SNAPSHOT

AppFuse 2.0-M3 Release

APF-699: Upgraded to MySQL 5.0.5

Re-arranged properties in pom.xml for readability.

APF-692: Fixed Tomcat download URL and upgraded to 5.5.23

APF-691: Upgraded to Spring 2.0.3 and Spring Modules 0.8

APF-672: Changed archetype version numbers to be inline with AppFuse version number

APF-663: Moved ${copyright.year} into ApplicationResources.properties instead of parsing footer.jsp

APF-584: Got Derby working in Networked mode and added profile to archetypes

APF-584: Fixed issue with Oracle profile and added to archetypes

APF-646: Upgraded to maven-compiler-plugin 2.0.2

Changed database profiles to be in alphabetical order

APF-584: Added SQL Server, H2 and HSQLDB as profiles to archetypes. Tested and certified to work against Hibernate implementation. Couldn't get Oracle Express to work (http://www.nabble.com/AppFuse-2.0-with-Oracle-Express-tf3225784s2369.html), nor Derby Embedded (http://www.nabble.com/Issues-trying-to-use-Embedded-Derby-with-hibernate3-and-dbunit-tf3226221.html).

Fixed version for warpath plugin and changed appfuse-maven-plugin's version to match appfuse.version since they should be the same (at least initially).

Changed version to 2.0-m4-SNAPSHOT

Changed version to 2.0-m3

APF-609: Moved WebTests to profile that only runs when -Dmaven.test.skip=true is not passed on. Changed activation on Cargo so it only runs when -Dmaven.test.skip=true is not passed in. This means you can run "mvn -Dmaven.test.skip" from the top-level directory and install AppFuse in 1:19 instead of 7 minutes+!

APF-606: Fixed issue with dbunit plugin executing before Hibernate and upgraded WTP to 1.5

Upgraded archetypes to Spring 2.0.2

Added plugin version numbers, as well as Eclipse and IDE plugins to archetypes. http://www.nabble.com/Maven-Plugins-and-Version-Numbers-tf3051399s2369.html

Changed version back to SNAPSHOT for M3 development

Preparing for 2.0 M2 Release

Removed WEB-INF/applicationContext-resources.xml as its a duplicate of src/main/resouces/applicationContext-resources.xml in web/common/src/main/resources. Changed web.xml and test cases to match. Also added provided dependencies to archetypes so web-tier junit tests are possible.

APF-564: Split modular archetype into 4 different archetypes, one for each web framework

APF-564: Split modular archetype into 4 different archetypes, one for each web framework