On Wed, May 21, 2008 at 8:09 PM, Jerome Lacoste <[EMAIL PROTECTED]> wrote: > Clovered EAR / WAR artifacts lacks clovered versions of transitive > dependencies. Cf: http://jira.codehaus.org/browse/MCLOVER-70. This > issue still exists in the maven clover plugin 3.7 from atlassian. > We've tested maven 2.0.6 and 2.0.9. > > The issue is caused apparently as the clover plugins tries to modify > the project artifacts list in a forked lifecycle, but the change is > not propagated to the mojos executed later on. My understanding is > that the way clover tries to achieve this is not possible, as the > forked lifecycle ends before the war/ear mojos are executed. > > Can someone confirm this reasoning, and maybe provide an alternative > solution to this problem ?
Changing to developer list. [original message: http://www.mail-archive.com/[EMAIL PROTECTED]/msg85358.html] The issue might look to come from the DefaultPluginManager. http://maven.apache.org/ref/2.0.4/maven-core/xref/org/apache/maven/plugin/DefaultPluginManager.html#1117 [1] It looks like it overrides the transitive dependencies after re-resolving them, hence losing the changes the clover plugin made. The non transitive dependencies don't seem to be overriden (with a comment mentionning clover). Does anyone know if the difference in behavior between transitive and non transitive dependencies is intended ? We're going to try to patch the class and open an issue if that works for us. Jerome [1] Cf. http://developer.atlassian.com/jira/browse/CLMVN-25?focusedCommentId=16756#action_16756 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
