On 18/12/09 11:45 PM, Andrus Adamchik wrote:
I think we need "clean install", not just "clean test" on Hudson. This failure seems to be due to the test linked against the old piece of code:
OK. I changed it. I don't understand Maven despite having slightly used it for some years now. The problem with 'install' is just that it takes so long. I don't understand why we want to install anything: can't the modules just build themselves against the compiled code in the other modules? Do they have to build against what is 'installed'? I'm having similar problems with Clover [1] where it builds and instruments the files, but then seems to find the uninstrumented classes. There I'm using: -Dmaven.test.skip=true -Dmaven.clover.licenseLocation=/export/home/hudson/tools/clover/latest/lib/clover.license javadoc:javadoc checkstyle:checkstyle findbugs:findbugs com.atlassian.maven.plugins:maven-clover2-plugin:instrument com.atlassian.maven.plugins:maven-clover2-plugin:aggregate com.atlassian.maven.plugins:maven-clover2-plugin:clover That seems to work in other projects, but not for us. I'm guessing it finds 'installed' files which are not instrumented, or something like that.
Wonder if we can have profile to skip docs generation for that..?
Also why is docs a problem?
Only because it adds a lot of time to the build process. Even as it is without the docs, we are looking at 90 minutes to run the tests. Ari [1] http://hudson.zones.apache.org/hudson/view/Cayenne/job/Cayenne-doc/clover/ -- --------------------------> Aristedes Maniatis GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
