Le 15/02/2012 07:32, Sébastien Brisard a écrit :
Dear all,
do we need to clear all Findbugs/PMD warning prior to releasing?
Yes, and checkstyle too.
In some cases, there are false positive which must be handled by adding
the appropriate filter using specific filtering comments in the code for
Hi.
do we need to clear all Findbugs/PMD warning prior to releasing?
Yes, and checkstyle too.
We'll have to make an exception for BOBYQAOptimizer: I don't want to
eliminate all those potential clues pointing at the needed improvements
towards a clean Java implementation.
If the CheckStyle
Hi.
Can we post the Javadocs generated from the latest trunk on the web site?
IIRC, it was Sébastien who did it last time. Can you do it again? Or please
let me know how I can do it.
Thanks,
Gilles
-
To unsubscribe, e-mail:
How do I, or can someone please tell Gump to use slf4j 1.5.5 and not
whatever is laying about?
Thank you,
Gary
On Wed, Feb 15, 2012 at 1:08 AM, Gump iss...@commons.apache.org wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information
+1
Looks good to me. All the issues I found in RC1 have been addressed.
Thank you!
Gary
On Tue, Feb 14, 2012 at 5:03 PM, sebb seb...@gmail.com wrote:
Trying again - I hope I've fixed all the problems found previously.
This is a vote to release Apache Commons NET 3.1 based on RC2.
[ ] +1
OK, I submited a patch that includes comments and documentation. Let me know
if I need to write more, but I think I've covered the functionality of the
classes.
Patrick
-Original Message-
From: Gilles Sadowski [mailto:gil...@harfang.homelinux.org]
Sent: Tuesday, February 14, 2012 7:46
Hi all,
I use a minimum integration step size of 1e-15, and got this error message:
org.apache.commons.math.exception.NumberIsTooSmallException: minimal
step size (8.97E-16) reached, integration needs 1.00E-15
It was generated here in AdaptiveStepSizeIntegrator, at line 326:
On Wed, Feb 15, 2012 at 7:23 AM, Gary Gregory garydgreg...@gmail.com wrote:
How do I, or can someone please tell Gump to use slf4j 1.5.5 and not
whatever is laying about?
Doesn't that run counter to the very purpose of Gump?
Matt
Thank you,
Gary
On Wed, Feb 15, 2012 at 1:08 AM, Gump
On Wed, Feb 15, 2012 at 10:38 AM, Matt Benson gudnabr...@gmail.com wrote:
On Wed, Feb 15, 2012 at 7:23 AM, Gary Gregory garydgreg...@gmail.com
wrote:
How do I, or can someone please tell Gump to use slf4j 1.5.5 and not
whatever is laying about?
Doesn't that run counter to the very purpose
Le 15/02/2012 15:28, Dennis Hendriks a écrit :
Hi all,
Hi Dennis,
I use a minimum integration step size of 1e-15, and got this error message:
org.apache.commons.math.exception.NumberIsTooSmallException: minimal
step size (8.97E-16) reached, integration needs 1.00E-15
It was
2012/2/15 Gilles Sadowski gil...@harfang.homelinux.org:
Hi.
Can we post the Javadocs generated from the latest trunk on the web site?
IIRC, it was Sébastien who did it last time. Can you do it again? Or please
let me know how I can do it.
Yes, I did it, I've even written it down somewhere.
Should be done now. I need to check that everything went all right,
but site has been deployed.
S
Le 15 février 2012 17:37, Sébastien Brisard
sebastien.bris...@m4x.org a écrit :
2012/2/15 Gilles Sadowski gil...@harfang.homelinux.org:
Hi.
Can we post the Javadocs generated from the latest
Hi,
finally I've found the time to answer to this topic :) We had a similar
discussion a while ago [1]. Back then James suggested to drop
collections completely in favor of google guava. I have started to
implement QueryableCollections in trunk anyway, because I still disagree
with James.
I
Hi
In fact the annotation can cause a test to succeed when it should fail.
If the NPE occurs too early in the test, the test will be marked as
successful.
If you want to ensure that the NPE only occurs in the last statement
of the test case, then drop the expected qualifier and use the
I would recommend guava over collections as well so it sounds like you
disagree with both of us!
:-)
On Wed, Feb 15, 2012 at 1:07 PM, Benedikt Ritter
b...@systemoutprintln.dewrote:
finally I've found the time to answer to this topic :) We had a similar
discussion a while ago [1]. Back then
Guava is a fine product but I'd like to see a generics version of
[collections]. I wonder what state trunk is in and if could be released
soon...
Gary
On Wed, Feb 15, 2012 at 1:13 PM, Ted Dunning ted.dunn...@gmail.com wrote:
I would recommend guava over collections as well so it sounds like
Hi all guys,
I notice that the methods getConnectedVertices( V v ) and getEdge( V
source, V target ) into the class BaseGraph are not protect if a user
passes a vertex that not exists.
Moreover in the first case the system throws a NPE and in the second case
the system accepts the argument but
OK, it is not yet published, but if you go to
http://commons.apache.org/ (using 140.211.11.10 port 80 as a proxy),
then you'll see the changes!
Sébastien
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
Yes , i know , but , arent other products like Tomcat 7.0 being hurt
by being dependent on a pre-generics version of Commons Collections ?
Leandro A. Pezzente
On miércoles, 15 de febrero de 2012 at 3:23 PM, Gary Gregory
wrote:Guava is a fine product but I'd like to see a generics version
of
On 02/15/2012 02:41 PM, Patrick Meyer wrote:
OK, I submited a patch that includes comments and documentation. Let me know
if I need to write more, but I think I've covered the functionality of the
classes.
Hi Patrick,
thanks for the patch. I have applied it together with additional code
Hola!
I'd recommend to throw the GraphException, as we reported in the javadoc:
* bNOTE/b: implementors have to take in consideration
throwing a {@link GraphException}
* if an error occurs while performing that operation.
How does it sound?
all the best,
-Simo
As far as I can tell, it looks pretty generified ;) But as I said, I'm
having that name clash error.
Okay, so it is consensus, that no more effort (regarding new features)
should be put into collections?
Benedikt
Am 15.02.2012 19:23, schrieb Gary Gregory:
Guava is a fine product but I'd like
Am 15.02.2012 20:21, schrieb leandro.pezze...@hush.com:
Yes , i know , but , arent other products like Tomcat 7.0 being hurt
by being dependent on a pre-generics version of Commons Collections ?
That's no problem. There is no need to update to the latest version. The
old versions will be
On 15/02/2012 20:14, Benedikt Ritter wrote:
Am 15.02.2012 20:21, schrieb leandro.pezze...@hush.com:
Yes , i know , but , arent other products like Tomcat 7.0 being hurt
by being dependent on a pre-generics version of Commons Collections ?
With my Tomcat committer hat on:
No. Primarily because
Hi Matt,
I have just created an issue for the work on enhancements on the Generator API
[1].
I will try to take a look at this this week.
Thanks Matt, in the meantime I will read other parts of the code base and will
work on the other existing issues to see if I can provide patches for
Hi Benedict,
Benedikt Ritter wrote:
Hi,
finally I've found the time to answer to this topic :) We had a similar
discussion a while ago [1]. Back then James suggested to drop
collections completely in favor of google guava. I have started to
implement QueryableCollections in trunk anyway,
On Wed, Feb 15, 2012 at 2:35 PM, Jörg Schaible joerg.schai...@gmx.de wrote:
Hi Benedict,
Benedikt Ritter wrote:
Hi,
finally I've found the time to answer to this topic :) We had a similar
discussion a while ago [1]. Back then James suggested to drop
collections completely in favor of
Looks good!
+1
Oliver
Am 14.02.2012 23:03, schrieb sebb:
Trying again - I hope I've fixed all the problems found previously.
This is a vote to release Apache Commons NET 3.1 based on RC2.
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because...
tag:
hi,
I'd recommend to throw the GraphException, as we reported in the javadoc:
I was thinking to use the method graph.utils.Assertions.checkArgument, it
throws an IllegalArgumentEx, but also GraphExpetion sounds good!
one more thing, the method getEdge() creates an instance of VertexPair for
On Wed, Feb 15, 2012 at 12:44 PM, Matt Benson gudnabr...@gmail.com wrote:
On Wed, Feb 15, 2012 at 2:35 PM, Jörg Schaible joerg.schai...@gmx.de wrote:
Hi Benedict,
Benedikt Ritter wrote:
Hi,
finally I've found the time to answer to this topic :) We had a similar
discussion a while ago [1].
Hola,
yes, I think so, every wrong behavior in the data structure should
throw GE, according to what we already agreed on on Graph contract.
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On
Bene,
please have a look at the javadoc before
http://docs.oracle.com/javase/1.5.0/docs/api/java/util/Map.html and
see why get(K) cannot be added.
HTH,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
Hi,
thanks for the hint. Maybe I gave too little context to my question. I
wasn't trying to add something to MultiMapK, V. It is checked in this
way in the repo. So I guess get(K key) in MultiMap will never work and
can be considered broken (and a ticket should be filed)?
Benedikt
Am
I looked at it again. I get it now. But it is really confusing... Forget
about it.
Good night! :)
Am 16.02.2012 00:17, schrieb Benedikt Ritter:
Hi,
thanks for the hint. Maybe I gave too little context to my question. I
wasn't trying to add something to MultiMapK, V. It is checked in this
way
On Wed, Feb 15, 2012 at 5:17 PM, Benedikt Ritter
b...@systemoutprintln.de wrote:
Hi,
thanks for the hint. Maybe I gave too little context to my question. I
wasn't trying to add something to MultiMapK, V. It is checked in this way
in the repo. So I guess get(K key) in MultiMap will never work
Hi.
Should be done now.
Thanks!
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
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-digester3 has an issue affecting its community integration.
This
Looks great, thanks!
-Original Message-
From: Thomas Neidhart [mailto:thomas.neidh...@gmail.com]
Sent: Wednesday, February 15, 2012 2:28 PM
To: dev@commons.apache.org
Subject: Re: [Math] Toward releasing 3.0 ?
On 02/15/2012 02:41 PM, Patrick Meyer wrote:
OK, I submited a patch that
Hi,
usage of ensureBufferSize() seems to be 'asymptotic' safe (despite the
fact that a line separator might be much bigger than
DEFAULT_BUFFER_SIZE, see below, and that no body else use the function
as he is told by description..).
/** Increases our buffer by the {@link
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-vfs2-test has an issue affecting its community integration.
This
Hello,
should I create a new JIRA ticket to remind people that in the end, we
need to get rid of
// CHECKSTYLE: stop all
and
// CHECKSTYLE: resume all
in this file?
That would be safer. Alternatively, I could attach that comment to MATH-712.
Sébastien
42 matches
Mail list logo