Build works fine with JDK 1.5 on Windows 7. Artifacts look good.
The only nitpick I found is that the binary distribution does not
contain the source and Javadocs jar.
So +1.
Oliver
Am 17.11.2010 02:27, schrieb sebb:
This is a vote to release Apache Commons NET 2.2 based on RC3.
Changes si
On 17 November 2010 19:53, Luc Maisonobe wrote:
> Le 17/11/2010 13:48, Phil Steitz a écrit :
>> On 11/16/10 7:10 PM, Gilles Sadowski wrote:
>> [...]
>> I think this transition is the smoother path for our users. Do you
>> think
>> this change is the way to go ?
>
> -0
Le 17/11/2010 13:48, Phil Steitz a écrit :
> On 11/16/10 7:10 PM, Gilles Sadowski wrote:
> [...]
> I think this transition is the smoother path for our users. Do you
> think
> this change is the way to go ?
-0
>>>
>>> +1
>>>
My first impression is that it is a lo
Hi Ralph,
Ralph Goers wrote:
> Moved from user's list.
>
> On Nov 17, 2010, at 7:27 AM, Jörg Schaible wrote:
>
>> Hi Ralph,
>>
>>>
>>> I'm not sure what you mean Jorg. VFS is an optional dependency so the
>>> Java 5 requirement isn't an issue (although the doc probably needs to be
>>> updated
Hi Damjan,
These are indeed limitations of the current api.
For the sake of backward compatibility as well as to honor
Sanselan's design principle of making the common case easy (almost all
image files contain a single image, for example) I would suggest
adding new, separate methods/propert
James Carman wrote:
> On Wed, Nov 17, 2010 at 12:25 PM, Gary Gregory
> wrote:
>>> My feeling is that if we are upgrading to Java 5 then we should do it
>>> correctly. Go ahead and break compatibility where required. In that view
>>> the changes done to the Comparables were done correctly. I susp
Hi,
I’ve spotted a bug in IteratorChain:
When the first iterator is empty, hasNext() returns false the first time
it’s called even if the next iterators are not empty.
This snippet shows that incorrect behavior:
Iterator it =
IteratorUtils.chainedIterator(Arrays.asList().iterator(),
Arra
On Wed, Nov 17, 2010 at 12:25 PM, Gary Gregory
wrote:
>> My feeling is that if we are upgrading to Java 5 then we should do it
>> correctly. Go ahead and break compatibility where required. In that view the
>> changes done to the Comparables were done correctly. I suspect they will
>> cause very
> -Original Message-
> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
> Sent: Wednesday, November 17, 2010 06:35
> To: Commons Developers List
> Subject: Re: [VFS] Analysis of binary compatibility breaks between 1.0 and
> 2.0; release strategy
>
>
> On Nov 17, 2010, at 2:54 AM, seb
Moved from user's list.
On Nov 17, 2010, at 7:27 AM, Jörg Schaible wrote:
> Hi Ralph,
>
>>
>> I'm not sure what you mean Jorg. VFS is an optional dependency so the Java
>> 5 requirement isn't an issue (although the doc probably needs to be
>> updated) and none of the changes made to VFS of late
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-quartz has an issue affecting its community
integratio
Switching to dev list, which is more appropriate.
On 17 November 2010 15:27, Jörg Schaible wrote:
> Hi Ralph,
>
> Ralph Goers wrote:
>
>>
>> On Nov 17, 2010, at 12:31 AM, Jörg Schaible wrote:
>>
>>> Hi Patel,
>>>
>>> Patel, Ronak Avinash (US SSA) wrote:
>>>
Any ideas when VFS will be release
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
On Nov 17, 2010, at 2:54 AM, sebb wrote:
> On 17 November 2010 07:17, Ralph Goers wrote:
>>
>
>> I'm not suggesting we change these. Since we are adopting Java 5 I would
>> prefer to change these now and move forward.
>
> To change or not to change? Sorry, cannot understand the last paragrap
Hi.
> > [...]
>
> I think what Luc is suggesting is that by introducing
> MathUserException in 2.2 without a material compatibility break
> (i.e. nothing that would actually break any 2.1 code) we could set
> users to start doing this work incrementally before 3.0 is released.
> That seems like a
On 11/16/10 7:10 PM, Gilles Sadowski wrote:
[...]
I think this transition is the smoother path for our users. Do you think
this change is the way to go ?
-0
+1
My first impression is that it is a lot of changes for 2.2 without any
benefit when users will switch to 3.0; they will still have
On 11/16/10 4:16 PM, Luc Maisonobe wrote:
Hi all,
Some of our algorithms do use random number generation. I quickly
reviewed them and found different ways to use them.
Genetic algorithm use a single static RandomGenerator shared by all
instances. It default to JDKRandomGenerator and can be rese
On 17 November 2010 07:17, Ralph Goers wrote:
>
> On Nov 16, 2010, at 4:19 PM, sebb wrote:
>
>> On 17 November 2010 00:06, ralph.goers @dslextreme.com
>> wrote:
>>> I'm not sure why the tool didn't catch it, but a few methods now return
>>> Map where they previously returned Map. I didn't check f
Hi
I've noticed a number of problems with Sanselan's API:
1. There is a way to read files with multiple images
(Sanselan.getAllBufferedImages()) but there is no way to write files
with multiple images. This limits the usability of all multi-image
file formats.
2. There needs to be a way to config
On Wed, Nov 17, 2010 at 12:19 AM, Luc Maisonobe wrote:
> > In Mahout, we did this by having a static method in a utility class for
> > getting a standard generator for either testing or normal operation.
> This
> > has turned out very well.
>
> It's a very good idea for production code, but I am
Le 17/11/2010 02:14, Ted Dunning a écrit :
> It is also desirable to have a way to inject a test generator so that test
> cases can be made deterministic.
Yes, this is what is done in the classes that already have a constructor
argument, the tests do use it and use hard coded funny constants to se
22 matches
Mail list logo
