This is more a plan to implement the existing multi-threading patch
than an actual proposal. Imo a proposal should describe the
solution...ie how will this multi-threading work, how will it decide
what to build and in what order, etc. I think essentially the details
you Ralph and I briefly discusse
This is now an official proposal here:
http://cwiki.apache.org/confluence/display/MAVEN/Experimental+Multithreading+Support
(I didn't have karma to edit this page until a few minutes ago; you might
need to request karma as well, especially since this the first proposal
in this new location.)
Unfortunately m2e will have to wait until alpha-4 due to PLX-444,
assuming alpha-3 is not respun that is. Do not break trunk just yet ;-)
--
Regards,
Igor
Dan Fabulich wrote:
Brian Fox wrote:
Does that mean that changes that we make in the Apache trunk can
automatically break people's Eclipse
Brian Fox wrote:
Does that mean that changes that we make in the Apache trunk can
automatically break people's Eclipse builds out in the wild, even without an
official release?
No. Igor has to bundle them into M2e before it's directly used, so it
could break the next time we update. It's a ps
On Tue, Nov 10, 2009 at 3:21 PM, Dan Fabulich wrote:
> Jason van Zyl wrote:
>
>> The trunk is now critical for M2Eclipse and anyone else who is embedding
>> and new features just aren't going in without adequate ITs.
>
> m2eclipse depends on the Maven 3.0-SNAPSHOT trunk?
>
Kinda
> Does that mean
Jorg Heymans wrote:
Would the multithreading feature make it easier or harder to implement
something like [1], ie distribute the different modules of a reactor
build across different machines ? Or is it completely unrelated you
think ?
No harder, but not much easier. With that said, I do ha
Hi Dan,
Would the multithreading feature make it easier or harder to implement
something like [1], ie distribute the different modules of a reactor
build across different machines ? Or is it completely unrelated you
think ?
Thanks,
Jorg Heymans
[1]
http://n4.nabble.com/New-plugin-to-distribute-
Jason van Zyl wrote:
The trunk is now critical for M2Eclipse and anyone else who is embedding
and new features just aren't going in without adequate ITs.
m2eclipse depends on the Maven 3.0-SNAPSHOT trunk?
Does that mean that changes that we make in the Apache trunk can
automatically break pe
Jason van Zyl wrote:
It's not going in that fast.
Fair enough; that seems to be the consensus.
Sorry, but passing all the existing ITs is the first step and then there
is ITs for the feature you multi-threading feature itself.
I've got a couple of ITs for MNG-3004 parallel projects on my m
On 2009-11-10, at 4:02 AM, Dan Fabulich wrote:
On Friday I was playing cowboy with my experimental thread support,
but here's a more formal proposal around parallel project support in
Maven 3.0.
OUTSTANDING ISSUES
In my earlier revision 833566, I attempted to fix MNG-3004:
"Allow build
On Mon, Nov 9, 2009 at 8:02 PM, Dan Fabulich wrote:
> I attempted to check in the code in time for 3.0-alpha-3 a few days ago.
> That code was rolled back over the weekend and now lives in the MNG-3004
> branch, because it broke integration tests. All integration tests now pass
> on my machine wi
On Friday I was playing cowboy with my experimental thread support, but
here's a more formal proposal around parallel project support in Maven
3.0.
OUTSTANDING ISSUES
In my earlier revision 833566, I attempted to fix MNG-3004:
"Allow build lifecycle to execute projects in parallel"
http://j
12 matches
Mail list logo
