Larry-
try loading both dependencies in your local repository and running offline with
mvn -o (at least your dependencies will be found)
did you check cobertura for errors?
mvn -e -X cobertura:cobertura -Dquiet=true
take junit out of the mix and run testng as solo Test dependency then check
output folders
${project.reporting.outputDirectory}/cobertura.
if these tests fail you may have found a bug in which cause you need to file a
JIRA at
http://jira.codehaus.org/browse/MCOBERTURA
hth
Martin-
______________________________________________
Jogi és Bizalmassági kinyilatkoztatás/Verzicht und
Vertraulichkeitanmerkung/Note de déni et de confidentialité
Ez az
üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy
jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és
semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek
könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet
ezen üzenet tartalma miatt.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Wed, 27 Jul 2011 19:32:43 -0600
> Subject: Maven 2/3 and Cobetura plugin with both TestNG and JUnit tests (with
> Surefire plugin configuration)
> From: lar...@gmail.com
> To: dev@maven.apache.org
>
> I did send this to the users list, but got no response in over a week.
> I know dev lists are not a magical escalation path, but this might be
> a better venue for this email.
>
>
> I have an example project at https://gist.github.com/1090223
>
> This project has both a JUnit test and a TestNG test. Following some
> instructions online to get surefire be able to run both I added lines
> 19-45 in the pom.
>
> This works fine when running "mvn test", except it runs the TestNG
> tests twice. I can fix that by commenting out lines 34-43.
>
> Now when I run "mvn cobertura:cobertura", this is where things get weird.
>
> In Maven 2.2.1, it runs both TestNG and JUnit just fine, and produces
> the correct coverage.
>
> Now in Maven 3.0.3 it just runs the JUnit tests. (With lines 34-43
> still commented out). When I bring those back, this is the output:
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.company.JUnitTest
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> Running com.company.TestNGTest
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
> There are no tests to run.
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> So it appears to try to run both tests, but fails to actually run any
> tests, and gets 0% coverage.
>
> It appears there is something odd between Maven 2.2.1 and Maven 3.0.3
> when the cobertura plugin runs, and its reading of the Surefire plugin
> configuration.
>
> Ideally I would only use JUnit or TestNG, and this would not be a
> problem. However, we are using TestNG exclusively, and wanted to
> introduce a tool that currently only is executed as a JUnit test
> (Spock). I wanted to avoid changing all our tests from TestNG to JUnit
> unless absolutely necessary.
>
> It appears to be a regression from Maven 2.2.1 to Maven 3.0.3, unless
> it was a bug in Maven 2 that was fixed.
>
> -- Larry
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
