You actually do not want to store your dependencies in SCM. No matter what you think on this issue, you really do not want to store your dependencies in SCM.
You want to store your dependencies in a Maven Repository Manager (e.g. Nexus, Artifactory, etc) These are really really easy to set up and are essential for ensuring that you have a reproducible build going forward. Now, you might want to store your Maven Repository Manager data in SCM.... and that might include the artifacts that it is proxying/hosting for you, but that would only be for cases where your corporate IT are refusing to ensure DR for anything other than your SCM. My preference is to have the Maven Repository Manager covered by DR directly. You definately do not want to be copying your local repository into SCM and checking it out on each developers machine. The local repository is not designed to work that way. -Stephen 2009/12/11 Xiaohui Chen <[email protected]> > Hi, > > I want to store our dependencies into SCM. There maybe other better ways. > The way that I see is some how change the maven's local repository to point > to somewhere in the source tree. But the local repository path has to be an > absolute path, that will not work because different developer have > different > local working copies. Is there a way to specify the local repository to be > a > relative path to the mvn binary? > > Thanks. >
