Maven
  1. Maven
  2. MNG-2664

Add native support for webdav

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.4
    • Fix Version/s: 2.0.9
    • Labels:
      None
    • Complexity:
      Intermediate
    • Patch Submitted:
      Yes
    • Number of attachments :
      2

      Description

      Actually with maven 2.0.4 we can't use the deploy:deploy-file goal to add an artifact on a remote repository with webdav.
      This is really annoying for archiva which supports webdav for uploads.

      1. MNG-2664.diff
        6 kB
        Brett Porter
      2. MNG-2664.patch
        1 kB
        Arnaud Heritier

        Issue Links

          Activity

          Hide
          Arnaud Heritier added a comment -

          Patch allowing to use webdav protocol to remotely install artefacts in a repository.

          Show
          Arnaud Heritier added a comment - Patch allowing to use webdav protocol to remotely install artefacts in a repository.
          Hide
          Trygve Laugstøl added a comment -

          This is not a good idea until the webdav wagon is working properly. It's probably better to add support loading custom wagons in the deploy plugin directly.

          Show
          Trygve Laugstøl added a comment - This is not a good idea until the webdav wagon is working properly. It's probably better to add support loading custom wagons in the deploy plugin directly.
          Hide
          Joakim Erdfelt added a comment -

          what's not working with the webdav wagon provider?
          we use it regularly.

          /me checks the WAGON jira ...

          Show
          Joakim Erdfelt added a comment - what's not working with the webdav wagon provider? we use it regularly. /me checks the WAGON jira ...
          Hide
          Arnaud Heritier added a comment -

          Trygve, I agree but the the best is the enemy of good. I we can't fix the deploy plugin before the 2.0.5 release, I think that it can be a temporary workaround. It's very annoying to have to modify the original distribution for each user who want to upload artifacts using webdav.
          WDYT ?

          Show
          Arnaud Heritier added a comment - Trygve, I agree but the the best is the enemy of good. I we can't fix the deploy plugin before the 2.0.5 release, I think that it can be a temporary workaround. It's very annoying to have to modify the original distribution for each user who want to upload artifacts using webdav. WDYT ?
          Hide
          Jason van Zyl added a comment -

          Sure, why not drop it in. I think people use it quite a bit. I think brett was fighting to get the extensions working but for now I would say just toss it in the core. Enough people use it.

          Show
          Jason van Zyl added a comment - Sure, why not drop it in. I think people use it quite a bit. I think brett was fighting to get the extensions working but for now I would say just toss it in the core. Enough people use it.
          Hide
          Brett Porter added a comment -

          This would make it harder - actually one of the bugs we encounter with it as an extension will cause a permanent problem if we drop it into the core, unless we also drop in (and exclude) jaxen, jdom, and slide (and maybe more, I think it might use some commons-*).

          It'd be Maven 1.x all over again.

          Show
          Brett Porter added a comment - This would make it harder - actually one of the bugs we encounter with it as an extension will cause a permanent problem if we drop it into the core, unless we also drop in (and exclude) jaxen, jdom, and slide (and maybe more, I think it might use some commons-*). It'd be Maven 1.x all over again.
          Hide
          Jason van Zyl added a comment -

          This is really going to required more heavy duty changes. Like running extensions like we do plugins.

          Show
          Jason van Zyl added a comment - This is really going to required more heavy duty changes. Like running extensions like we do plugins.
          Hide
          Arnaud Heritier added a comment -

          I'm sad to hear it. I hope maven 2.1 will be available quickly.

          Show
          Arnaud Heritier added a comment - I'm sad to hear it. I hope maven 2.1 will be available quickly.
          Hide
          Wendy Smoak added a comment -

          To use deploy:deploy-file with webdav, you can use a simple pom file containing the wagon-webdav build extension.

          Either save it as pom.xml in the current directory, or use -f on the command line to point Maven at an alternate file.

          See: http://maven.apache.org/archiva/guides/getting-started/maven-configuration.html at the bottom.

          Show
          Wendy Smoak added a comment - To use deploy:deploy-file with webdav, you can use a simple pom file containing the wagon-webdav build extension. Either save it as pom.xml in the current directory, or use -f on the command line to point Maven at an alternate file. See: http://maven.apache.org/archiva/guides/getting-started/maven-configuration.html at the bottom.
          Hide
          Arnaud Heritier added a comment -

          It's what I'm doing for now. Thanks for this explanation in the documentation. I didn't see it some weeks ago.

          Show
          Arnaud Heritier added a comment - It's what I'm doing for now. Thanks for this explanation in the documentation. I didn't see it some weeks ago.
          Hide
          Jason van Zyl added a comment -

          Ok, not going into the core because of potential conflicts. This can work as an extension.

          Show
          Jason van Zyl added a comment - Ok, not going into the core because of potential conflicts. This can work as an extension.
          Hide
          Brett Porter added a comment -

          being pedantic, should be won't fix

          Show
          Brett Porter added a comment - being pedantic, should be won't fix
          Hide
          Brett Porter added a comment -

          it appears that this works with the changes since 2.0.5 for plugin isolation.

          The only problem is the injection of commons-logging which can be addressed through shading, so I'll take a look.

          Show
          Brett Porter added a comment - it appears that this works with the changes since 2.0.5 for plugin isolation. The only problem is the injection of commons-logging which can be addressed through shading, so I'll take a look.
          Hide
          Arnaud Heritier added a comment -

          I love you Brett

          Show
          Arnaud Heritier added a comment - I love you Brett
          Hide
          Brett Porter added a comment -

          attaching an alternate solution that also works, should the slf4j inclusion prove to be problematic. It provides a pre-shaded webdav lib

          Show
          Brett Porter added a comment - attaching an alternate solution that also works, should the slf4j inclusion prove to be problematic. It provides a pre-shaded webdav lib
          Hide
          Arnaud Heritier added a comment -

          For others users, you can also use the -Durl=http:// without the dav protocol to deploy files and it works without having a pom with the webdav extension. Brett, is it documented somewhere ? If not, where can we put it ?

          Show
          Arnaud Heritier added a comment - For others users, you can also use the -Durl=http:// without the dav protocol to deploy files and it works without having a pom with the webdav extension. Brett, is it documented somewhere ? If not, where can we put it ?

            People

            • Assignee:
              Brett Porter
              Reporter:
              Arnaud Heritier
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: