My idea was that > 90% of the potential users will use Java 6+, thus it
made sense to me, but of course we can change it and wait till we move to
Java 6 ourselves.
Thomas
On Sun, Apr 21, 2013 at 11:10 PM, sebb wrote:
> On 21 April 2013 21:30, Thomas Neidhart wrote:
>
> > On 04/21/2013 09:20 P
On Sun, Apr 21, 2013 at 5:27 AM, sebb wrote:
> On 21 April 2013 05:44, Henri Yandell wrote:
>
> > Proposed fix: https://issues.apache.org/jira/browse/IO-295
> >
> >
> I did wonder about using Reflection to solve the issue for Java 7.
>
> Should we still use the command shell for Java 6?
>
>
Doe
+1 :)
Regular cadence is huge.
On Sat, Apr 20, 2013 at 11:57 PM, Gary Gregory wrote:
> My view is that we do not have to fix or address everything in each
> release that is outstanding. In my mind its important to keep the
> release trains moving.
>
> Gary
>
> On Apr 21, 2013, at 0:45, Henri Ya
On 21 April 2013 21:30, Thomas Neidhart wrote:
> On 04/21/2013 09:20 PM, sebb wrote:
> > On 21 April 2013 16:21, wrote:
> >
> >> Author: tn
> >> Date: Sun Apr 21 15:21:45 2013
> >> New Revision: 1470311
> >>
> >> URL: http://svn.apache.org/r1470311
> >> Log:
> >> Suppress deprecation warnings fo
On 04/21/2013 09:20 PM, sebb wrote:
> On 21 April 2013 16:21, wrote:
>
>> Author: tn
>> Date: Sun Apr 21 15:21:45 2013
>> New Revision: 1470311
>>
>> URL: http://svn.apache.org/r1470311
>> Log:
>> Suppress deprecation warnings for ArrayStack usage.
>>
>>
> Surely the code should use whatever the
On 21 April 2013 16:21, wrote:
> Author: tn
> Date: Sun Apr 21 15:21:45 2013
> New Revision: 1470311
>
> URL: http://svn.apache.org/r1470311
> Log:
> Suppress deprecation warnings for ArrayStack usage.
>
>
Surely the code should use whatever the replacement is?
> Modified:
>
> commons/proper/co
On 21 April 2013 05:44, Henri Yandell wrote:
> Because they're low hanging fruit:
>
> Javadoc: https://issues.apache.org/jira/browse/IO-299
> Javadoc: https://issues.apache.org/jira/browse/IO-328
>
I can do those; partly I was waiting for some feedback, which I now have.
> Proposed fix: https:
Build using Java 1.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Continuum-Build-Host: vmbuild
X-Continuum-Project-Id: 83
X-Continuum-Project-Name: Commons IO
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildI
I agree. I think it is vital that people have the feeling that something is
happening (without following the Dev ML). This works best by pushing out
releases frequently.
2013/4/21 Gary Gregory
> My view is that we do not have to fix or address everything in each
> release that is outstanding. I
Le 21/04/2013 01:24, Emmanuel Bourg a écrit :
> Le 09/04/2013 09:23, Emmanuel Bourg a écrit :
>
>> I packaged it last week, it's in the new package queue and
>> should appear in the Debian repository soon.
>
> The package is now available in the experimental repository:
>
> http://packages.qa.de
10 matches
Mail list logo
