I don't really use Clover, so hopefully someone else who uses Clover will reply with more specific info.
Classifier is simply a child node of dependency: <dependency> <groupId/> <artifactId/> <version/> <scope/> <classifier/> </dependency> So you'd want to use <classifier>clover</classifier> in your particular case, to target the -clover.jar file. Wayne On 5/10/07, Maya Nayak <[EMAIL PROTECTED]> wrote:
INFO - INFO - [INFO] [clover:instrumentInternal] INFO - [WARNING] No Clover instrumentation done as no matching sources files found INFO - [INFO] [ear:generate-application-xml] INFO - [INFO] ------------------------------------------------------------------------ INFO - [ERROR] BUILD FAILURE INFO - [INFO] ------------------------------------------------------------------------ INFO - [INFO] Artifact[jar:com.tsysprepaid.psa:psa-common] has 2 candidates, please provide a classifier. INFO - [INFO] ------------------------------------------------------------------------ psa-common is a separate project and i ran clover:instrument successfully on that. it created psa-common-<version num>-clover.jar in the local repository and after that my other project which lists psa-common as a dependency started to fail on clover:instrument with the above error. It appears that since psa-common now has psa-common-<version num>.jar and psa-common-<version num>-clover.jar in the repository, clover is unable to resolve it and fails it with message artificat has 2 candidates, please provide a classifier. Has anyone come across this issue? How do I provide a classifier? Is there any way to prevent clover from installing clover artifacts into m2 repository? Thanks. Maya --------------------------------- Need Mail bonding? Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
