Re: application url context change is it possible
It should be apps/archiva/conf/application.xml, change context/ On 16/04/2008, Paul G [EMAIL PROTECTED] 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/
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 idsomeid/id usernamearchiva-user-with-repo-manager-rights/username passwordpw/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:[EMAIL PROTECTED] 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) [EMAIL PROTECTED] 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 modelVersion4.0.0/modelVersion groupIdcom.example/groupId artifactIdwebdav-deploy/artifactId packagingpom/packaging version1/version nameWebdav Deployment POM/name build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project -- Brett Porter Blog: http://blogs.exist.com/bporter/
including artifacts
Hi, I don't know if I understood well how it works. If I wanna purchase a new artifact as a normal user and I don't have access to the links for remote repositories, then how can I get ant (example) if I don't know the path and version so it could be added to my archiva repository? There is an easy way to do it? PS: not talking about deploy. Regards, Renato
Re: Error uploading artifact (MRM-753)
Brett proposed to try if the change in wagon for archiva 1.1 will change this. I'll try to free some hours to test it, because it is a very very anoying bug. The repository doesn't have all data and our CI server fails without a real reason. Arnaud On Wed, Apr 16, 2008 at 10:55 AM, Benoit Decherf [EMAIL PROTECTED] wrote: Hi, We are blocked by this issue. This is blocker because if it fails while uploading a jar file, then the pom is already in the repo and the metadata.xml is already updated. It makes the others components that depend on it to fails. Is there any workaround ? The stacktrace shows that it come from the security module (redback). Is it possible to desactivate it ? Benoit -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
