[
http://jira.codehaus.org/browse/MCOBERTURA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169461#action_169461
]
Frédéric Camblor commented on MCOBERTURA-96:
--------------------------------------------
To finish up spamming this issue (;)) I succeeded temporarily in generating my
cobertura report by :
- changing my test framework scope (switching from "test" to "compile" ... eurk
this is bad ! ;))
- deleting my spring reference dependency
... these are only temporary measures (since I don't want to package my test
framework with my BlehProject !) => but it demonstrates the problem :-)
> Jar classpath ordering issue during test execution
> --------------------------------------------------
>
> Key: MCOBERTURA-96
> URL: http://jira.codehaus.org/browse/MCOBERTURA-96
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: Maven 2.0.9
> Reporter: Frédéric Camblor
> Priority: Blocker
>
> I have different test result between the surefire test execution and the
> cobertura test execution.
> Looks like it is a classloading problem ...
> I use a test framework based which weaves spring classes in order to override
> spring file loading policies.
> => woven spring classes are added to my TestFramework.jar file.
> Then, my project (let's name it BlehProject) depends on spring spring on
> compile scope execution.
> It depends on my TestFramework artifact too (and firstly !) on test scope
> execution.
> That is to say I have something like this in my pom.xml :
> <!-- Dependency to my test framework artefact... which will
> weave spring classes with aspects
> Artefact must be defined before spring framework artefact in
> order to provide woven spring classes !
> -->
> <dependency>
> <groupId>foo.bar.test</groupId>
> <artifactId>MyTestFramework</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.springframework</groupId>
> <artifactId>spring</artifactId>
> </dependency>
> Then, during the surefire test execution, I enabled the debug feature in
> order to debug things in my tests => I saw spring classes were nicely woven
> Nevertheless, during cobertura test execution, I enabled the debug feature
> too, and saw a "standard" (not woven by my test framework) spring execution.
> => This is the reason why I wonder if cobertura is nicely using the good
> classpath order defined in pom.xml 's <dependencies> section.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
