The Maven Jetty plugin has been updated to version 6.1.18. Apart from being a more stable version that the previous one (6.1.12.rc2), it adds the <reload> configuracion option (available from version 6.1.18 onwards). In particular, the plugin has been configured with <reload>manual</reload>. This way Jetty does not scan for changes to project files. Instead, it is necessary to hit "ENTER" key on the Jetty console whenever we want Jetty to reload the application.
Manual reloading has a number of advantages over automatic reloading:
+ ZK can manage by itself the reloading of .zul pages (without intervertion of Jetty).
+ Whenever a developer creates/modifies "n" non ZK-managed files (e.g. .java files) to develop/fix a feature, she/he hits RETURN (after all modifications are done) to verify the changes, causing Jetty to reload the application only once (instead of "n" times when using automatic reloading).
Minimizing the number of times Jetty reloads the application is important, since class loaders do not release memory properly after reloading (in consequence, after a number of reloads, Jetty must be restarted; as usual, JVM memory options can also be used to increase available memory if desired).
Relocated dependencies in Maven central repository haven been updated (pom.xml files), style of inclusion of dependencies has been improved (pom.xml files), profile-based approach (root pom.xml) has been improved (bug fixed for supporting multiple databases, PostgreSQL has been set as the default database, and addition of HSQLDB), README.txt updated, and JavDoc for navalplanner-business code.
Now, by default, only resources matching "*spring-config.xml" or "*hibernate.cfg.xml" located directly on "src/main/resources", or "*spring-config-test.xml" or "*hibernate-test.cfg.xml" located directly on "src/test/resources" are filtered. To apply the patch, rember to execute "mvn clean install" from root directory.
Now filtering is applied by default only to files matching "*spring-config*.xml" and "*hibernate.cfg*.xml" located directly under "src/{main,test}/resources". After installing the patch, remember to execute "mvn clean install" from root directory.
