Wendy,

I have the same issue, and I followed your suggestion of matching up the
id's, but I still get the 401 error.

settings.xml:

   <server>
      <id>dev.repo</id>
      <username>xxxxx</username>
      <password>xxxxx</password>
   </server>

pom.xml:

        <distributionManagement>
                <repository>
                        <id>dev.repo</id>
                        <name>Internal Release Repository</name>
                        
<url>dav:http://ng00003570:8080/archiva/repository/internal/</url>
                </repository>
                <snapshotRepository>
                        <id>dev.repo</id>
                        <name>Internal Snapshot Repository</name>
                        
<url>dav:http://ng00003570:8080/archiva/repository/snapshots/</url>
                </snapshotRepository>
        </distributionManagement>

        <build>
                <plugins>
                        <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-surefire-plugin</artifactId>
                                <configuration>
                                        <skip>true</skip>
                                </configuration>
                        </plugin>
                </plugins>
      <extensions>
        <extension>
          <groupId>org.apache.maven.wagon</groupId>
          <artifactId>wagon-webdav</artifactId>
          <version>1.0-beta-2</version>
        </extension>
      </extensions>
        </build>

Is there anything else missing?

Thanks,
Chris


Wendy Smoak-3 wrote:
> 
> On Jan 14, 2008 11:27 AM, Mick Knutson <[EMAIL PROTECTED]> wrote:
> 
>> I can deploy my site docs to my remote server just fine, but when I try
>> to
>> deploy a module to my archiva REP, I get a 401 error.
> 
> Please choose *one* list and ask your question there.  Someone will
> tell you if you're in the wrong place.  Many of the people who can
> help are already reading both lists, and cross-posting just causes
> duplicate traffic, as well as splitting a conversation so it's hard to
> follow in the archives.
> 
> In this case it doesn't look like a problem with Archiva, just a
> problem with configuration, so I'm replying on [EMAIL PROTECTED] You have:
> 
>> *pom.xml:*
>>
>>         <!-- use the following if you're not using a snapshot version.
>> -->
>>         <repository>
>>             <id>dap.internal</id>
> ...
>>         <snapshotRepository>
>>             <id>dap.snapshots</id>
>>     </distributionManagement>
> 
> and
> 
>> *settings.xml:*
> ...
>>             <id>rc_sun66e-site</id>
>>             <id>rc_sun66e-repository</id>
>>             <id>dap2.internal</id>
>>             <id>deployment.webdav</id>
>>             <id>deployment.webdav</id>
> 
> In order for Maven to figure out what credentials to send to the
> server, the ids need to match in the pom.xml distributionManagement
> section, and settings.xml servers section.
> 
> You're probably getting the 401 because Maven isn't supplying any
> credentials.
> 
> -- 
> Wendy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-m2--archiva1--Issue-deploying-to-Archiva-tp14808246s177p15072410.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to