Re: m2eclipse was: Proposal after-the-fact: Experimental multithreading support

2009-11-11 Thread Igor Fedorenko
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

Re: m2eclipse was: Proposal after-the-fact: Experimental multithreading support

2009-11-10 Thread Dan Fabulich
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

Re: m2eclipse was: Proposal after-the-fact: Experimental multithreading support

2009-11-10 Thread Brian Fox
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

m2eclipse was: Proposal after-the-fact: Experimental multithreading support

2009-11-10 Thread Dan Fabulich
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