|
From: Culnane, D. J. <Dou...@id...> - 2006-11-29 10:21:57
|
Had a play with ziping and unziping jar files to make proper separate jars for Maven dependancies but got into a mess, corrupted my repository and gave up. I have changed tactics and set up a new project that is a Maven 2 build for StatSVN. Using the svn:externals I pull in the source from the StatSVN repository so it is easy up maintain. It all looks like it works and I have clean Maven 2 dependancy management. I can release to my repository with: svn up mvn clean=20 mvn deploy So long as I get the release timing right and maintain the pom.xml this should work well, and be easy to maintain. The main StatSVN project is unaffected by this. I have now upgraded my plugin to use StatSVN 0.2.1-SNAPSHOT. =20 Can not publish (deploy) all work (jars etc site..) yet (firewall..) but it is in SVN. This evening I will scp all jars to my repositories. " <scm> <connection> =09 scm:svn:https://svn.sourceforge.net/svnroot/stat-scm/statsvn/trunk </connection> <developerConnection> =09 scm:svn:https://svn.sourceforge.net/svnroot/stat-scm/statsvn/trunk </developerConnection> <url> =09 http://stat-scm.svn.sourceforge.net/viewvc/stat-scm/statsvn/trunk/ </url> </scm> ... <repositories> <repository> <id>stat-scm-sourceforge</id> <name>stat-scm Sourceforge Maven 2 repository</name> =09 <url>http://stat-scm.sourceforge.net/maven2</url> </repository> <repository> <id>stat-scm-sourceforge-snapshot</id> <name>stat-scm Sourceforge Maven 2 SNAPSHOT repository</name> =09 <url>http://stat-scm.sourceforge.net/maven2-snapshots</url> </repository> </repositories> " All the best, Doug |