The Cobertura plugin causes Maven to download inter-submodule dependencies from
external repositories
-----------------------------------------------------------------------------------------------------
Key: MCOBERTURA-152
URL: https://jira.codehaus.org/browse/MCOBERTURA-152
Project: Maven 2.x Cobertura Plugin
Issue Type: Bug
Affects Versions: 2.6
Environment: Fedora 13 (32bit)
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode)
Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
Java version: 1.6.0_20
Java home: /usr/java/jdk1.6.0_20/jre
Default locale: hu_HU, platform encoding: UTF-8
OS name: "linux" version: "2.6.34.9-69.fc13.i686.pae" arch: "i386" Family:
"unix"
Reporter: Kolos Tatar
This morning a colleague showed me that on our multimodule project, if we run
"mvn test" in the parent directory it runs different test code than what we run
if we run "mvn cobertura:cobertura".
After some debugging and investigation it turned out that we have
inter-submodule dependencies in our project and a unit test in one of the
submodules refers to a class in another submodule. If we run "mvn test" from
the parent directory, it will use the artifact generated by the submodule
providing the class being referred to, however if we run "mvn
cobertura:cobertura", Maven will not use the artifact provided by the other
submodule, but will go to the external repositories straight away and download
the same artifact. This renders the coverage analysis result kind of useless as
we're not testing the code we have in our hands, but mixed code.
Just a note - this ticket has nothing to do with aggregating the coverage
results.
--
This message is automatically generated by JIRA.
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
