I run into this all the time. I'm working on A B & C simultaneously,
make changes to B, and then A, then build A, and forget to build and
install B.
This is one of many things that conceivably the maven2 Eclipse plugin
could handle, and possibly will one day. I've been using the 0.0.10
release of m2eclipse for a while, and it's only slightly worth having
installed. The quality of the plug-in is reflected in its version
number. It doesn't yet add enough value to recommend.
So if you're working on multiple dependent projects, for now you just
have to be disciplined about installing the dependency snapshots in your
local repository when you change them.
Cheers,
Mojo
swebb wrote:
Hi,
If I say have project A that depends on B & C is there anyway using the
combination of Eclipse/Maven2 to set up Eclipse so that if say project A & B
is local it will automatically build A against B's source rather than fetch
its jar from the Repro. What I mean by automattically is that we don't have
to touch anything once the POM and eclipse settings are set.
I ask about this because some people like to check all projects out and
other just the project they are working on and each has to mess around with
the eclipse settings each time. It would be good if they could just check
what they want out of svn and eclipse would automatically build against
local project sources if they were there otherwise use the maven repro !
Any thoughts, ideas ?
Thanks
Steve
--
Morris Jones
Monrovia, CA
http://www.whiteoaks.com
Old Town Astronomers http://www.otastro.org
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
