On 2009-09-27, at 8:30 AM, Nayan Hajratwala wrote:
On Sep 27, 2009, at 11:26 AM, Jason van Zyl wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will
force a build of project a... but all the jar files will be
installed into and resolved from your local maven repository
(~/.m2/repository), not the target directory.
The JARs will not be resolved from the local repository by default
if you are using M2Eclipse. They are resolved from the workspace
which is one of the primary reasons for using M2Eclipse: the live
management of your dependencies and being able to work with them as
you would expect in Eclipse.
Doh -- thanks for catching my error. I (believe it or not) actually
knew this. Perhaps I hadn't had enough coffee yet when writing my
response :-)
btw, thanks for all the great usability/stability improvements in
m2eclipse over the past couple years!
They have all honestly been in the last 6 months where all the
improvements have been made. You can specifically thank Igor and
Benjamin. Igor on the M2Eclipse side as he's really made M2Eclipse
production quality, and Benjamin has done the same on the Maven side.
They work together constantly to try and improve the user experience
from Maven workflow into Eclipse.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
