On Fri, Oct 15, 2010 at 10:12 AM, thisguy <[email protected]> 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.
Most IDEs can deal with this situation for you. What are you using? What Maven command are you using to build? Are you using -SNAPSHOT version numbers? Are A and B part of the same multi-module project under a parent pom? If so, then building "from the top" (parent) will do what you want. If you are down in B, Maven will look in the repository (first local, then remote) for A's jar. (Assuming they are totally separate projects,) you don't have to deploy your A jar to a remote repository, but you do need to get it into your local repo with 'mvn install' in order for B to see it. Lots of details missing here, hopefully those random bits of advice will help. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
