We've discussed this subject on m2e dev list a lot recently and I
believe the conclusion is that both collocated and separate output
folders cause problems for some projects and development "styles", for
the lack of a better word.
For example, I mostly work with maven core and various maven plugin
projects. These projects make heavy use of code and resource generation
and I could not make them work with separate output folders reliably.
But everything works almost perfectly with m2e using maven output folders.
On the other hand, however, I hear people are having troubles with
collocated output folders when they switch between m2e and cli often.
Like you describe, either eclipse gets confused by out-of-workspace
changes or maven cli picks up stale/broken files produced by eclipse and
neither eclipse nor maven cli would give any meaningful explanation of
the problems.
Michael McCallum wrote:
A long time back i discovered that if you have the same target output for
eclipse and maven you end up with broken shit all over the place, intemittent
errors. All really unpleasant.
The default settings for eclipse:eclipse and eclipse:m2eclipse set the outputs
to the same. Does this actually work for people? Maybe locking on windows
actually make a positive impact finally?
Thoughts anyone?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
