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

move the maven plugin to apache so we don't have to edit settings.xml

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      please can you move the maven plugin to apache server ?

      for now we have to edit .m2/settings.xml

      <pluginGroups>
      <pluginGroup>com.atlassian.maven.plugins</pluginGroup>
      </pluginGroups>

      but I don't want to force the users to edit this file, they should be able to use directly. Like that I would just have to replace the maven task clover by clover2.

      we consider that as a show stopper, for now ww will stick to clover1 or cobertura.

          Form Name

            [CLOV-371] move the maven plugin to apache so we don't have to edit settings.xml

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3342065 ] New: JAC Suggestion Workflow 3 [ 3584535 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Michael Andreacchio made changes -
            Workflow Original: New Clover Workflow [ 897961 ] New: JAC Suggestion Workflow [ 3342065 ]
            Assignee Original: Nick [ npellow ]
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 896218 ] New: New Clover Workflow [ 897961 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 147716 ] New: Clover Workflow [ 896218 ]
            Nick made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Reopened [ 4 ] New: Closed [ 6 ]
            Nick made changes -
            Fix Version/s New: 2.4 [ 13971 ]
            Fix Version/s Original: post 2.4 [ 13646 ]
            Nick made changes -
            Resolution Original: Not a bug [ 12 ]
            Status Original: Closed [ 6 ] New: Reopened [ 4 ]

            Nick added a comment -

            re-opening to provide a fix version

            Nick added a comment - re-opening to provide a fix version

            Nick added a comment -

            Hi Sebastien,

            Thanks for reporting this - the feedback helped us improve the documentation and will hopefully make this clearer for future users.

            You will indeed need the licenseLocation in the reporting section's configuration as well.

            Please let me know if there is anything else we can do to help.

            Best Regards,
            Nick Pellow

            Nick added a comment - Hi Sebastien, Thanks for reporting this - the feedback helped us improve the documentation and will hopefully make this clearer for future users. You will indeed need the licenseLocation in the reporting section's configuration as well. Please let me know if there is anything else we can do to help. Best Regards, Nick Pellow

            sebastien added a comment -

            thanks. it works well like that. Sorry for the confusion, I just followed
            the steps on the web site.

            Should I put the license in the reporting for build ?

            that what I have now
            <reporting>
            ....
            <plugin>
            <groupId>com.atlassian.maven.plugins</groupId>
            <artifactId>maven-clover2-plugin</artifactId>
            <configuration>

            <licenseLocation>clover.license</licenseLocation>
            </configuration>
            </plugin>
            ...

            2008/11/11 Nick Pellow [Atlassian] (JIRA) <jira@atlassian.com>

            sebastien added a comment - thanks. it works well like that. Sorry for the confusion, I just followed the steps on the web site. Should I put the license in the reporting for build ? that what I have now <reporting> .... <plugin> <groupId>com.atlassian.maven.plugins</groupId> <artifactId>maven-clover2-plugin</artifactId> <configuration> <licenseLocation>clover.license</licenseLocation> </configuration> </plugin> ... 2008/11/11 Nick Pellow [Atlassian] (JIRA) <jira@atlassian.com>

              Unassigned Unassigned
              aed241f97497 sebastien
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: