I've updated a few things in the maven scripts we use: 1. The support-common POM now takes in certain properties which can be defined in child POMs, to determine behaviour. Defaults are provided in the support-common POM, so default behaviour won't change from what you are used to. 1.1. "defaultTestGroup", which defaults to "functional" - the default TestNG group for Surefire to run 1.2. "javadocPhase", the default phase in which to generate javadocs. Defaults to "package". 2. The JBoss Cache core POM has changed, such that: 2.1. "mvn package" no longer generates javadocs and user guides, etc. This now *only* compiles, tests and generates a jar file. 2.2. Skip tests above by doing "mvn package -Dmaven.test.skip=true" 2.3. Javadocs are now generated when you do a "mvn install". 2.4. Generate docs by specifying the "Docs" profile, in any phase. E.g., "mvn package -P Docs" will be exactly the same as "mvn package" prior to this change. 2.5. Changed the way you specify which test groups to run. No longer a system property (-Dgroups=functional) but now using profiles (-P test-functional). (The sys properties tripped up the javadoc plugin!!) 2.6. Default test group run is now "unit" and not "functional". Run functional tests by doing "mvn test -P test-functional". See README-Maven.txt in jbosscache-core for more details. Cheers, -- Manik Surtani Lead, JBoss Cache manik(a)jboss.org _______________________________________________ jbosscache-dev mailing list jbosscache-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache-dev