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

Migrate Clover-for-Grails release artifacts to new repository

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.1.6
    • Grails Plugin
    • None
    • 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.

      According to information received from Grails developers, the SVN https://svn.codehaus.org/grails-plugins/ repository will no longer be used for keeping release artifacts and will become read-only.

      Instead of this the Artifactory repository will be used for plugins.

      Therefore, we should migrate our Clover-for-Grails plugin according to the following procedure:

      http://grails.github.com/grails-howtos/en/migrateToTheNewCentralRepository.html

      Affects: our build script

      Open questions:
      1) What about version compatibility. We support Grails 1.2 or later, but new release deployment mechanism requires Grails 2.0 or later - check if it will not interfere (I guess that should not)

      2) What about old clover-for-grails releases? Should we migrate them to Artifactory as well?

          Form Name

            [CLOV-1089] Migrate Clover-for-Grails release artifacts to new repository

              Unassigned Unassigned
              mparfianowicz Marek Parfianowicz
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 8h
                  8h
                  Remaining:
                  Remaining Estimate - 8h
                  8h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified