Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of gcjcu-commons-user@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Mail-Followup-To: commons-user@jakarta.apache.org
To: commons-user@jakarta.apache.org
From: =?ISO-8859-1?Q?J=F6rg?= Schaible <joerg.schaible@gmx.de>
Subject: Re: Where to get commons-discovery 0.3 and 0.4-snapshot?
Date: Tue, 14 Nov 2006 18:56:25 +0100
Lines: 40
Message-ID: <ejcvur$nfg$1@sea.gmane.org>
References: <F0D7281DAB048B438E8F5EC4ECEFBDDC0111DC0A@esmail.elsag.de>
 <31cc37360611140915u26c91d0fh7f96f911140be2d2@mail.gmail.com>
Reply-To: joerg.schaible@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8Bit
Mail-Copies-To: never
User-Agent: KNode/0.10.2
Sender: news <news@sea.gmane.org>

Hi Henri,

Henri Yandell wrote:

> On 11/13/06, J�rg Schaible <Joerg.Schaible@elsag-solutions.com> wrote:
>> Henri Yandell wrote on Tuesday, November 14, 2006 2:40 AM:
>>
>> [snip]
>>
>> > A 0.3 release was prepared and voted on, an svn tag made, but the
>> > actual release didn't happen. The site had been updated though - and
>> > was pushed out in mid-2006 for some unknown reason.
>> >
>> > Since then the following changes of interest have been made to trunk:
>> >
>> > * Logging dependency moved to 1.0.4.
>> > * Various build changes.
>> > * Moved from producing 1.1 compliant classes to 1.2+ compliant.
>> > * And most importantly, various code fixes from Dims:
>> >
>> > - Adding getSystemProperty in JDKHooks for handling SecurityException
>> > - Handle one more SecurityException in classLoader.getParent()
>> > - Check permission to create a class loader (Axis fails in Applet
>> > Scenarios - http://issues.apache.org/jira/browse/AXIS-2145)
>> >
>> > So...seems that an 18 month overdue release should happen. Thoughts?
>> > (besides ones mentioning farcical, laughter, crying or containing
>> > expletives).
>>
>> +1
>>
>> but we should possibly skip 0.3 and go with 0.4. Peolpe might have build
>> their own version from the tag and changes have been made since then.
> 
> Then a 0.3 from the tag, and a 0.3.1 or 0.4 from trunk?

I would simply go on with a 0.4 from trunk. And state the fact that an
official 0.3 is missing in the release notes.

- J�rg


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