Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-184

Artifact[ejb:my.wonderful.artifact] has 2 candidates, please provide a classifier.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • Icon: High High
    • won't fix
    • None
    • Maven plugin
    • None

    • Linux, jdk1.6, maven 2.0.8, maven-clover-plugin 3.6

      Running clover over our project with maven gives

      [INFO] Executed tasks
      [INFO] [ear:generate-application-xml]
      [INFO] ------------------------------------------------------------------------
      [ERROR] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Artifact[ejb:my.wonderful.artifact] has 2 candidates, please provide a classifier.

      A little google'ing directs to http://jira.codehaus.org/browse/MCLOVER-77 which lets me assume that the atlassian plugin has similar problems. Can you verify that, please?

      It talks about a way to workaround that problem:

      "This can be fixed by specifying a classifier in the Modules section for the ear, but means that you must create two poms (or use complicated profiles), one with the classifier set to clover and one set to the empty string. This is a pain and hard to maintain."

      Can you tell detail of how to specify a classifier there?

      Thanks,
      Thomas

            [CLOV-184] Artifact[ejb:my.wonderful.artifact] has 2 candidates, please provide a classifier.

            Owen made changes -
            Workflow Original: New Clover Workflow [ 896715 ] New: New Clover Workflow - Restricted [ 1473104 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 895127 ] New: New Clover Workflow [ 896715 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 123539 ] New: Clover Workflow [ 895127 ]
            Marek Parfianowicz made changes -
            Fix Version/s New: won't fix [ 38394 ]
            Nick made changes -
            Resolution New: Invalid [ 6 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            Nick added a comment -

            Sorry Thomas,

            I can not provide any further information on this.

            Cheers,
            Nick

            Nick added a comment - Sorry Thomas, I can not provide any further information on this. Cheers, Nick

            Nick added a comment -

            Hi Thomas,

            Have you tried specifying the classifier as outlined here: http://maven.apache.org/plugins/maven-ear-plugin/modules.html ?
            Clover classifiers all clovered artifacts with the "clover" classifier.

            Something I've not tested however is worth a try: instead of using 2 pom.xmls, or a profile would be to simply specify the classifier as a maven property.
            The default should be the empty string, and when you run clover, pass the property on the command line using -D .

            Also, please also upgrade to the latest version of the maven-clover2-plugin, (version 2.3.2).

            Let me know how you go.

            Cheers,
            Nick

            Nick added a comment - Hi Thomas, Have you tried specifying the classifier as outlined here: http://maven.apache.org/plugins/maven-ear-plugin/modules.html ? Clover classifiers all clovered artifacts with the "clover" classifier. Something I've not tested however is worth a try: instead of using 2 pom.xmls, or a profile would be to simply specify the classifier as a maven property. The default should be the empty string, and when you run clover, pass the property on the command line using -D . Also, please also upgrade to the latest version of the maven-clover2-plugin, (version 2.3.2). Let me know how you go. Cheers, Nick
            BrendanA made changes -
            Component/s New: Maven plugin [ 12666 ]
            Thomas Arand created issue -

              npellow Nick
              924489c72524 Thomas Arand
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: