There are a few issues with the wagon-scm provider as it was only prototyped earlier in the year and there hasn't been a lot of interest since.
The URL needs to be like a Maven connection: scm:svn:svn://... IF you have any issues and are willing to help, join wagon-dev@maven.apache.org ([EMAIL PROTECTED]) and we can discuss it there. Cheers, Brett On 11/18/05, Darren Hartford <[EMAIL PROTECTED]> wrote: > Hey all, > Has anyone used the wagon-scm provider for use with the antlib > artifact:deploy task? > > We keep a separate repository of jar's in Subversion (for versioning > control and security of those jars/poms) and would like to automate this > task with the build.xml file using the maven2 antlibs. > =========================== > <!-- pom setup previously--> > <target name="jar:install"> > <artifact:install-provider artifactId="wagon-scm" > version="1.0-alpha-3"/> > > <artifact:deploy file="target/mydist.jar"> > <artifact:remoteRepository > url="svn://mylocalserver/svnroot/repository/"> > </artifact:remoteRepository> > <pom refid="pom"/> > </artifact:deploy> > </target> > =========================== > > Any pointers would be welcome, thanks! > > -D > > --------------------------------------------------------------------- > 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]
