The differences between what I have and what you recommend are:
a) I don't have 'clean'
b) I don't have the -D's. So, I'm first running the regular mvn
install and unit tests, and all is well, and then I ran sonar and
things failed.
I don't know if I can reproduce this.
I'm inclined to start by adding 'clean'.
On Mon, Jun 22, 2009 at 3:53 PM, Freddy Mallet<
freddy.mallet@...> wrote:
> Hi Benson,
> In any case, your sources need to be compile, it's why we recommend [1] to
> launch
> mvn clean install -Dtest=false -DfailIfNoTests=false
> and then
> mvn sonar:sonar
> Could you configure your hudson job to do first this compilation ? If you
> still have an error, please send your log file.
> Freddy
> [1] -
http://docs.codehaus.org/display/SONAR/Collect+data>
> On Mon, Jun 22, 2009 at 5:15 PM, Benson Margulies <
bimargulies@...>
> wrote:
>>
>> I've set my standard hudson job for my project to run Sonar every time.
>>
>> The main maven build ran clean. No errors.
>>
>> The subsequent sonar processing got failures from undefined methods:
>> as if the sonar run of surefire somehow ended up with a mixture of old
>> and new code.
>>
>> I don't know where to start diagnosing this. Help?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>
http://xircles.codehaus.org/manage_email>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
