if A has a pom file, mvn install will install it in your ~/.m2/repository (which maven searches before using the remote repository)
if it's not 'mavenized', you can use mvn install:install-file http://maven.apache.org/plugins/maven-install-plugin/usage.html Just make sure your dependency spec in B matches the one you install locally (and probably best it's different than the one in the remote) -sr On Oct 15, 2010, at 7:12 AM, thisguy wrote: Hi, I have two projects, A and B. B has a dependency on A. A's output (jar) is in my repository. Now say I want to change A's java code and then run B to see my changes. B will look in the repository for A's jar right? I don't want it to do that during development. I want B to use the local file system to get the new version of the A jar because I haven't deployed A to the repository yet. Does that make sense? Is there a nice mechanism to tell maven to use local project directory dependencies before searching the repository? Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/dependency-evaluation-order-tp3213753p3213753.html Sent from the Maven - Users mailing list archive at Nabble.com<http://Nabble.com>. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected]<mailto:[email protected]> For additional commands, e-mail: [email protected]<mailto:[email protected]> Sam Rash [email protected]<mailto:[email protected]>
