On 6 Dec 06, at 9:41 PM 6 Dec 06, Brett Porter wrote:

Cool. What's next?


1. Make sure that any fixes from the 2.0.x branch are present in trunk. I've seen a few discrepancies so I would just like to match those up.

2. Make another drop for the embedder so that Milos and Eugene can get caught up. This is really to get this working a little better for embedder users.

3. John and I talked about some refactoring and feel that the best thing we could do is a refactoring of the project builder, default plugin manager and the lifecycle executor. The best way forward here is to actually define how this all works by building up a body of POMs that define the inputs and decide what the output should look like. So basically starting the real effort of defining how everything gets pieced together. The code is our specification for constructing final output which is bad.

4. Once we decide what should happen we need to compare that to what is actually happening.

5. John wants to start writing a load more tests to make sure that capture all the quirks so we can emulate them if necessary.

6. Chop up the project builder, default plugin manager, and the lifecycle executor as they are too big, convoluted and hard to understand.

7. Let the bug fixing and patching begin!

Jason.

On 07/12/2006, at 11:51 AM, Andrew Williams wrote:

the maven.new branch which contained the work to get maven up to the latest and greatest plexus container and classworlds has been branched to trunk. The tests all pass and bootstrapping works here, please bug Jason or I if there appears to be any problems with this substantial change.

Andy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to