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?

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

            Marek Parfianowicz added a comment - - edited

            Implemented. Support for Grails 1.2 is dropped. The "release" plugin from Grails 2.0.3 is be for deployment of the plugin.
            However, the Clover-for-Grails itself is compatible with Grails 1.3.x as well as Grails 2.x.

            Marek Parfianowicz added a comment - - edited Implemented. Support for Grails 1.2 is dropped. The "release" plugin from Grails 2.0.3 is be for deployment of the plugin. However, the Clover-for-Grails itself is compatible with Grails 1.3.x as well as Grails 2.x.

            > 1) Have you migrated all plugin artifacts from SVN to new grails repository?
            > In other words: is it possible to find in new repository all releases of all plugins which
            > were published before the day of switch?

            I believe we need to do one more sync from the Svn repository to
            repo.grails.org - Graeme should be able to confirm.

            > 2) I understand that all new releases have to be published in new repository
            > instead of SVN. But what about bugfixes of old releases?
            > For example: I have clover-3.0.2 in SVN and I want to publish a fix 3.0.2.1?
            > The problem is that external tools / documentation might still rely
            > on old location (svn) and old way of installation.

            All future plugin releases will have to go to the new repository. Note
            that we plan to switch plugins.grails.org to the new repository so
            that any tools using that domain should continue to work (unless they
            try to treat it as a Subversion repository). But anything that refers
            to svn.codehaus.org will only see stale data.

            > 3) How grails "install-plugin" works in such case? Does it scan for plugins
            > in both SVN and new repo?

            1.3.8 (& 1.3.9 which is due soon) use plugins.grails.org URLs, so
            people using those versions won't have to do anything at all. Users of
            1.3.7 and earlier will have to add

            grailsRepo "http://plugins.grails.org"

            to their repository definitions. It's an inconvenience, but we've
            tried to minimise the impact for end users.

            Marek Parfianowicz added a comment - > 1) Have you migrated all plugin artifacts from SVN to new grails repository? > In other words: is it possible to find in new repository all releases of all plugins which > were published before the day of switch? I believe we need to do one more sync from the Svn repository to repo.grails.org - Graeme should be able to confirm. > 2) I understand that all new releases have to be published in new repository > instead of SVN. But what about bugfixes of old releases? > For example: I have clover-3.0.2 in SVN and I want to publish a fix 3.0.2.1? > The problem is that external tools / documentation might still rely > on old location (svn) and old way of installation. All future plugin releases will have to go to the new repository. Note that we plan to switch plugins.grails.org to the new repository so that any tools using that domain should continue to work (unless they try to treat it as a Subversion repository). But anything that refers to svn.codehaus.org will only see stale data. > 3) How grails "install-plugin" works in such case? Does it scan for plugins > in both SVN and new repo? 1.3.8 (& 1.3.9 which is due soon) use plugins.grails.org URLs, so people using those versions won't have to do anything at all. Users of 1.3.7 and earlier will have to add grailsRepo "http://plugins.grails.org" to their repository definitions. It's an inconvenience, but we've tried to minimise the impact for end users.

            According to this documentation http://grails.org/doc/2.0.3/guide/plugins.html#repositories, we can use Maven repository format since Grails 1.3. It means that we'll have to drop support of Grails 1.2, as listed on http://confluence.atlassian.com/display/CLOVER/Supported+Platforms

            Marek Parfianowicz added a comment - According to this documentation http://grails.org/doc/2.0.3/guide/plugins.html#repositories , we can use Maven repository format since Grails 1.3. It means that we'll have to drop support of Grails 1.2, as listed on http://confluence.atlassian.com/display/CLOVER/Supported+Platforms

            Prioritizing (Major, 3.1.6) as we are not able to release new versions of clover-for-grails plugin into Grails SVN repository anymore.

            Marek Parfianowicz added a comment - Prioritizing (Major, 3.1.6) as we are not able to release new versions of clover-for-grails plugin into Grails SVN repository anymore.

            Marek Parfianowicz added a comment - - edited

            Updated http://confluence.atlassian.com/display/CLOVER/Clover-for-Grails+Installation+and+Upgrade+Guide - added information that we can install plugin by declaring dependency in BuildConfig.groovy file.

            Marek Parfianowicz added a comment - - edited Updated http://confluence.atlassian.com/display/CLOVER/Clover-for-Grails+Installation+and+Upgrade+Guide - added information that we can install plugin by declaring dependency in BuildConfig.groovy file.

            Excerpt from email:

            > BTW: are you able to tell when the svn repo will become read-only, as mentioned in migrateToTheNewCentralRepository.html ?

            This has already happened.
            Peter

            Peter Ledbrook
            Grails Advocate
            SpringSource - A Division of VMware

            Marek Parfianowicz added a comment - Excerpt from email: > BTW: are you able to tell when the svn repo will become read-only, as mentioned in migrateToTheNewCentralRepository.html ? This has already happened. Peter – Peter Ledbrook Grails Advocate SpringSource - A Division of VMware

              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