Re: The Embedder as our only export interface

2007-06-07 Thread Jason van Zyl
On 6 Jun 07, at 11:28 PM 6 Jun 07, Brett Porter wrote: On 07/06/2007, at 12:09 AM, Jason van Zyl wrote: - we will have to retain runtime compatibility in 2.1, but not necessarily API compatibility which is fine For plugins yes, for sanity. Not any other APIs. Plugins using older artifac

Re: The Embedder as our only export interface

2007-06-06 Thread Brett Porter
On 07/06/2007, at 12:09 AM, Jason van Zyl wrote: - we will have to retain runtime compatibility in 2.1, but not necessarily API compatibility which is fine For plugins yes, for sanity. Not any other APIs. Plugins using older artifact APIs are not my concern for 2.1. Those plugins will ha

Re: The Embedder as our only export interface

2007-06-06 Thread Jason van Zyl
On 6 Jun 07, at 1:19 AM 6 Jun 07, Brett Porter wrote: (Getting annoyed by everyone replying to each other across 3 threads, so picking this one to move forward from) On 06/06/2007, at 5:29 AM, Jason van Zyl wrote: Here is my reasoning as the Embedder as the only form we should be exposing

Re: The Embedder as our only export interface (was: Re: svn commit: r543671 - in /maven/components/trunk: maven-core/ maven-core/src/main/java/org/apache/maven/core/monitor/event/ maven-core/src/main/

2007-06-06 Thread Stephane Nicoll
+1 Stéphane On 6/6/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: I agree. If we try to refactor everything now, it just means longer term before 2.1 can come out. Committing to a public façade for future compatibility and abstraction from internals is the way to go. -

Re: The Embedder as our only export interface

2007-06-05 Thread Brett Porter
(Getting annoyed by everyone replying to each other across 3 threads, so picking this one to move forward from) On 06/06/2007, at 5:29 AM, Jason van Zyl wrote: Here is my reasoning as the Embedder as the only form we should be exposing in the short term (the emphasis being on short term) h

Re: The Embedder as our only export interface (was: Re: svn commit: r543671 - in /maven/components/trunk: maven-core/ maven-core/src/main/java/org/apache/maven/core/monitor/event/ maven-core/src/main/

2007-06-05 Thread Carlos Sanchez
ing to a public façade for future compatibility and abstraction from internals is the way to go. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 05, 2007 12:29 PM To: Maven Developers List Subject: The Embedder as our only export interface (was: Re:

RE: The Embedder as our only export interface (was: Re: svn commit: r543671 - in /maven/components/trunk: maven-core/ maven-core/src/main/java/org/apache/maven/core/monitor/event/ maven-core/src/main/

2007-06-05 Thread Brian E. Fox
05, 2007 12:29 PM To: Maven Developers List Subject: The Embedder as our only export interface (was: Re: svn commit: r543671 - in /maven/components/trunk: maven-core/ maven-core/src/main/java/org/apache/maven/core/monitor/event/ maven-core/src/main/java/org/apache/maven/core/monitor/logging

The Embedder as our only export interface (was: Re: svn commit: r543671 - in /maven/components/trunk: maven-core/ maven-core/src/main/java/org/apache/maven/core/monitor/event/ maven-core/src/main/java

2007-06-05 Thread Jason van Zyl
Here is my reasoning as the Embedder as the only form we should be exposing in the short term (the emphasis being on short term) http://docs.codehaus.org/display/MAVEN/The+Embedder+for+all+client+use +in+2.1 On 4 Jun 07, at 9:01 PM 4 Jun 07, Carlos Sanchez wrote: I got this lost between th