On 15/10/2010 10:35 AM, Antonio Petrelli wrote:
2010/10/15 Wendy Smoak<[email protected]>:
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?
In particular, using m2eclipse with "workspace resolution" enabled
(that is the default) does what you need.
That gets it out of your active projects (Eclipse workspace after "build
of A") rather than your local repository(~.m2) version of A after install.
Not always what you want but usually is OK.
Just be aware of the difference.
Ron
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
