You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Paul G <ps...@googlemail.com> on 2008/04/16 11:30:25 UTC
application url context change is it possible
Running in stand alone mode is it possible to change the context root of the
Archiva application. Currently it is set to archiva I would like to set it
to repomanager. Any hint's on which config file controls this?
--
View this message in context: http://www.nabble.com/application-url-context-change-is-it-possible-tp16719758p16719758.html
Sent from the archiva-users mailing list archive at Nabble.com.
AW: deploying third party artifacts: "Unsupported Protocol: 'dav'"
Posted by "Lustig, Marc (Allianz Deutschland AG)" <EX...@allianz.de>.
it works now, as assumed the server-id was not mapped correctly.
-----Ursprüngliche Nachricht-----
Von: Lustig, Marc (Allianz Deutschland AG)
Gesendet: Mittwoch, 16. April 2008 14:41
An: archiva-users@maven.apache.org
Betreff: AW: deploying third party artifacts: "Unsupported Protocol: 'dav'"
thanks much, Brett.
the file is being uploaded now, however another error occurs:
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file: ....... Return code is: 401
so it's an authentication issue.
on the local machine (where mvn deploy is called) in settings.xml is configured:
<server>
<id>someid</id>
<username>archiva-user-with-repo-manager-rights</username>
<password>pw</password>
</server>
</servers>
any idea what might cause the 401?
Do I need to map the server-id to something?
M.
-----Ursprüngliche Nachricht-----
Von: Brett Porter [mailto:brett.porter@gmail.com]
Gesendet: Mittwoch, 16. April 2008 13:00
An: archiva-users@maven.apache.org
Betreff: Re: deploying third party artifacts: "Unsupported Protocol: 'dav'"
What version of Maven are you using?
You may also try without "dav:" - just http:// is often fine.
- Brett
On 16/04/2008, Lustig, Marc (Allianz Deutschland AG)
<EX...@allianz.de> wrote:
> We are having trouble to deploy 3rd party-artefacts using mvn
> deploy-plugin.
>
> I followed the instructions located here
> http://maven.apache.org/archiva/guides/getting-started/maven-configurati
> on.html
>
> but the result is
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot
> find wagon which supports the requested protocol: dav
>
> Component descriptor cannot be found in the component repository:
> org.apache.maven.wagon.Wagondav.
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
> artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports
> the requested protocol: dav
>
>
> here is the pom.xml used for upload:
>
> <project>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.example</groupId>
> <artifactId>webdav-deploy</artifactId>
> <packaging>pom</packaging>
> <version>1</version>
> <name>Webdav Deployment POM</name>
>
>
> <build>
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-webdav</artifactId>
> <version>1.0-beta-2</version>
> </extension>
> </extensions>
> </build>
>
> </project>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
AW: deploying third party artifacts: "Unsupported Protocol: 'dav'"
Posted by "Lustig, Marc (Allianz Deutschland AG)" <EX...@allianz.de>.
thanks much, Brett.
the file is being uploaded now, however another error occurs:
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file: ....... Return code is: 401
so it's an authentication issue.
on the local machine (where mvn deploy is called) in settings.xml is configured:
<server>
<id>someid</id>
<username>archiva-user-with-repo-manager-rights</username>
<password>pw</password>
</server>
</servers>
any idea what might cause the 401?
Do I need to map the server-id to something?
M.
-----Ursprüngliche Nachricht-----
Von: Brett Porter [mailto:brett.porter@gmail.com]
Gesendet: Mittwoch, 16. April 2008 13:00
An: archiva-users@maven.apache.org
Betreff: Re: deploying third party artifacts: "Unsupported Protocol: 'dav'"
What version of Maven are you using?
You may also try without "dav:" - just http:// is often fine.
- Brett
On 16/04/2008, Lustig, Marc (Allianz Deutschland AG)
<EX...@allianz.de> wrote:
> We are having trouble to deploy 3rd party-artefacts using mvn
> deploy-plugin.
>
> I followed the instructions located here
> http://maven.apache.org/archiva/guides/getting-started/maven-configurati
> on.html
>
> but the result is
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot
> find wagon which supports the requested protocol: dav
>
> Component descriptor cannot be found in the component repository:
> org.apache.maven.wagon.Wagondav.
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
> artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports
> the requested protocol: dav
>
>
> here is the pom.xml used for upload:
>
> <project>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.example</groupId>
> <artifactId>webdav-deploy</artifactId>
> <packaging>pom</packaging>
> <version>1</version>
> <name>Webdav Deployment POM</name>
>
>
> <build>
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-webdav</artifactId>
> <version>1.0-beta-2</version>
> </extension>
> </extensions>
> </build>
>
> </project>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: deploying third party artifacts: "Unsupported Protocol: 'dav'"
Posted by Brett Porter <br...@gmail.com>.
What version of Maven are you using?
You may also try without "dav:" - just http:// is often fine.
- Brett
On 16/04/2008, Lustig, Marc (Allianz Deutschland AG)
<EX...@allianz.de> wrote:
> We are having trouble to deploy 3rd party-artefacts using mvn
> deploy-plugin.
>
> I followed the instructions located here
> http://maven.apache.org/archiva/guides/getting-started/maven-configurati
> on.html
>
> but the result is
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot
> find wagon which supports the requested protocol: dav
>
> Component descriptor cannot be found in the component repository:
> org.apache.maven.wagon.Wagondav.
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
> artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports
> the requested protocol: dav
>
>
> here is the pom.xml used for upload:
>
> <project>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.example</groupId>
> <artifactId>webdav-deploy</artifactId>
> <packaging>pom</packaging>
> <version>1</version>
> <name>Webdav Deployment POM</name>
>
>
> <build>
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-webdav</artifactId>
> <version>1.0-beta-2</version>
> </extension>
> </extensions>
> </build>
>
> </project>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
deploying third party artifacts: "Unsupported Protocol: 'dav'"
Posted by "Lustig, Marc (Allianz Deutschland AG)" <EX...@allianz.de>.
We are having trouble to deploy 3rd party-artefacts using mvn
deploy-plugin.
I followed the instructions located here
http://maven.apache.org/archiva/guides/getting-started/maven-configurati
on.html
but the result is
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot
find wagon which supports the requested protocol: dav
Component descriptor cannot be found in the component repository:
org.apache.maven.wagon.Wagondav.
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports
the requested protocol: dav
here is the pom.xml used for upload:
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.example</groupId>
<artifactId>webdav-deploy</artifactId>
<packaging>pom</packaging>
<version>1</version>
<name>Webdav Deployment POM</name>
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-2</version>
</extension>
</extensions>
</build>
</project>
Re: application url context change is it possible
Posted by Paul G <ps...@googlemail.com>.
Cheers Brett
That worked a treat
Brett Porter wrote:
>
> It should be apps/archiva/conf/application.xml, change <context/>
>
> On 16/04/2008, Paul G <ps...@googlemail.com> wrote:
>>
>> Running in stand alone mode is it possible to change the context root of
>> the
>> Archiva application. Currently it is set to archiva I would like to set
>> it
>> to repomanager. Any hint's on which config file controls this?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/application-url-context-change-is-it-possible-tp16719758p16719758.html
>> Sent from the archiva-users mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
>
--
View this message in context: http://www.nabble.com/application-url-context-change-is-it-possible-tp16719758p16720679.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: application url context change is it possible
Posted by Sergey Nikitin <ni...@gmail.com>.
Probably directory layout was changed, in version 1.2.1 there is no "conf"
under "apps/archiva".
File with name "application.xml" is located under
"apps/archiva/WEB-INF/classes/META-INF/plexus/" and there is no element
"context".
For now i've just renamed directory from "apps/archiva" to "apps/newName".
That works fine, but maybe it is better to modify configuration file? Im not
an expert with these things.
Thanks in advance
Brett Porter wrote:
>
> It should be apps/archiva/conf/application.xml, change <context/>
>
> On 16/04/2008, Paul G <ps...@googlemail.com> wrote:
>>
>> Running in stand alone mode is it possible to change the context root of
>> the
>> Archiva application. Currently it is set to archiva I would like to set
>> it
>> to repomanager. Any hint's on which config file controls this?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/application-url-context-change-is-it-possible-tp16719758p16719758.html
>> Sent from the archiva-users mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
>
--
View this message in context: http://www.nabble.com/application-url-context-change-is-it-possible-tp16719758p24373192.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: application url context change is it possible
Posted by Brett Porter <br...@gmail.com>.
It should be apps/archiva/conf/application.xml, change <context/>
On 16/04/2008, Paul G <ps...@googlemail.com> wrote:
>
> Running in stand alone mode is it possible to change the context root of the
> Archiva application. Currently it is set to archiva I would like to set it
> to repomanager. Any hint's on which config file controls this?
>
> --
> View this message in context: http://www.nabble.com/application-url-context-change-is-it-possible-tp16719758p16719758.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/