Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dixson3@gmail.com designates
 209.85.220.220 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=T9YqKLMxOXONWXlZIS6G2xb7cQlONbSS8QppLZQ7SjFSbJEN+sFueawnG+ZoSWQoV4
         xYtQhRX1kpq+IdLX9xJfACco8OmaaeM9bcHJoilzsyUHw/ZHjZ+XkPCpMn2fbvrBFu1i
         raUm+sgmAmKUXAY8Sa6wuwWHZmEqirRN+Aa4Y=
MIME-Version: 1.0
In-Reply-To: 
 <7C2EC2BAE9C867409CFF34390FB83E73075CF058@xmb-sjc-225.amer.cisco.com>
References: <49F4DCA6.5080802@mac.com> <49F8FCCF.70805@mac.com>
	 <4b7f2c670904291905v38c6e269x95d9c4419bca9f80@mail.gmail.com>
	 <7C2EC2BAE9C867409CFF34390FB83E73075CF058@xmb-sjc-225.amer.cisco.com>
Date: Sat, 2 May 2009 11:25:59 -0500
Message-ID: <b89544e50905020925h3cb519fcwe499228b1a78b192@mail.gmail.com>
Subject: Re: [vote] fix for etch-69 in release 1.1
From: James Dixson <dixson3@gmail.com>
To: etch-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

+1 from me too.

On Thu, Apr 30, 2009 at 9:05 AM, Gaurav Sandhir (gsandhir)
<gsandhir@cisco.com> wrote:
> +1
>
> -----Original Message-----
> From: Manoj Ganesan [mailto:manoj.ganesan@gmail.com]
> Sent: Wednesday, April 29, 2009 9:05 PM
> To: etch-dev@incubator.apache.org
> Subject: Re: [vote] fix for etch-69 in release 1.1
>
> + 1 for the inclusion.
> Manoj.
>
>
> On Wed, Apr 29, 2009 at 8:20 PM, scott comer <wert1y@mac.com> wrote:
>
>> ok, folks, i need some votes to proceed...
>>
>> scott out
>>
>>
>> scott comer wrote:
>>
>>> currently release 1.1 is pretty much in the can. but since there is a
>
>>> fix for this path problem for maven users that rick bolkey found so
>>> long ago, what do you say for putting it in 1.1?
>>>
>>> it doesn't break anything, and brian smith did check out the code and
>
>>> built his own version with the fix and it solved the problem.
>>>
>>> i've put a 1.0.2 special up (location noted in the comments of the
>>> issue) if anyone else is setup to try it. mainly i think that might
> be rick.
>>>
>>> +1 (include fix for etch-69 in release 1.1)
>>>
>>> scott out
>>>
>>>
>>
>