Yeah, I had those problems. Its not as easy as ‘mvn clean install’ because a
good number of them fail without the intermediate assemble stage.
I did get the unit tests to run with the following:
./compile.pl -Pjarsigner.skip=true -Pbuild-bamboo install
./assemble.pl -Dopennms.home=/opt/opennms -Pjarsigner.skip=true -Pbuild-bamboo
install
./compile.pl -Pjarsigner.skip=true -Pbuild-bamboo -t —fail-never
-Penable.jacoco jacoco:prepare-agent test jacoco:report
./compile.pl -Pjarsigner.skip=true -Pbuild-bamboo sonar:sonar
After I added this profile to the pom.xml:
<profile>
<id>enable.jacoco</id>
<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.2.201409121644</version>
</plugin>
</plugins>
</build>
</profile>
and I also moved the <argLine>-Xmx1024m</argLine> from the
maven-surefire-plugin <configuration> section to be a global property to fix
the jacoco prepare-agent conflict.
33.2% test coverage on code.
99.8% test success, most likely due to some java primitive autoboxing changes I
was testing.
Ron
On Sep 14, 2014, at 3:40 PM, Simon Walter <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hej Ron,
>
> On 10.09.2014 04:35, Ronald Roskens wrote:
>> Anybody successfully been able to run the unit tests with
>> sonarqube
> 4.4 & java 2.4 ecosystem?
>>
>> The maven target sonar:sonar no longer runs unit tests. If I try
>> and
> enable unit-tests during the compile stage, I run into issues like
> ${install.database.driver} where properties set via assembly don’t yet
> exist in the populated form.
>
> you probably ran into this:
> http://www.sonarqube.org/unit-test-execution-in-sonarqube/
>
> also this is helpful:
> http://docs.codehaus.org/display/SONAR/Analysis+Parameters
>
> - --
> Regards
> Simon
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJUFf0mAAoJEL8uhqS1MuWQMg0H/RzWOS3S7rwJ+rtyzXnlos6m
> dmPds4b0ebiiH5INvnKCDT8TIpTmVnm6CYA5/Es5QkVDsgwJvwPieebl5bPW+Y7a
> oWYoRvdH0MWYrG/tLkfwUtc366oeJq8KZzT448jFxXTc8okbHUYtCZV64FSLyH54
> yYftKpzaT1Yv9EB2iSdYGgk6PrvFyDtGceUvnbg3KAIhXVxJOEa3n/oEsTWy6f8d
> rA/UaIOFjS0e+5DbxkwfvcOhPH6hmw9ctUcdmbKfV9pKkv0pHOznbg8w37EF+TWU
> YJ/4FNYKYEURqnCq8E3PAsvVCvz/S0rcMYY5wBbTqUo2YoWzEiDQ2yIWoV2+Zho=
> =ir9t
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of this
> page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
