Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <42E81D0D.5080805@apache.org>
Date: Thu, 28 Jul 2005 09:47:25 +1000
From: Brett Porter <brett@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [proposal] exec support in commons
References: <d8565s$ufl$1@sea.gmane.org> <87br6g9ewj.fsf@www.samaflost.de>
 <d89hjq$887$1@sea.gmane.org> <dc94up$46e$1@sea.gmane.org>
In-Reply-To: <dc94up$46e$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Well, both our replies did say we were swamped :)

At some point we will want this, so I will create an empty sandbox
project. You might like to read
http://jakarta.apache.org/commons/charter.html (you may already have)
Basically to start we need to send an email to this list with a
proposal, similar to what you've done already but with a bit more details:
- name (commons-exec?)
- rationale (this is really what you've already said, so include that)
- scope (the goals we'd like to achieve: feature X, Y, incorporate
functionality from Ant's exec and plexus-utils)
That should be all. List Stefan (I'll dob him in since he seemed
interested, he can always change his mind) and myself as initial committer.

Next, we can discuss the design choices and goals here using an [exec]
prefix on emails (or whatever is chosen).

I'll be happy to import any code from your patches. Please let me know
if you obtained it from another project such as Ant, plexus-utils or
somewhere else as I'll need to be checking that.

Thanks!

- Brett

Niklas Gustavsson wrote:

> Hi again,
>
> I never got any reply to the answers below so I'll try again :-)
>
> If you still exec support of interest, what would be the appropriate
> way  to proceed to either:
> 1. donate the code to an existing Commons project (possibly as a
> biggish patch)
> 2. create a new project ("exec") using the code as a starting point.
> 3. some other way
>
> I'm not a Apache commiter but would of course be happy to work by
> commiting patches.
>
> /niklas


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org