|
From: dhoffer <DH...@xr...> - 2007-05-02 11:18:55
|
I can't speak to how it fixes it as I don't know the internals of webdav
and/or artifactory. However it seemed to me that webdav might be a better
choice as we needed it anyway for site publishing, once there for that I
tried it to publish to artifactory as well and it worked. Here is the pom
contents to use it:
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-2</version>
</extension>
</extensions>
</build>
<distributionManagement>
<repository>
<id>releases</id>
<name>Inhouse Internal Release Repository</name>
<url>dav:http://xrbuild3:8081/artifactory/libs-releases@repo</url>
</repository>
<snapshotRepository>
<id>snapshots</id>
<name>Inhouse Internal Snapshot Repository</name>
<url>dav:http://xrbuild3:8082/artifactory/libs-snapshots@repo</url>
<uniqueVersion>true</uniqueVersion>
</snapshotRepository>
<site>
<id>website</id>
<url>dav:http://xrbuild3/site/${artifactId}/${project.version}</url>
</site>
</distributionManagement>
zalym wrote:
>
> H,
>
> I am having the same issue. How does webdav solve this? I am very new to
> Maven and Artifactory. Any help would be appreciated.
>
> Regards,
> Saleem
>
>
--
View this message in context: http://www.nabble.com/500-Error-tf3652969.html#a10284063
Sent from the Artifactory-Users mailing list archive at Nabble.com.
|