Thanks for the clarification, Brett.
What can the maven-clover2-plugin do to ensure that only classified
artifacts are resolved if they are available?
On 03/02/2009, at 9:17 AM, Brett Porter wrote:
Yes, that's expected - artifacts with a particular classifier are
considered different to artifacts with a different or no classifier.
On 02/02/2009, at 5:44 PM, Nick Pellow wrote:
Hi,
The maven-clover2-plugin creates both a classified and a normal jar
artifact for each sub-module it builds.
I have a problem, where I am seeing both a classified _and_ a non-
classified artifact being put on the classpath under certain
circumstances.
e..g
[INFO] Compiling 3 source files to target\clover\test-classes
[DEBUG] com.app:app:jar:1.0-SNAPSHOT (selected for null)
[DEBUG] com.app:app-domain:jar:clover:1.0-SNAPSHOT:compile
(selected for compile)
... and ...
[DEBUG] com.app:app-mail:jar:clover:1.0-SNAPSHOT:compile
(selected for compile)
[DEBUG] com.app:app-domain:jar:1.0-SNAPSHOT:compile (selected
for compile)
This debug output shows that both com.app:app-domain:jar:clover:
1.0-SNAPSHOT and com.app:app-domain:jar:1.0-SNAPSHOT:compile are on
the compile time classpath.
Is this expected behavior? Is there something possibly
misconfigured that will cause this?
Cheers,
Nick Pellow
Atlassian Clover.
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
