The following is _not_ recommended. Once you get more used to Maven you will realize that storing your binary artifacts in SVN is a "bad thing".
Fundamentally, they are a different creature from the source code. What you should do is use a Maven repository manager (e.g. Nexus, Artifactory, etc) and deploy your binary artifacts to that manager. There is a poor man's solution to your problem... and that is to fake a remote repository in subversion providing your subversion is served over http (if Maven > 2.0) or https (if Maven > 2.0.5) You add a repository definition where the repository URL is the place in SVN where you are keeping your remote repository Basically, you'd be doing similar to what has been done at https://maven2-repository.dev.java.net That way your binaries are kept in SVN, but the developer does not check out the trunk of that repository, only accesses it via HTTP -Stephen On Sat, Apr 19, 2008 at 8:28 AM, Lachlan Deck <[EMAIL PROTECTED]> wrote: > Hi Mark, > > On 19/04/2008, at 5:13 PM, Mark Struberg wrote: > > To be more specific: > > Look at the maven-deploy-plugin > > > > http://maven.apache.org/plugins/maven-deploy-plugin/usage.html > > > > and use the > > > > > mvn deploy:deploy-file > > > > > mojo > > > > Example: > > mvn deploy:deploy-file -DrepositoryId=myrepo.id \ > > -Dfile=myjartoupload.jar \ > > -DgroupId=my.groupId \ > > -DartifactId=my-artifactId \ > > -Dversion=myversion \ > > -Dpackaging=jar \ > > > > You can use this mojo from everywhere, since it is marked as > > '@requiresProject false'. > > > > If this was successfull (check your ~/.m2/repository), you may remove > > this jar from your lib > > folder and add the dependency in your pom. > > > > I'm wondering how this helps another developer who checks out the project? > Or indeed if my system gets somehow hosed? > > I have no permissions to be creating a shared repo. Thus I need to be able > to keep the jars with the project. With ant this was completely simple (one > of the few nice things about ant)... so I don't quite appreciate why it > needs to be so complex with maven? > > Fair enough for world-sharable jars (i.e., all the various open-source > projects out there) - but for a private jar I can't see the sense in it (at > least yet). > > Thanks... > > with regards, > -- > > Lachlan Deck > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
