1) I'm encountering some integration failures in my build at work when
using -Dmaven.threads.experimental=1; I'll try to turn them into proper
bugs in the next few days.
2) In the documentation on http://github.com/krosenvold/maven3/ it says
that it does not yet build Maven 3. Does this mean that it's unable to
build Maven 3 in multithreaded mode? It seems to build OK for me in
non-multithreaded mode.
3) I noticed that the branch seems to be unable to run "mvn
eclipse:eclipse" on itself; the "Apache Maven 3.x" project is marked
"SUCCESS" but then all the subsequent projects are skipped. Is this
known? I filed it as http://github.com/krosenvold/maven3/issues/#issue/2
4) A point of terminology: I think the branch is now using the term "weave
mode" differently from the way I'd meant it when I introduced the term.
As I understood it, "weave mode" means running compile X compile Y compile
Z, then test X test Y test Z, as opposed to the default non-weave behavior
to compile X and test X, then compile Y and test Y, then compile Z and
test Z.
Is that what you think it means? Or is that what "violate lifecycle" means?
It seems like the branch uses "weave mode" to refer to any multithreaded
build, which means that it's now not possible in Kristian's branch to do
the coarse-grained multithreading I had working in my MNG-3004 branch.
Do I understand that correctly?
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
