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>
                <id>internal</id>
                <name>Inhouse Internal Release Repository</name>
                <url>ftp://XRBUILD2/internal</url>
        </repository>
        <snapshotRepository>
                <id>internal_snapshot</id>
                <name>Inhouse Internal Snapshot Repository</name>
                <url>ftp://XRBUILD2/internal_snapshot</url>
                <uniqueVersion>true</uniqueVersion>
        </snapshotRepository>
  </distributionManagement>
  <repositories>
    <repository>
      <id>inhouse</id>
          <url>http://XRBUILD2:81/proximity/repository/inhouse</url>
    </repository>
    <repository>
          <id>public</id>
          <url>http://XRBUILD2:81/proximity/repository/public</url>
    </repository>
  </repositories>
  <pluginRepositories>
    <pluginRepository>
      <id>inhouse</id>
      <url>http://XRBUILD2:81/proximity/repository/inhouse</url>
    </pluginRepository>
    <pluginRepository>
      <id>public</id>
      <url>http://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:
>
> <url>dav: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>
>                 <groupId>org.apache.maven.wagon</groupId>
>                 <artifactId>wagon-webdav</artifactId>
>                 <version>1.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]

Reply via email to