Uploaded image for project: 'Build'
  1. Build
  2. BUILD-23

Don't install nor deploy clover-instrumented artifacts

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • POMs 10
    • None
    • Poms
    • None

    Description

      This is causing issues such as MGNLEE-162 - clover-instrumented get installed in our local repositories, and somehow, despite them being built with the correct name (...-bundle-clover.zip for instance), they end up being copied to the local repo as ..-bundle.zip, thus overriding the "real" bundle. This does not affect the deploy phase, which is why this is only occuring when the same local repo was used to build module-bundles and the ee-bundle, for instance.

      We can avoid this by using the instrument-test goal instead of instrument.
      See http://forums.atlassian.com/thread.jspa?messageID=257322053

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                gjoseph Magnolia International
                gjoseph Magnolia International
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: