Re: deploying to proximity via webdav
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 repository group name (which happens to be the same as the repository in this case). In the case of extNonFree the group name is public and when one uses this, the artifact ends up in extFree (which is also a member of the public group). (*) by successfully, I mean that the deployement with wagon worked, it just took *ages* (5mn to deploy an almost empty artefact vs 13s with apache + mod_dav). See https://trac.abstracthorizon.org/proximity/ticket/114 I don't see such a slowdown here. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploying to proximity via webdav
On 8/23/07, Dave Hoffer [EMAIL PROTECTED] wrote: If I recall correctly proximity did not support uploading artifacts only downloading them. This may have changed since we used it however. I think this was one of the reasons we switched to Artifactory. With proximity we were using ftp 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 knows the trick how to do it or can confirm that it doesn't work in the current version. Unfortunately the source is not available at the moment, otherwise I would have had a look there. If I don't get it to work I have to switch to other upload methods (ftp or scp). - Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
deploying to proximity via webdav
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 log shows an exception that the groupId is null, and http://myserver:8080/proximity/dav/public/extNonFree - this works, but deploys to extFree, the first repository in the public group (with an extra extNonFree directory). What's the right URL to deploy to extNonFree? Is there some more configuration necessary? TIA - Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploying to proximity via webdav
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 groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions -Dave -Original Message- From: Heinrich Nirschl [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2007 2:39 AM To: Maven Users List Subject: deploying to proximity via webdav 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 log shows an exception that the groupId is null, and http://myserver:8080/proximity/dav/public/extNonFree - this works, but deploys to extFree, the first repository in the public group (with an extra extNonFree directory). What's the right URL to deploy to extNonFree? Is there some more configuration necessary? TIA - Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploying to proximity via webdav
Thanks for your answer, Dave! On 8/22/07, Dave Hoffer [EMAIL PROTECTED] wrote: 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 Unfortunately, this URL does not work with proximity either. I tried .../[EMAIL PROTECTED] and .../[EMAIL PROTECTED] Both resulted in the 500 reply from the server. The exact exception on the server is (I was not in front of the machine when I wrote my first mail): org.abstracthorizon.proximity.NoSuchRepositoryException: Repository with name group 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 /extensions Yes, I have that. -Dave -Original Message- From: Heinrich Nirschl [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2007 2:39 AM To: Maven Users List Subject: deploying to proximity via webdav 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 log shows an exception that the groupId is null, and http://myserver:8080/proximity/dav/public/extNonFree - this works, but deploys to extFree, the first repository in the public group (with an extra extNonFree directory). What's the right URL to deploy to extNonFree? Is there some more configuration necessary? TIA - Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploying to proximity via webdav
If I recall correctly proximity did not support uploading artifacts only downloading them. This may have changed since we used it however. I think this was one of the reasons we switched to Artifactory. With proximity we were using ftp to upload (deploy, release). Here is one of our old poms. distributionManagement repository idinternal/id nameInhouse Internal Release Repository/name urlftp://XRBUILD2/internal/url /repository snapshotRepository idinternal_snapshot/id nameInhouse Internal Snapshot Repository/name urlftp://XRBUILD2/internal_snapshot/url uniqueVersiontrue/uniqueVersion /snapshotRepository /distributionManagement repositories repository idinhouse/id urlhttp://XRBUILD2:81/proximity/repository/inhouse/url /repository repository idpublic/id urlhttp://XRBUILD2:81/proximity/repository/public/url /repository /repositories pluginRepositories pluginRepository idinhouse/id urlhttp://XRBUILD2:81/proximity/repository/inhouse/url /pluginRepository pluginRepository idpublic/id urlhttp://XRBUILD2:81/proximity/repository/public/url /pluginRepository /pluginRepositories -Dave -Original Message- From: Heinrich Nirschl [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2007 10:25 AM To: Maven Users List Subject: Re: deploying to proximity via webdav Thanks for your answer, Dave! On 8/22/07, Dave Hoffer [EMAIL PROTECTED] wrote: 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 Unfortunately, this URL does not work with proximity either. I tried .../[EMAIL PROTECTED] and .../[EMAIL PROTECTED] Both resulted in the 500 reply from the server. The exact exception on the server is (I was not in front of the machine when I wrote my first mail): org.abstracthorizon.proximity.NoSuchRepositoryException: Repository with name group 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 /extensions Yes, I have that. -Dave -Original Message- From: Heinrich Nirschl [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2007 2:39 AM To: Maven Users List Subject: deploying to proximity via webdav 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 log shows an exception that the groupId is null, and http://myserver:8080/proximity/dav/public/extNonFree - this works, but deploys to extFree, the first repository in the public group (with an extra extNonFree directory). What's the right URL to deploy to extNonFree? Is there some more configuration necessary? TIA - Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
