Configure distributionManagement in your pom.xml file

For example

	<distributionManagement>
		<!-- use the following if you're not using a snapshot version. -->
		<repository>
			<id>raisercostin.googlecode.releases</id>
			<name>raisercostin.googlecode.releases</name>
			<url>dav:https://raisercostin.googlecode.com/svn/maven2/</url>
		</repository>
		<!-- use the following if you ARE using a snapshot version. -->
		<snapshotRepository>
			<id>raisercostin.googlecode.snapshots</id>
			<name>raisercostin.googlecode.snapshots</name>
			<url>dav:https://raisercostin.googlecode.com/svn/maven2-snapshots/</url>
		</snapshotRepository>
     </distributionManagement>

Add credentials in your settings.xml file (USER_HOME/.m2/settings.xml - the recomended place or in MAVEN_HOME/conf/settings.xml)

    <servers>
        <server>
            <id>raisercostin.googlecode.releases</id>
            <username>raisercostin</username>
            <password>*******</password>
        </server>
        <server>
            <id>raisercostin.googlecode.snapshots</id>
            <username>raisercostin</username>
            <password>*******</password>
        </server>
    </servers>

Comment by nicolas.delsaux, Jan 4, 2009

Well ... I've tried this procedure, but it fails when doing a mvn deploy with the following error message :

[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.mav
en.wagon.Wagondav.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------

Well ... a little googling solved (in theory) my issue : http://agileshrugged.com/blog/?p=34 : a simple update to maven 2.0.9 is enough

► Sign in to add a comment