sverhagen wrote:
Hi Oleg, would developers in these environments never run command-line Maven?
We demand our developers to run a full command-line Maven just before they
commit their work to Subversion, to make sure all tests succeed.
What's the difference from running it in m2eclipse? Well - there was -
don't get me wrong :), it used to use maven-2.1-SNAPSHOT, but starting
with 0.9.3 or somewhere around that (m2eclispe guys will correct me) -
you can point it to external Maven install and have that install do all
the work.
Apparently
we've not the trust yet in Eclipse (and m2eclipse) or perhaps not the
patience to wait for it to finish on our entire base of projects (there are
about 80 of them).
Well - you have a problem right away - if you have to open 80 projects
in Eclipse more often than for occasional refactoring, to me it means
you don't have true binary dependency separation in the code. Ideal
maximum number for me is 20, which is enough for working on a rather
complex feature.
The lack of trust comes from a lot of "red crosses" (errors) in Eclipse, in
the past, which we're now looking into more thouroughly, hency my presence
in these forums/mailing lists.
I believe it's "in the past", the m2eclipse came a long way since then.
Thanks,
Oleg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
