> [WARNING] JAR will be empty - no content was marked for inclusion! Yes this is normal. At least for us. It occurs a lot when building each submodule's -tests.jar
All tests which extend DataModelTestCase or SiteTestCase are only expected to execute in a war submodule that provides the basic site-spi implementation (eg configuration.properties, modes.xml, and views.xml). Examples of these modules are sesat-kernel/generic.sesam/war and sesat-kernel/generic.sesam/sesam.com/war. Therefore the test classes must be bundled into a separate jar file (-tests.jar) that can be referenced and executed in the war submodule. http://maven.apache.org/guides/mini/guide-attached-tests.html Maybe there's a way to make the build a little more intelligent and skip the jar:test-jar goal when src/main/test (or whatever testSourceDirectory is) is empty|non-existent...? It would no doubt make the whole build a little faster. ~mck -- Linux, because I'd rather own a free OS than steal one that's not worth paying for. | semb.wever.org | sesat.no | sesam.no |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
