quattor / ncm-cdispd

Node Configuration Manager Configuration Dispatch Daemon
www.quattor.org
Other
2 stars 5 forks source link

build failure if no clean before build #5

Closed jouvin closed 10 years ago

jouvin commented 10 years ago

mvn test fails in pod2man if it was already run once:

[INFO] --- exec-maven-plugin:1.2:exec (pod2man) @ ncm-cdispd ---
Can't open target/doc/pod/ncm-cdispd.pod: No such file or directory at /exp/si/jouvin/GitRepositories/Quattor/ncm-cdispd/target/dependency/build-scripts/pod2man.pl line 74
Generating man page from target/lib/perl/ncm-cdispd.pod
Creating man page for target/doc/pod/ncm-cdispd.pod, ncm-cdispd.8

In addition at each run it adds another .pod extension... The workaround is to use mvn clean test.

jouvin commented 10 years ago

It seems that there are other problems for building ncm-cdispd. mvn clean package returns the following error on my SL6 machine:

[INFO] --- exec-maven-plugin:1.2:exec (prove) @ ncm-cdispd ---
Cannot determine source for src/test/perl at /usr/share/perl5/App/Prove.pm line 496
jrha commented 10 years ago

I cannot reproduce this in my build environment, can you verify that your environment is setup correctly? For reference I'm running Maven 3.0.5 on OpenJDK 1.7

jouvin commented 10 years ago

Turned out to be caused by missing src/test tree (as it is currently empty) and a very old version of the build tools being used (1.29).

jouvin commented 10 years ago

Even with the previous pom.xml change, mvn test fails once every 2 runs with (on SL6.5):

[INFO] --- exec-maven-plugin:1.2:exec (pod2man) @ ncm-cdispd ---
Can't open target/doc/pod/ncm-cdispd.pod: No such file or directory at /exp/si/jouvin/GitRepositories/Quattor/ncm-cdispd/target/dependency/build-scripts/pod2man.pl line 74
Generating man page from target/lib/perl/ncm-cdispd.pod
Creating man page for target/doc/pod/ncm-cdispd.pod, ncm-cdispd.8
jouvin commented 10 years ago

pod/man generation problem fixed by last revision of the commit (pom.xml fixes).

jrha commented 10 years ago

Issue closed?

jouvin commented 10 years ago

Will be closed by merging the referenced commit which is part of the pending PR #9 (almost ready to be merged as far as I'm concerned).

jrha commented 10 years ago

Ok, thanks.