Yep, I've had it work with dav:https:// using Apache mod_webdav
-Stephen
On 1/30/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Graham Leggett a écrit :
> On Tue, January 30, 2007 3:49 pm, Aaron Digulla wrote:
>
>> I'm using wagon-webdav 1.0-beta-2 with maven-deploy-plugin 2.3
>> together wi
There is plenty of work done to create the collections (one at a time,
in order) in order to perform a PUT request.
What dav server are you using when you got this error?
The HTTP Response 500 is the likely culprit here.
- Joakim
Graham Leggett wrote:
> Hi all,
>
> As a test I have configured t
Graham Leggett a écrit :
On Tue, January 30, 2007 3:49 pm, Aaron Digulla wrote:
I'm using wagon-webdav 1.0-beta-2 with maven-deploy-plugin 2.3
together with Archiva (SVN SNAPSHOT build). Before 1.0-beta-2/2.3,
this was pretty unstable (every 3rd deploy would fail) but now, it
works pretty goo
On Tue, January 30, 2007 3:49 pm, Aaron Digulla wrote:
> I'm using wagon-webdav 1.0-beta-2 with maven-deploy-plugin 2.3
> together with Archiva (SVN SNAPSHOT build). Before 1.0-beta-2/2.3,
> this was pretty unstable (every 3rd deploy would fail) but now, it
> works pretty good (even though I still
Quoting Graham Leggett <[EMAIL PROTECTED]>:
Can anyone confirm whether this plugin has ever worked for them, and if
so, what DAV server is being used? I am using httpd v2.0.52 as shipped
default with RHEL4.
I'm using wagon-webdav 1.0-beta-2 with maven-deploy-plugin 2.3
together with Archiva
On Tue, January 30, 2007 3:08 pm, Aaron Digulla wrote:
> The simple workaround would be to create the directories manually
> until the bug is fixed.
I created each directory manually, up to and including the version number.
Once all the directories existed, the return code from wagon-webdav was
On Tue, January 30, 2007 3:08 pm, Aaron Digulla wrote:
> You do see the correct version in the output of Maven?
I saw maven download the v1.0-beta-2 jars and dependencies.
> The simple workaround would be to create the directories manually
> until the bug is fixed.
Unfortunately the end result
On Tue, January 30, 2007 3:09 pm, Aaron Digulla wrote:
> Which version of the maven-deploy-plugin do you use? Have you tried 2.3?
Yes (both natively as it's the latest release, and explicitly by adding it
to the pom) - made no difference.
Regards,
Graham
--
---
Quoting Graham Leggett <[EMAIL PROTECTED]>:
Have you tried with 1.0-beta-2 of wagon-webdav? This solved some
problems for me.
Which version of the maven-deploy-plugin do you use? Have you tried 2.3?
Regards,
--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limi
Quoting Graham Leggett <[EMAIL PROTECTED]>:
On Tue, January 30, 2007 1:55 pm, Aaron Digulla wrote:
Have you tried with 1.0-beta-2 of wagon-webdav? This solved some
problems for me.
Added the 1.0-beta-2 of wagon-webdav like this:
org.apache.maven.wagon
wagon-we
Hi all,
As a test I have configured the maven deploy:deploy-file goal to deploy to a
WebDAV server. The login and ssl part works fine, but the attempt to PUT
the file fails with a 403 response code (but not because of auth failure
according to the logs).
It looks like the plugin is not making an
On Tue, January 30, 2007 1:55 pm, Aaron Digulla wrote:
> Have you tried with 1.0-beta-2 of wagon-webdav? This solved some
> problems for me.
Added the 1.0-beta-2 of wagon-webdav like this:
org.apache.maven.wagon
wagon-webdav
1.0-beta-2
...
On Tue, January 30, 2007 1:55 pm, Aaron Digulla wrote:
> Have you tried with 1.0-beta-2 of wagon-webdav? This solved some
> problems for me.
Dumb question... how do you override the dependency of a plugin?
Regards,
Graham
--
On Tue, January 30, 2007 1:55 pm, Aaron Digulla wrote:
> Have you tried with 1.0-beta-2 of wagon-webdav? This solved some
> problems for me.
Not yet - I am trying to do this without a pom file (the artifacts are
ultimately matlab generated). Seems creating a pom is the way to go. Will
try it and
Quoting Graham Leggett <[EMAIL PROTECTED]>:
It looks like the plugin is not making an attempt to create the
directories in the repository before trying to upload the file to the
repository, thus the failure:
Have you tried with 1.0-beta-2 of wagon-webdav? This solved some
problems for me.
Hi all,
As a test I have configured the deploy:deploy-file goal to deploy to a
WebDAV server. The login and ssl part works fine, but the attempt to PUT
the file fails with a 403 response code (but not because of auth failure
according to the logs).
It looks like the plugin is not making an attemp
16 matches
Mail list logo
