On Tuesday, February 27, 2018 2:53 PM, anders.g.ham...@gmail.com
[mailto:anders.g.ham...@gmail.com] On Behalf wrote:
> The problem is that you have specified the configuration for a specific
> execution. An execution bound to the deploy phase.
> If you want to execute from command line by
usly wrong with my pom and I cannot
> figure out what...
>
> /Lars
>
> > On 27 February 2018 at 21:52, Svensson, Lars <l.svens...@dnb.de> wrote:
> >
> > > On Tuesday, February 27, 2018 12:34 PM, Olivier Lamy [mailto:
> > > ol...@apache.org] wrote:
&g
February 2018 at 21:29, Svensson, Lars <l.svens...@dnb.de> wrote:
> > >
> > > > Hi Olivier and thanks for your quick reply!
> > > >
> > > > On Tuesday, February 27, 2018 11:54 AM, Olivier Lamy [mailto:
> > > > ol...@apache.org]
l.svens...@dnb.de> wrote:
> >
> > > Hi Olivier and thanks for your quick reply!
> > >
> > > On Tuesday, February 27, 2018 11:54 AM, Olivier Lamy [mailto:
> > > ol...@apache.org] wrote:
> > >
> > > > webdav is not a plugin but a protocol
, Olivier Lamy [mailto:
> > ol...@apache.org] wrote:
> >
> > > webdav is not a plugin but a protocol supported by wagon
> > > you're right using extension tag
> > > If you want to deploy your artifacts just configure
> > distributionManagement
> > > to us
On 27 February 2018 at 21:29, Svensson, Lars <l.svens...@dnb.de> wrote:
> Hi Olivier and thanks for your quick reply!
>
> On Tuesday, February 27, 2018 11:54 AM, Olivier Lamy [mailto:
> ol...@apache.org] wrote:
>
> > webdav is not a plugin but a protocol supported by w
Hi Olivier and thanks for your quick reply!
On Tuesday, February 27, 2018 11:54 AM, Olivier Lamy [mailto:ol...@apache.org]
wrote:
> webdav is not a plugin but a protocol supported by wagon
> you're right using extension tag
> If you want to deploy your artifacts just
Hi,
webdav is not a plugin but a protocol supported by wagon
you're right using extension tag
If you want to deploy your artifacts just configure distributionManagement
to use dav protocol: dav:https://thewebdavurl/
Otherwise have a look at this plugin:
http://www.mojohaus.org/wagon-maven-plugin
Greetings,
This is my first post to this list so please bear with me if I'm ignoring
something obvious...
I'm trying to deploy a set of files to a webdav server using Maven Wagon, but
the plugin does not pick up the configuration specified in my POM. If I specify
the URL parameter
kill for what we need and could be
> rather expensive per year.
>
> We already have plenty of hardware so I just want something simple.
>
> We used to use SCP but I don't want to give our CI hosting provider / SAAS
> the ability to auth into our cluster.
>
> WebDAV seems id
com>
wrote:
> +1 on not trying to use some other solution. Some people I know were
> trying to use WebDAV and the WebDAV wagon to work around some network
> limitation that they had and it was extremely painful and the WebDAV wagon
> seems to have not really been tested very we
+1 on not trying to use some other solution. Some people I know were trying to
use WebDAV and the WebDAV wagon to work around some network limitation that
they had and it was extremely painful and the WebDAV wagon seems to have not
really been tested very well.
I stood up an artifactory
On Wed, Nov 4, 2015 at 10:36 PM, Anders Hammar wrote:
> A real repository manager is not overkill but rather the basic foundation
> in a Maven-based dev environment. And there are free versions of them:
> nexus oss, artifactory and archiva.
> I strongly advice against trying
want something simple.
We used to use SCP but I don't want to give our CI hosting provider / SAAS
the ability to auth into our cluster.
WebDAV seems ideal because it could just work with plain old apache.
However, I can't find any documentation for how to set this up.
--
We’re hiring if you
used to use SCP but I don't want to give our CI hosting provider
> / SAAS the ability to auth into our cluster.
>
> WebDAV seems ideal because it could just work with plain old
> apache.
>
> However, I can't find any documentation for how to set this up.
and could be
> rather expensive per year.
>
> We already have plenty of hardware so I just want something simple.
>
> We used to use SCP but I don't want to give our CI hosting provider / SAAS
> the ability to auth into our cluster.
>
> WebDAV seems ideal because it could jus
Hi,
I was bitten by bug OutOfMemory when deploying big files
(http://jira.codehaus.org/browse/WAGON-272) so I decided to switch to dav
protocol. In my pom I have added dav: in front of URL in
distributionManagement section, and also added webdav wagon this way:
build
pluginManagement
This is actually a maven wagon issue:
http://jira.codehaus.org/browse/MNG-4301
Try using the extension specified in that issue, it seems to solve it for me:
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-webdav/artifactId
Hi Siarhei,
Could you please share the information on did you modelled the sharepoint
project using maven? Are you aware of any archetype for sharepoint projects?
Thanks,
Sathish
--
View this message in context:
http://maven.40175.n5.nabble.com/site-deploy-via-webdav-to-a-NTLM-based-location
project using maven? Are you aware of any archetype for sharepoint
projects?
Thanks,
Sathish
--
View this message in context:
http://maven.40175.n5.nabble.com/site-deploy-via-webdav-to-a-NTLM-based-location-tp103370p4895435.html
Sent from the Maven - Users mailing list archive at Nabble.com
This could be an incompatibility with Maven 3. Have you tried with Maven 2.2.1?
On 31/07/2010, at 4:46 AM, Meeusen, Christopher W. wrote:
Hi,
I'm trying to use maven-site-plugin and the wagon-webdav artifact. I
get this error when I do mvn site-deploy. But according to
http
Hi,
I'm trying to use maven-site-plugin and the wagon-webdav artifact. I
get this error when I do mvn site-deploy. But according to
http://maven.apache.org/wagon/wagon-providers/wagon-webdav/ it says it
does support directory copying... anyone know what could produce this
error?
Thanks
I'm not sure if you got this resolved but I'm told this is a server
side rule to prevent the bad checksums from 2.2.0 getting into the
repository. It may need to be reviewed - in any case you should
contact Atlassian about it as Maven is working with other WebDAV hosts..
- Brett
On 15/09
-Original Message-
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Monday, September 14, 2009 12:42 PM
To: users@maven.apache.org
Subject: RE: webdav deployment fails with Access denied message with 2.2.1
(works with 2.0.10)
appears that the pom is absent
did you try downloading
Is there something special I need to do to get WebDAV artifact
deployment working with 2.2.1? When trying to do a deploy, I get the
error below. In looking at the release notes for 2.1.x and 2.2.x,
there's discussion of using different wagons for HTTP (httpclient vs.
lightweight), but my
contenu fourni.
Subject: webdav deployment fails with Access denied message with 2.2.1 (works
with 2.0.10)
Date: Mon, 14 Sep 2009 12:16:10 -0400
From: justin.edel...@mtvstaff.com
To: users@maven.apache.org
Is there something special I need to do to get WebDAV artifact
deployment
contenu fourni.
Subject: RE: webdav deployment fails with Access denied message with 2.2.1
(works with 2.0.10)
Date: Mon, 14 Sep 2009 12:55:51 -0400
From: justin.edel...@mtvstaff.com
To: users@maven.apache.org
The pom is what's trying to be deployed:
Uploading:
https
Martin-
This doesn't make any sense to me. SCP and WebDAV should have nothing to do
with each other. In any case, there is an id in the distributionManagement
section and a corresponding entry in settings.xml. If not, the deploy wouldn't
have worked with 2.0.10.
Oh, an Tortoise is a SVN client
justin.edel...@mtvstaff.com wrote:
Martin-
This doesn't make any sense to me. SCP and WebDAV should have nothing to do
with each other. In any case, there is an id in the distributionManagement
section and a corresponding entry in settings.xml. If not, the deploy
wouldn't have worked
No.. tortoise supports svn+ssh:
No.. anyone implementing webdav can secure their webdav site with ssl
http://www.howtoforge.com/webdav_with_ssl_and_two_factor_authentication
scp is secure copy or copy implementing SSH
http://www.computerhope.com/unix/scp.htm
my advice is to contact
[mailto:kalle.o.korho...@gmail.com]
Sent: Monday, September 14, 2009 2:14 PM
To: Maven Users List
Subject: Re: webdav deployment fails with Access denied message with 2.2.1
(works with 2.0.10)
Not clear to me if you are using that dav: try it if you aren't. I had a
similar issue - but not sure
Hi Michael,
I switched to use scp and all is good :-)
Sorry I can not help you with the webdav thing,
- Ross
Michael K. wrote:
Hello Ross,
I have the same problem as you had. Did you get resolve the problem?
I would appreciate your help.
Kind regards,
Michael
rossputin
I already use Maven 2.1.0.
The error.log contains:
Digest: client used wrong authentication scheme `Basic':
Cannot create collection; intermediate collection does not exist. [409, #0]
How do I get maven to use wagon-webdav-jackrabbit 1.0-
beta-5 ?
Thanks for help,
Michael
brettporter
Hello Ross,
I have the same problem as you had. Did you get resolve the problem?
I would appreciate your help.
Kind regards,
Michael
rossputin wrote:
Hi,
I am using maven 2.0.9, and everything is working great except for site
deployment with webdav. I have not tried any other kind
contenu fourni.
Date: Tue, 5 May 2009 05:16:31 -0700
From: mail4s...@arcor.de
To: users@maven.apache.org
Subject: Re: unable to deploy site with webdav
Hello Ross,
I have the same problem as you had. Did you get resolve the problem?
I would appreciate your help.
Kind regards
Hello Martin,
I try to upload to the apache-webserver 2.2. I've configured webdav as
described in the httpd.conf and the httpd-dav.conf. I tested it via windows
web folder and it works fine.
Michael
mgainty wrote:
Ross-
which container are you attempting to upload to ?
Martin
500 errors will show up in the Apache error log which might help you
nail down the problem.
You might also try Maven 2.1.0 and the wagon-webdav-jackrabbit 1.0-
beta-5 wagon as an alternative if you are still having problems.
Cheers,
Brett
On 06/05/2009, at 12:00 AM, Michael K. wrote
: Failed to create destination WebDAV collection
(directory): /lpr-project/./css
SSL peer shut down incorrectly
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
site
]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug
]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https
]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org
] Error handling resource
Embedded error: Destination path exists but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon
but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon webdav?
-D
On Fri, Oct 10, 2008 at 7:56 PM, Brett Porter
]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
path exists but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon webdav?
-D
On Fri, Oct 10, 2008 at 7:56 PM
]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full
]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
ERROR
[INFO]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
but is not a WebDAV
collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon webdav?
-D
On Fri, Oct 10, 2008 at 7:56 PM, Brett Porter
[EMAIL PROTECTED
handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon webdav?
-D
]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so
] BUILD ERROR
[INFO]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper
Hello,
I am currently continue on with James Dumay's wagon-maven-plugin at
MOJO's sanbox and running to issue invokes' Wagon:getFilelist() with
wagon-webdav-jackrabbit
The IT pom is at
http://svn.codehaus.org/mojo/trunk/sandbox/wagon-maven-plugin/src/it/webdav
The error
2008/10/11 Dan Tran [EMAIL PROTECTED]:
Hello,
I am currently continue on with James Dumay's wagon-maven-plugin at
MOJO's sanbox and running to issue invokes' Wagon:getFilelist() with
wagon-webdav-jackrabbit
The IT pom is at
http://svn.codehaus.org/mojo/trunk/sandbox/wagon-maven-plugin/src
and running to issue invokes' Wagon:getFilelist() with
wagon-webdav-jackrabbit
The IT pom is at
http://svn.codehaus.org/mojo/trunk/sandbox/wagon-maven-plugin/src/it/webdav
Maybe this is a classpath ordering problem - to apply a patch from
Jackrabbit's JIRA we included a couple of Jackrabbit
sanbox and running to issue invokes' Wagon:getFilelist() with
wagon-webdav-jackrabbit
The IT pom is at
http://svn.codehaus.org/mojo/trunk/sandbox/wagon-maven-plugin/src/it/webdav
Maybe this is a classpath ordering problem - to apply a patch from
Jackrabbit's JIRA we included a couple
, Brett Porter [EMAIL PROTECTED] wrote:
2008/10/11 Dan Tran [EMAIL PROTECTED]:
Hello,
I am currently continue on with James Dumay's wagon-maven-plugin at
MOJO's sanbox and running to issue invokes' Wagon:getFilelist() with
wagon-webdav-jackrabbit
The IT pom is at
http://svn.codehaus.org/mojo
]:
Hello,
I am currently continue on with James Dumay's wagon-maven-plugin at
MOJO's sanbox and running to issue invokes' Wagon:getFilelist() with
wagon-webdav-jackrabbit
The IT pom is at
http://svn.codehaus.org/mojo/trunk/sandbox/wagon-maven-plugin/src/it/webdav
Maybe this is a classpath
handling resource
Embedded error: Destination path exists but is not a WebDAV collection (director
y): https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon webdav?
-D
]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus
resource
Embedded error: Destination path exists but is not a WebDAV collection (director
y): https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon webdav?
-D
On Fri
]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https
handling resource
Embedded error: Destination path exists but is not a WebDAV collection
(director
y):
https://dav.codehaus.org/snapshots.repository/mojo/org/codehaus/mojo/build-h
elper-maven-plugin/1.2-SNAPSHOT
so it seems we cannot use full path to dav's URL
is this a bug in wagon webdav
Hi,
I have since successfully deployed the site with scp, so the problem is
definitely with webdav, or my configuration of it.
My parent pom.xml contains a 'distributionManagement' element as below:
distributionManagement
site
idourproject.website/id
urldav:http://our.webserver.com/projects
The Mojo project at Codehaus uses webdav for site deployment. Perhaps
you can pick up a clue or two by looking at their parent POM:
http://svn.codehaus.org/mojo/tags/mojo-17/pom.xml
The users of that parent doesn't have to configure anything related to
site deployment.
The configuration
Hi,
I am using maven 2.0.9, and everything is working great except for site
deployment with webdav. I have not tried any other kind of deployment yet,
as I do it manually, so it may not be just site deployment that is not
working for me. I have an apache webdav setup in place, and can access
On Fri, May 16, 2008 at 7:53 AM, rossputin [EMAIL PROTECTED] wrote:
Has anyone successfully deployed with any recent version of maven over
webdav? One of the books I have on it suggests using it. I have not seen
much on the mailing list though.
Yes, it works for me with wagon-webdav
Hi All,
I am trying to deploy a site to MS Sharepoint which is *not* behind a proxy
via webdav (Sharepoint supports webdav protocol).
For that I have defined site in my pom (it worked well for deployment to IIS
via webdav which didnt use NTLM auithentication):
distributionManagement
It's not possible to use webdav by default.
There's some useful information on how to enable it in this link:
http://docs.codehaus.org/display/MAVENUSER/Deploying+3rd+Party+Jars+With
+WebDAV
-Original Message-
From: Savita_p_m [mailto:[EMAIL PROTECTED]
Sent: 13 February 2008 06:54
Hi,
Thanks for the pointer...
However my issues was related to hudson configuration as it was working fine
with command line.
Hudson job configuration using Build a maven2 project (beta) doesn't work
with webdav where as same thing worked for me when I configured the job
using Build a free
@maven.apache.org
Subject: Re: not able to deploy using webdav
Hi,
Thanks for the pointer...
However my issues was related to hudson configuration as it was working
fine
with command line.
Hudson job configuration using Build a maven2 project (beta) doesn't
work
with webdav where as same thing worked
is rock solid and the
only thing I use.
-Original Message-
From: Savita_p_m [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 12:22 PM
To: users@maven.apache.org
Subject: Re: not able to deploy using webdav
Hi,
Thanks for the pointer...
However my issues was related
Hi,
I am getting following error while trying for site-deploy, I have
configured job using hudson to run maven goals. Build extensions are
mentioned in pom.xml and the repository has the wagon-webdav jars.
However from command line it works properly where as it fails with the
following error
Add the wagon to your pom inside the extensions tag.
-Original Message-
From: Savita_p_m [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 10:54 PM
To: users@maven.apache.org
Subject: not able to deploy using webdav
Hi,
I am getting following error while trying for site
Hi,
Is it still necessary to add 'wedav' as a protocol to the url of
distributionManagement in the pom.xml. When i remove it things work fine, so i
assumed the http wagon implementation has been improved.
What i'm also curious about is the number of repositories between the
Hi,
I have been trying to get WAGON-WEBDAV working with an Apache WebDAV
provider and can only see
that BASIC authentication is attempted. Am I missing something in the
following configuration sections:
pom.xml
extensions
extension
groupIdorg.apache.maven.wagon/groupId
requests.
D.
On 11/1/07, Heinrich Nirschl [EMAIL PROTECTED] wrote:
This is a problem with the default Windows TCP/IP configuration. The
client runs out of available ports during the many webdav transfers.
The solution is described here:
http://msdn2.microsoft.com/en-us/library/aa560610.aspx
to create destination WebDAV collection (directory): /pro
jects/web-app-parent/csa/./apidocs/com/csatravelprotection/rules/class-use
Address already in use: connect
[INFO]
[DEBUG] Trace
to create destination WebDAV collection (directory):
/pro
jects/web-app-parent/csa/./apidocs/com/csatravelprotection/rules/class-use
Address already in use: connect
This is a problem with the default Windows TCP/IP configuration. The
client runs out of available ports during the many webdav
which
fails on the server with an obvious message.
--
View this message in context:
http://www.nabble.com/WebDav%2C-Wagon-and-Digest-Authentication-tf4653580s177.html#a13295600
Sent from the Maven - Users mailing list archive at Nabble.com
I'm doing a lot of first time setup with Geronmio hosting Proximity,
and using WebDAV to deploy a jar.
I'm stuck at a point where 'mvn deploy' reports
[INFO] Error deploying artifact: Failed to transfer file:
http://...snipjar Return code is: 500 Internal Server Error
When I look
and this type of request works well with
archiva-1.0-beta-1.
Is there any modification that may explain this error?
Regards.
--
View this message in context:
http://www.nabble.com/Webdav-error-tf4473901.html#a12755763
Sent from the archiva-users mailing list archive at Nabble.com.
-webdav do not ask for the creation of the directories before uploading
the artifact as we can see in the following logs :
[Thu Sep 06 10:36:27 2007] [error] [client 10.194.3.100] Unable to PUT
new contents for
/inhouse.snapshot/com/test/my-plugin/1.0-SNAPSHOT/my-
plugin-1.0-20070906.083623-1.jar
running maven
trusts
the certificate
Not for the moment.
We continue some tests this morning and it seems effectively that
wagon-webdav do not ask for the creation of the directories before uploading
the artifact as we can see in the following logs :
[Thu Sep 06 10:36:27 2007] [error
.
To make the thinks worse webdav://... also does not work for me in
release plugin.
Thank you,
Piotr Tabor
Carlos Sanchez pisze:
check the permissions because wagon definitely creates the dirs
On 9/6/07, Rémy Sanlaville [EMAIL PROTECTED] wrote:
Hi Michael,
Sorry for my late reply, but I am
you need to use dav as wagon protocol, not http or webdav
something like
dav:https://dav.codehaus.org/snapshots.repository/mojo/
check the mojo pom for an example
http://repo1.maven.org/maven2/org/codehaus/mojo/mojo/16/mojo-16.pom
On 9/6/07, Piotr Tabor [EMAIL PROTECTED] wrote:
Wagon creates
2007/9/6, Carlos Sanchez [EMAIL PROTECTED]:
you need to use dav as wagon protocol, not http or webdav
something like
dav:https://dav.codehaus.org/snapshots.repository/mojo/
My problem was here !
I used http://myhost/inhouse rather than dav:http://myhost/inhouse
Now it works like a charm
As I mentioned in my first post, I followed the instructions from this
article
(http://docs.codehaus.org/display/MAVENUSER/Deploying+3rd+Party+Jars+With+WebDAV
)
So it is not correct because it uses a bad url:
-Durl=http://localhost:8080/archiva/repository/myrepo
It would be nice to update
September 2007 03:59, Rémy Sanlaville wrote:
Thanks Carlos and Michael for your reply.
I try to find what's wrong with apache. I will tell you if I find something
wrong.
Did you have a specific configuration of apache for the WebDav protocol ?
Rémy
--
Michael McCallum
Enterprise Engineer
I have a deployment problem with maven 2 and WebDav protocol.
My context :
---
I have corporate repositories (inhouse and inhouse.snapshot) with Proximity
proxy.
As Proximity seems to not support efficiently WebDav protocol, I also have a
apache frontal allowing access to my
wagon-webdav does create directories and it's being widely used, i
even use it with svn
I'd look for something specific to your configuration that may not be
the typical configuration or an error in your server setup
On 8/31/07, Rémy Sanlaville [EMAIL PROTECTED] wrote:
I have a deployment
i have webdav working without problems... using digest authentication
i might have a had a few issues but nothing that was not resolved by watching
the apache logs...
much faster than ssh/sftp IMO
On Friday 31 August 2007 21:50, Rémy Sanlaville wrote:
I have a deployment problem with maven 2
Thanks Carlos and Michael for your reply.
I try to find what's wrong with apache. I will tell you if I find something
wrong.
Did you have a specific configuration of apache for the WebDav protocol ?
Rémy
Here is an Ant build.xml snippet using maven tasks:
artifact:remoteRepository id=my.repo
url=dav:http://fred:[EMAIL PROTECTED] layout=default/
artifact:install-provider artifactId=wagon-webdav
version=1.0-beta-2/
artifact:deploy file=my.jar
remoteRepository refid=my.repo
Le jeudi 30 août 2007, Craig Ryan a écrit :
Here is an Ant build.xml snippet using maven tasks:
artifact:remoteRepository id=my.repo
url=dav:http://fred:[EMAIL PROTECTED] layout=default/
artifact:install-provider artifactId=wagon-webdav
version=1.0-beta-2/
artifact:deploy file
On 8/22/07, Pascal Thivent [EMAIL PROTECTED] wrote:
Hi,
I've used the following url successfully(*) :
urldav:http://host:port/pxweb/dav/inhouse.snapshot/url
I guess it should work in the same way with extNonFree.
Unfortunately not. The inhouse.snapshot is understood by proximity
as the
to upload (deploy, release).
[configuration example deleted]
Thanks for the configuration example. Upload to proximity via WebDAV
works in principle, I can successfully upload to the other
repositories (inhouse, inhouse.snapshot, extFree). It's just the
extNonFree that doesn't work.
I hoped, somebody
Hi,
in the out-of-the-box setup of proximity with the repositories
extFree, extNonFree, and central in the public group I would like to
deploy to extNonFree via WebDAV.
I tried the URLs:
http://myserver:8080/proximity/dav/extNonFree - this results in a 500
response from the server, the server
It's been awhile since I have used proximity but I thought you would use
the following syntax:
urldav:http://xr-grr-build:8081/artifactory/[EMAIL PROTECTED]/url
Of course you have to enable webdav in your pom's build section.
extensions
extension
null not found!
Of course you have to enable webdav in your pom's build section.
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-webdav/artifactId
version1.0-beta-2/version
/extension
1 - 100 of 167 matches
Mail list logo