Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates
 66.249.82.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=YMB9fVwbWyAB0JGTTjWobjy56ZjsVuaaok3fQRRq0TRvBMKLRsbaqsEVJKcFV+W0A9Nj7HJYVp09RTrTBUyQHJrvoy0JNgXPDNJ22THujXo68EZ8A4fwJhlL4LoDeEObJLt3KUYkIyEHkI7CncmgoKJiUI/ujx6cnaDRiPRhqtw=
Message-ID: <a32f6b020703152121x374c5c22i654cfae4a71eb473@mail.gmail.com>
Date: Fri, 16 Mar 2007 00:21:46 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [Maven] [POLL] Stay on 2.0.4, move to 2.0.5 or wait for 2.0.6
In-Reply-To: <a32f6b020703152115v4f49b7c4y11e4abc035039552@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_35781_2822391.1174018906047"
References: <a32f6b020703152115v4f49b7c4y11e4abc035039552@mail.gmail.com>

------=_Part_35781_2822391.1174018906047
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think we have workarounds for some issues and live fine with them but I
just want
to find out what people are thinking and if there are bugs that matter.

I know for one if this darn bug associated with maven repo permissions were
guaranteed
to be fixed I'd be moving to that version but I don't think this is the case
at least with
2.0.5 which breaks our build BTW.  I did not investigate this further
however I'm hoping
2.0.6 does not and fixes this little issue.

Alex

On 3/16/07, Alex Karasulu <akarasulu@apache.org> wrote:
>
> Hi,
>
> Maven just had it's 2.0.5 release but a 2.0.6 seems to be in the making.
> Should we stick
> to what we have since it just works or should we move on to 2.0.5 or just
> wait until 2.0.6?
>
> [ X ] Don't change if it works
> [  ] Move on to 2.0.5
> [  ] Wait to upgrade when 2.0.6 is released
>
> --------
>
> Alex
>

------=_Part_35781_2822391.1174018906047
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think we have workarounds for some issues and live fine with them but I just want <br>to find out what people are thinking and if there are bugs that matter.<br><br>I know for one if this darn bug associated with maven repo permissions were guaranteed 
<br>to be fixed I&#39;d be moving to that version but I don&#39;t think this is the case at least with<br>2.0.5 which breaks our build BTW.&nbsp; I did not investigate this further however I&#39;m hoping<br>2.0.6 does not and fixes this little issue.
<br><br>Alex<br><br><div><span class="gmail_quote">On 3/16/07, <b class="gmail_sendername">Alex Karasulu</b> &lt;<a href="mailto:akarasulu@apache.org">akarasulu@apache.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>Maven just had it&#39;s 2.0.5 release but a 2.0.6 seems to be in the making.&nbsp; Should we stick<br>to what we have since it just works or should we move on to 2.0.5 or just wait until 2.0.6?<br><br>[ X ] Don&#39;t change if it works
<br>[&nbsp; ] Move on to 2.0.5 <br>[&nbsp; ] Wait to upgrade when 2.0.6 is released<br><br>--------<br><span class="sg"><br>Alex<br>
</span></blockquote></div><br>

------=_Part_35781_2822391.1174018906047--