Hi Seb,
So long as the $Date$ ones are removed, I don't think it matters
whether the others use Revision or Id.
thanks for the feedback! since in the code on /trunk there is a mixed
use of both $Id$ and $Revision$, would it worth have a uniformed way?
TIA,
-Simo
Phil Steitz phil.ste...@gmail.com wrote:
On 7/18/12 9:35 PM, Becksfort, Jared wrote:
My employer requires that we retain copyright.
OK, that requires a patch to the (single) NOTICE.txt file in the
project root.
No it does not. The ASF does NOT require copyright assignment from
contributors.
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-exec-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-digester3 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-proxy-test has an issue affecting its community integration.
This
Hi all/Elijah,
during my current inspection I noticed some @Deprecated methods in the
web module - since we are jumping to a major release, it would be good
IMHO dropping them
WDYT? do you have a cycle to dedicate?
TIA,
-Simo
http://people.apache.org/~simonetripodi/
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
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-jmx has an issue affecting its community integration.
very good, I was waiting for you! :)
two minor observations:
* we usually mark resolved issue with [FUNCTOR-XX] rather than FIXED
FUNCTOR-XX - not a big deal, but feel free to modify the log message;
* can you please track the issue in the src/main/changes.xml file?
many thanks in advance,
On Jul 18, 2012, at 10:38 AM, sebb wrote:
Can the above be read as follows for VFS and JCIFS: you cannot copy the
JCIFS jar into VFS (which we do not) but the VFS POM can point to it (which
we do).
The above document is only proposed, not actual policy.
The following is the resolved
Hi.
Is there any issue of maintaining compatibility when changing code that is
in the test subtree of the code repository?
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
Hi Simo!
two minor observations:
* we usually mark resolved issue with [FUNCTOR-XX] rather than FIXED
FUNCTOR-XX - not a big deal, but feel free to modify the log message;
Thanks for the heads up! I've updated the log message and will try to remember
this in the next time.
* can you please
On 19/07/2012 20:06, Gilles Sadowski wrote:
Hi.
Is there any issue of maintaining compatibility when changing code that is
in the test subtree of the code repository?
No problems for such changes.
Luc
Gilles
-
To
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-logging-test has an issue affecting its community integration.
On 19 July 2012 07:54, Simone Tripodi simonetrip...@apache.org wrote:
Hi Seb,
So long as the $Date$ ones are removed, I don't think it matters
whether the others use Revision or Id.
thanks for the feedback! since in the code on /trunk there is a mixed
use of both $Id$ and $Revision$, would
On 19 July 2012 19:09, Bruno P. Kinoshita brunodepau...@yahoo.com.br wrote:
Hi Simo!
two minor observations:
* we usually mark resolved issue with [FUNCTOR-XX] rather than FIXED
FUNCTOR-XX - not a big deal, but feel free to modify the log message;
Thanks for the heads up! I've updated the log
On 7/19/12 11:41 AM, Luc Maisonobe wrote:
On 19/07/2012 20:06, Gilles Sadowski wrote:
Hi.
Is there any issue of maintaining compatibility when changing code that is
in the test subtree of the code repository?
No problems for such changes.
Right. The only thing to ever worry about there is
On 19 July 2012 21:26, Phil Steitz phil.ste...@gmail.com wrote:
On 7/19/12 11:41 AM, Luc Maisonobe wrote:
On 19/07/2012 20:06, Gilles Sadowski wrote:
Hi.
Is there any issue of maintaining compatibility when changing code that is
in the test subtree of the code repository?
No problems for
Hi Sebb!
Also it may be worth adding the commit message header to the JIRA
issue when resolving it.
This used to be done by a JIRA plugin but that broke when JIRA was
upgraded recently.
Hmm, that's true indeed. In the Jenkins project, when you include the issue
number in your commit, the
Hi all,
In [functor], the class
org.apache.commons.functor.core.comparator.ComparableComparator [1] is used by
some functors and, as the name says, is a comparator of comparables. I was
reviewing the raw types in [functor] tests when I stumbled across this class,
and noticed it hasn't been
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=24010projectId=97
Build statistics:
State: Failed
Previous State: Ok
Started at: Thu 19 Jul 2012 22:20:46 +
Finished at: Thu 19 Jul 2012 22:26:37 +
Total time: 5m 50s
Build Trigger: Schedule
Hi Simo,
I've already partly investigated some of those methods. Some of them
are still used by the chain code, so I didn't just go ahead and delete
them. I believe they should be their own ticket. I would like to do it
in a 2.0.1 release. I want to get the new functionality proven and
burned in
Then again on the other hand, keeping deprecated APIs across major
releases is not good. I'm very much undecided about this.
-Elijah
On Thu, Jul 19, 2012 at 4:27 PM, Elijah Zupancic eli...@apache.org wrote:
Hi Simo,
I've already partly investigated some of those methods. Some of them
are
On Jul 19, 2012, at 15:38, sebb seb...@gmail.com wrote:
On 19 July 2012 07:54, Simone Tripodi simonetrip...@apache.org wrote:
Hi Seb,
So long as the $Date$ ones are removed, I don't think it matters
whether the others use Revision or Id.
thanks for the feedback! since in the code on /trunk
On Wed, Jul 18, 2012 at 11:05:28PM +0200, Gilles Sadowski wrote:
Hi.
Cf. issues 764 and 823.
What would be the preferred class to be used as the RNG in a
distribution's default constructor?
I somewhat arbitrarily chose Well19937c.
Please open a JIRA if this is to be changed.
Gilles
On Mon, Jul 16, 2012 at 04:39:41PM -0700, Phil Steitz wrote:
On 7/16/12 2:46 PM, Gilles Sadowski wrote:
Hi.
Referring to the discussion here:
https://issues.apache.org/jira/browse/MATH-764
https://issues.apache.org/jira/browse/MATH-823
Those issues have been resolved in revision
One thing that should be considered is how a deterministic seed can be
injected during testing to make tests deterministic.
Mahout does this by providing a static method that returns a standard PRNG.
During tests, that PRNG is seeded by a constant. During normal operation,
the PRNG is seeded
On 7/19/12 7:16 PM, Ted Dunning wrote:
One thing that should be considered is how a deterministic seed can be
injected during testing to make tests deterministic.
That is one reason to keep the reseed method that exists now. That
method provides a seed to the underlying PRNG. The default
28 matches
Mail list logo
