Uploaded image for project: 'Maven Deploy Plugin'
  1. Maven Deploy Plugin
  2. MDEPLOY-118

Enable deployment of attached release artifacts if POM is identical

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Reopened
    • Major
    • Resolution: Unresolved
    • 2.4
    • None
    • None
    • Windows XP SP3

    Description

      In the context of the build of a native application, one might have zip-artifacts containing several DLL or so files like:
      boost:boost_regex:1.34.1:zip

      In order to distinguish between platforms, it seems to be recommended to use the classifier:
      boost:boost_regex:1.34.1:zip:bin-x86-windows-vc8
      or:
      boost:boost_regex:1.34.1:zip:bin-x86-linux2.6-gcc3.3

      If a Maven repository manager is configured to prevent from re-deploying release artifacts (and I believe it should be), it is not possible to deploy attached artifacts when the POM is the same because the POM is deployed twice. The deploy plugin could check that the POM is already deployed and is the same than the local one (modulo platform-dependent line-break concerns, and that's important!), then choose not to deploy it but only the attached artifact.

      In the example above, it could enable to deploy the boost:boost_regex:1.34.1:zip:bin-x86-windows-vc8 artifact from a Windows machine(coming along with a boost:boost_regex:1.34.1:pom artifact), then to deploy the boost:boost_regex:1.34.1:zip:bin-x86-linux2.6-gcc3.3 artifact from a Linux machine (coming along with the same boost:boost_regex:1.34.1:pom artifact, that will not be deployed since it is identical to the first one deployed).

      Maybe this could be generalized to any kind of artifact? If the artifact to deploy is the same, the plugin should not fail and simply skip the deployment of that artifact?

      I post that bug here on a suggestion of Brett Porter (see the MRM-1357 bug) since it is quite unclear to me whether it is a MRM or deploy plugin concern.

      That bug might also be related to:

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. MDEPLOY-117 Use GAV from specified pomFIle but not deploy the pom

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MRM-1357 Allow deployment of attached release artifacts if POM is identical

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. MDEPLOY-154 Rewrite page 'deploy with classifier'

          • Major - Major loss of function.
          • Closed

          Wish - General wishlist item. MDEPLOY-114 Add an option to not fail when remote file already exists and redeploy is forbidden

          • Major - Major loss of function.
          • Closed
          supercedes

          New Feature - A new feature of the product, which has yet to be developed. MDEPLOY-156 Add flag to 'ignoreReleaseDeployErrors' to ease multi module release builds with classifiers.

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MDEPLOY-126 Deploy only artifacts which have been explicitly attached

          • Major - Major loss of function.
          • Closed
          links to

          Web Link GitHub Pull Request #28

          Activity

            People

              Unassigned Unassigned
              bfreuden Bruno Freudensprung
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: