I understand the use case.
But starting with JDK 7, java.lang.Throwable has
Throwable#addSuppressed(Throwable)
Throwable[] getSuppressed()
which would lend themselves pretty obviously to the purpose, at least if
the mechanism hasn't been disabled using the special ctor
protected Throwabl
ree to duplicate the JSR-305 annotations into the jakarta Namespace.
- Or rolling our own.
I would be in favor of the second option, as this would be easier to
control for commons. Maybe it is finally time to start modules
'annotation' and/or 'annotation-processing' within the co
mples module should produce and release kind
of a source artifact, containing the *complete* source (with pom,
src/main/** etc), or if we point the users simply to the version
control URL, where they might check it out.
Regards,
Thomas
On 09.08.2021 13:22, Matt Juntunen wrote:
Advertisin
On 11.04.2022 00:00, Ralph Goers wrote:
See below
On Apr 8, 2022, at 9:23 AM, Peter Verhas wrote:
Thanks Ralph for the detailed explanation. I appreciate it and now I see
the points.
I’ve removed the parts that I don’t think need any more discussion.
- How will it be a “plugin" project an
that enables us to
swap out say, CDI for Spring or OSGi. Don't tempt me to cite XKCD 927 on
you!
Cheers, Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Maybe start small, with a universally usable prerequisite:
something like commons-unit as an implementation of javax.measure.
See:
https://unitsofmeasurement.github.io/unit-api/site/apidocs/javax/measure/class-use/Unit.html
| javax.measure
unit-api 1.0
Even if not used for physics projects,
used as an opportunity to safeguard against the
situation: by throwing another exception, if such a change was detected.
Having choice, you still have the possibility to reuse code, without
giving up control, and inadvertently hiding problems.
Just my thoughts.
Thomas
On 2023/12/03 12:2
On 01/05/2019 21:38, Eric Barnhill wrote:
> Actually some objections have been raised to using Slack because it is not
> open source. So the options will be either zulipchat if a group of people
> want to use it, or Riot if it is just me.
Better stop using GitHub as well then.
There is no ASF pol
On 01/05/2019 21:48, Gary Gregory wrote:
> On Wed, May 1, 2019 at 3:54 PM Gary Gregory wrote:
>
>> I created https://issues.apache.org/jira/browse/INFRA-18316
>>
>
> And the work is done. Note that open PRs on trunk have been closed
> automatically, so they would need to be re-opened.
Note that
On 01/05/2019 21:54, Eric Barnhill wrote:
> On Wed, May 1, 2019 at 1:49 PM Mark Thomas wrote:
>
>> On 01/05/2019 21:38, Eric Barnhill wrote:
>>> Actually some objections have been raised to using Slack because it is
>> not
>>> open source. So the options wi
there
> though!
You should be able to invite folks without @apache.org addresses
Mark
>
> Eric
>
> On Wed, May 1, 2019 at 1:58 PM Mark Thomas wrote:
>
>> On 01/05/2019 21:54, Eric Barnhill wrote:
>>> On Wed, May 1, 2019 at 1:49 PM Mark Thomas wro
On 03/05/2019 13:59, Gary Gregory wrote:
> Hi Mark and All:
>
> I've seen a lot of commits lately in Daemon from Mark T.
>
> Are you planning a release?
I am starting to think in that direction. There are still a handful of
Jira issues I want to look at first.
Given past experience with the Com
On 03/05/2019 14:20, Rob Tompkins wrote:
>> On May 3, 2019, at 9:18 AM, Mark Thomas wrote:
>>
>>> On 03/05/2019 13:59, Gary Gregory wrote:
>>> Hi Mark and All:
>>>
>>> I've seen a lot of commits lately in Daemon from Mark T.
>>>
>&g
On 24.05.19 12:33, Gary Gregory wrote:
> -1
>
> We are now on gitbox https://gitbox.apache.org/repos/asf/commons-jcs.git
>
When did that happen? I don't remember an announcement or a vote.
Bye, Thomas
-
On 26.05.19 15:54, sebb wrote:
> Jan 2019
>
> https://lists.apache.org/thread.html/053bb8f18e90800d918956f69364167b23c0cdca175568300b1108f6@%3Cdev.commons.apache.org%3E
Ok, I missed that one completely.
What do I have to do?
By
On 27.05.19 10:21, sebb wrote:
> Either re-apply each of the commits in turn to Git.
Done.
Bye, Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On 12/06/2019 14:09, Gary Gregory wrote:
> Hi All:
>
> I am pleased to see renewed activity in Commons Daemon.
>
> Are there any release thoughts?
https://commons.markmail.org/thread/qklsh7jg3qwo2uf3
Mark
-
To unsubscribe, e-m
On 12/06/2019 14:23, Mark Thomas wrote:
> On 12/06/2019 14:09, Gary Gregory wrote:
>> Hi All:
>>
>> I am pleased to see renewed activity in Commons Daemon.
>>
>> Are there any release thoughts?
>
> https://commons.markmail.org/thread/qklsh7jg3qwo2uf3
I
ago that needs a review.
>>
>> Gary
>>
>> On Fri, Jun 14, 2019, 12:34 Mark Thomas wrote:
>>
>>> On 12/06/2019 14:23, Mark Thomas wrote:
>>>> On 12/06/2019 14:09, Gary Gregory wrote:
>>>>> Hi All:
>>>>>
>>>>
On 14/06/2019 20:39, Gary Gregory wrote:
> On Fri, Jun 14, 2019 at 3:36 PM Mark Thomas wrote:
>
>> On 14/06/2019 20:31, Gary Gregory wrote:
>>> This one: https://github.com/apache/commons-daemon/pull/11
>>
>> Review for what? Looks pretty uncontroversial to me.
&
On 14/06/2019 20:43, Mark Thomas wrote:
> On 14/06/2019 20:39, Gary Gregory wrote:
>> On Fri, Jun 14, 2019 at 3:36 PM Mark Thomas wrote:
>>
>>> On 14/06/2019 20:31, Gary Gregory wrote:
>>>> This one: https://github.com/apache/commons-daemon/pull/11
&
It has been ~18 months since the last Commons Daemon release. After the
recent flurry of activity, I think we are ready for a release.
Notable changes include:
- Improved JRE/JDK detection to support increased range of both JVM
versions and vendors.
- Procrun. Change the default service from Loc
1.2 would be more appropriate since we upgraded both
> the Java and OS requirements.
No we didn't. See the changelog. The Java and OS requirements are the
same for 1.1.1 as they are for 1.1.0.
Mark
>
> Gary
>
> On Mon, Jun 17, 2019, 08:13 Mark Thomas wrote:
>
>> It
r 1.1.1 on the grounds the older OSes
are unsupported but using 1.2.0 makes it cleaner.
The changes from the 1.1.1 tag to 1.2.0 are essentially cosmetic so far
so I'd urge folks to continue to test 1.1.1 and provide feedback.
Mark
>
> Gary
>
> On Mon, Jun 17, 2019 at 8:13 AM M
On 18/06/2019 17:15, Gary Gregory wrote:
> On Tue, Jun 18, 2019 at 11:43 AM Mark Thomas wrote:
>
>> On 18/06/2019 14:20, Gary Gregory wrote:
>>> Also, while we even discussed PR
>>> https://github.com/apache/commons-daemon/pull/11, it was not merged fir
>>&g
on't complain if someone beats me
to it.
Mark
>
> Cheers,
> -Rob
>
>
>> On Jun 17, 2019, at 8:13 AM, Mark Thomas wrote:
>>
>> It has been ~18 months since the last Commons Daemon release. After the
>> recent flurry of activity, I think we are re
On 19/06/2019 10:44, Jonathan Gallimore wrote:
> This works well in my tests, many thanks for the release.
Thanks for the confirmation.
Mark
>
> (non-binding) +1.
>
> Jon
>
> On Mon, Jun 17, 2019 at 1:13 PM Mark Thomas wrote:
>
>> It has been ~18 months
d a commit to branch master
>> in repository https://gitbox.apache.org/repos/asf/commons-daemon.git
>>
>> commit a089ee036affef903029b481de9e9137294b0217
>> Author: Mark Thomas
>> AuthorDate: Wed Jun 19 11:46:19 2019 +0100
>>
>> Update
y objections to this plan then please speak up in the
next 24 hours.
Mark
On 17/06/2019 13:13, Mark Thomas wrote:
> It has been ~18 months since the last Commons Daemon release. After the
> recent flurry of activity, I think we are ready for a release.
>
> Notable changes include:
> -
box.a.o rather than GitHub.
I'll try and remember to do that for 1.2.0.
For a longer response, see the Daemon 1.1.0 vote thread.
Mark
>
> Gary
>
> On Wed, Jun 19, 2019 at 6:30 AM Mark Thomas wrote:
>
>> On 19/06/2019 10:44, Jonathan Gallimore wrote:
>>
It has been ~18 months since the last Commons Daemon release. After the
recent flurry of activity and a couple of failed RCs, it is time for
another release vote.
Notable changes since 1.1.0 include:
- Improved JRE/JDK detection to support increased range of both JVM
versions and vendors.
- Proc
On 28/06/2019 15:49, Gary Gregory wrote:
> +1
>
> TODO later: Update RNs since the POM uses version "1.2.0" and the release
> notes use "1.2".
That is by design. The release notes are intended for the entire 1.2.x
release stream. This is how Daemon has done it in the past.
Do we want to switch t
On 28/06/2019 15:20, Mark Thomas wrote:
> [X] Approved - go ahead and release Commons Daemon 1.2.0 RC2 as 1.2.0
> [ ] Broken - do not release because...
Tested with Tomcat 9.0.x build process and the resulting Windows installer.
There were (expected) file permission issues due to the
The following votes were cast:
Binding:
+1: ggregory, markt, chtompki, stain
Non-binding:
+1: Jonathan Gallimore
No other votes were cast.
The vote therefore passes.
Thanks to everyone who contributed to this release.
Mark
On 28/06/2019 15:20, Mark Thomas wrote:
> It has been ~18 mon
The Apache Commons Team is pleased to announce the availability of
Apache Commons Daemon 1.2.0.
The Apache Commons Daemon software library provides a generic Daemon
(unix) or Service (Windows) wrapper for Java code.
Version 1.2.0 is a feature and bugfix release.
A full list of changes can be fou
On 08/07/2019 16:14, ggreg...@apache.org wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> ggregory pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/commons-dbcp.git
>
>
> The following commit(s) were added to refs/heads/master b
On 08/07/2019 21:42, Gary Gregory wrote:
> On Mon, Jul 8, 2019 at 11:23 AM Mark Thomas wrote:
>
>> On 08/07/2019 16:14, ggreg...@apache.org wrote:
>>> This is an automated email from the ASF dual-hosted git repository.
>>>
>>> ggregory pushed a commit t
On 10/07/2019 15:49, Gary Gregory wrote:
> Without arguing about the merits of one kind of formatting vs. another...
> If you can configure the Eclipse formatter to do that, I'd consider it,
> otherwise, I'm not into what I'd call "artisanal formatting" ;-)
The Eclipse setting you want is:
Form
On 10/07/2019 22:47, Gary Gregory wrote:
> On Wed, Jul 10, 2019 at 11:52 AM Mark Thomas wrote:
>
>> On 10/07/2019 15:49, Gary Gregory wrote:
>>
>>> Without arguing about the merits of one kind of formatting vs. another...
>>> If you can configure the Eclipse f
added to refs/heads/master by this push:
>> new 4228b53 Correct regression in DAEMON-401
>> 4228b53 is described below
>>
>> commit 4228b53ec99ae4e7f1d96242fbc8d4a27316fd57
>> Author: Mark Thomas
>> AuthorDate: Tue Sep 3 22:30:37 2019 +0100
>>
>>
A couple of regressions have been identified in the 1.2.0 release so I'd
like to get 1.2.1 released to address them. So, time for another release
vote.
Notable changes since 1.2.0 include:
- Correct a regression (DAEMON-401) that caused 32-bit Windows services
to crash on start-up
- Correct a re
On 05/09/2019 21:39, Mark Thomas wrote:
> [X] Approved - go ahead and release Commons Daemon 1.2.1 RC1 as 1.2.1
> [ ] Broken - do not release because...
Tested with a release build of Tomcat 9.0.x - all good.
I did notice that the about box for prunmgr uses the old Commons logo.
I&
On 06/09/2019 13:05, Gilles Sadowski wrote:
> Hi.
>
> Le ven. 6 sept. 2019 à 12:17, Mark Thomas a écrit :
>>
>> On 05/09/2019 21:39, Mark Thomas wrote:
>>
>>
>>
>>> [X] Approved - go ahead and release Commons Daemon 1.2.1 RC1 as 1.2.1
>>&
On 06/09/2019 14:07, Gilles Sadowski wrote:
> Hi.
>
> Le ven. 6 sept. 2019 à 14:49, Mark Thomas a écrit :
>>
>> On 06/09/2019 13:05, Gilles Sadowski wrote:
>>> Hi.
>>>
>>> Le ven. 6 sept. 2019 à 12:17, Mark Thomas a écrit :
Hi all,
I've looked but can't find a previous vote on this.
The current logo is:
https://apache.org/foundation/press/kit/ApacheFoundation_StyleGuide.pdf
The options for the new logo are:
https://issues.apache.org/jira/browse/COMMONSSITE-86
Of those, commons_logo.small.png is not consistent wit
ssworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
> at
>org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
> at
>org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
> at java.lang.Class.getDeclaredConstr
On September 7, 2019 1:25:41 AM UTC, Gilles Sadowski
wrote:
>2019-09-06 16:53 UTC+02:00, Mark Thomas :
>> Hi all,
>>
>> I've looked but can't find a previous vote on this.
>>
>> The current logo is:
>>
>https://apache.org/foundation/press/kit/A
The following votes were cast:
Binding:
+1: markt, kinow, chtompki, ggregory
No other votes were cast.
The vote therefore passes.
Thanks to everyone who contributed to this release.
Mark
On 05/09/2019 21:39, Mark Thomas wrote:
> A couple of regressions have been identified in the 1.
The Apache Commons Team is pleased to announce the availability of
Apache Commons Daemon 1.2.1.
The Apache Commons Daemon software library provides a generic Daemon
(unix) or Service (Windows) wrapper for Java code.
Version 1.2.1 is a bugfix release.
A full list of changes can be found at
http
ing to use the "{ on the same line" which means that
> blocks go from:
>
> if (test)
> {
>// this
> }
> else
> {
> // that
> }
>
> to:
>
> if (test) {
>// this
>
On 25/09/2019 12:34, ma...@apache.org wrote:
> Fix https://issues.apache.org/jira/browse/DAEMON-408 Procrun start fail
>
> Correct a regression in the fix for DAEMON-401 that prevented the
> service from starting unless support for the universal C runtime had
> been installe
A further regression has been identified in the 1.2.0/1.2.1 releases so
I'd like to get 1.2.2 released to address it. So, time for another
release vote.
Notable changes since 1.2.1 include:
- Correct a regression (DAEMON-408) that caused Windows services to
crash on start-up when the universal C
On 25/09/2019 15:57, Mark Thomas wrote:
> [X] Approved - go ahead and release Commons Daemon 1.2.2 RC1 as 1.2.2
Tested a Tomcat 9.0.26 install that failed to start with 1.2.1 and it
starts cleanly with 1.2.2
Also double-checked that the configure script was in place.
M
On 28/09/2019 17:06, Gary Gregory wrote:
> On Sat, Sep 28, 2019 at 12:04 PM Gary Gregory
> wrote:
>
>> I can confirm that if I delete all of:
>>
>> src\native\windows\apps\prunmgr\WINXP_X86_GUI_RELEASE
>> src\native\windows\apps\prunsrv\WINXP_X86_EXE_RELEASE
>> src\native\windows\apps\prunsrv\WIN
On 29/09/2019 23:15, Gary Gregory wrote:
> On Sun, Sep 29, 2019 at 6:04 PM sebb wrote:
>
>> On Sun, 29 Sep 2019 at 22:36, Matt Sicker wrote:
>>>
>>> I’m sort of going off of what GNU projects do (they use autotools for
>> any C
>>> projects), but the common ‘./configure && make && sudo make inst
On 28/09/2019 17:42, Mark Thomas wrote:
> On 28/09/2019 17:06, Gary Gregory wrote:
>> On Sat, Sep 28, 2019 at 12:04 PM Gary Gregory
>> wrote:
>>> I can build without errors but with warnings:
>>>
>>> .\..\..\apps\prunsrv\prunsrv.c(323): warning C4996
I am cancelling this vote due to the presence of Windows build artefacts
in RC1.
RC2 should follow shortly.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apa
A further regression has been identified in the 1.2.0/1.2.1 releases so
I'd like to get 1.2.2 released to address it. So, time for another
release vote.
Notable changes since 1.2.1 include:
- Correct a regression (DAEMON-408) that caused Windows services to
crash on start-up when the universal C
On 30/09/2019 21:09, Gary Gregory wrote:
> Hi Mark,
>
> I know you said you fixed a bunch of warnings but I still warning get these
> using CPU=X64; I had only tested CPU=X86 previously (sorry):
No problem. I think you hit upon I configuration I've never tested.
> C:\Program Files (x86)\Windows
On 30/09/2019 17:04, Mark Thomas wrote:
> [X] Approved - go ahead and release Commons Daemon 1.2.2 RC2 as 1.2.2
> [ ] Broken - do not release because...
I've checked the contents of the src distros against the 1.2.1 release.
That identified no missing files in 1.2.2 but a few
The following votes were cast:
Binding:
+1: ggregory, markt, chtompki
The vote therefore passes.
Thanks to everyone who contributed to this release.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additio
On 05/10/2019 18:59, Gary Gregory wrote:
> On Sat, Oct 5, 2019 at 1:19 PM Phil Steitz wrote:
>
>>
>> On 10/5/19 5:47 AM, Gary Gregory wrote:
>>> On Sat, Oct 5, 2019 at 8:17 AM sebb wrote:
>>>
On Sat, 5 Oct 2019 at 02:32, Gary Gregory
>> wrote:
> Hi Phil and all:
>
> It looks li
The Apache Commons Team is pleased to announce the availability of
Apache Commons Daemon 1.2.2.
The Apache Commons Daemon software library provides a generic Daemon
(unix) or Service (Windows) wrapper for Java code.
Version 1.2.2 is a bugfix release.
A full list of changes can be found at
http
On 22/11/2019 18:11, Gary Gregory wrote:
> On Fri, Nov 22, 2019 at 12:29 PM Mark Thomas wrote:
>
>> On 21/11/2019 19:29, ggreg...@apache.org wrote:
>>> This is an automated email from the ASF dual-hosted git repository.
>>>
>>> ggregory pushed a commit t
if somebody with an interest in this topic
could take a look and provide feedback.
Thanks & Regards,
Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On 13/06/2020 05:06, Miguel Munoz wrote:
> When I send an email to this list, my email address shows up in the archive
> as ending with .INVALID. Is there anything I can do about this? (I submitted
> an ICLA, so that shouldn't be the problem.)
https://blogs.apache.org/infra/entry/dmarc_filtering
On 13/07/2020 06:43, Stefan Bodewig wrote:
> On 2020-07-12, Rob Tompkins wrote:
>
>> given the consistency of the signatures from the plugins…do we need to
>> check them for releases anymore?
>
> Yes, please. Not everybody uses the plugins and even if everybody did a
> misconfiguration could be p
works in principle, you can understand all others. This is
one of the greatest strengths of Maven IMO.
> With respect to this project, it is my opinion that we do not want to
> create a build system that is so complex that it becomes
On 22/07/2012 22:41, Phil Steitz wrote:
> One more quick question as I begin hacking:
>
> Currently, abandoned object recuperation is triggered by
> borrowObject in AOP. I am thinking about moving this to the
> evictor. Or I guess it could be in both places?
The third option is a separate thre
On 24/07/2012 08:42, Liviu Tudor wrote:
> Phil & others who have been in touch with [pool],
>
> A follow up to this: I'm trying to log this in JIRA and submit a patch but
> I've come across the following problem:
>
> 1/ The mechanism I am referring to had pool-1.6.0 in mind, however, I
> can't fi
>> svn:eol-style = native
>>
>> Propchange:
>> commons/proper/collections/trunk/src/test/resources/org/apache/commons/collections/trie/hamlet.txt
>> --
>> svn:executable = *
>
Hi,
is there a way to disable the hudson integration with jira?
Is is just annoying and confusing if build failure comments pop up in
completely unrelated issues.
Thanks,
Thomas
-
To unsubscribe, e-mail: dev-unsubscr
On 07/26/2012 11:41 PM, sebb wrote:
> On 26 July 2012 21:27, Thomas Neidhart wrote:
>> Hi,
>>
>> is there a way to disable the hudson integration with jira?
>
> Try asking on the bui...@apache.org list.
Thanks, b
On 07/27/2012 08:33 PM, sebb wrote:
> On 27 July 2012 19:17, Thomas Neidhart wrote:
>> On 07/26/2012 11:41 PM, sebb wrote:
>>> On 26 July 2012 21:27, Thomas Neidhart wrote:
>>>> Hi,
>>>>
>>>> is there a way to disable the hudson integration
On 07/27/2012 09:17 PM, sebb wrote:
> On 27 July 2012 20:02, Thomas Neidhart wrote:
>> On 07/27/2012 08:33 PM, sebb wrote:
>>> On 27 July 2012 19:17, Thomas Neidhart wrote:
>>>> On 07/26/2012 11:41 PM, sebb wrote:
>>>>> On 26 July 2012 21:27, Thomas
On 30/07/2012 09:36, Liviu Tudor wrote:
> Thanks very much for pointing me in the right direction, Mark!
> As with all development tasks, this, however, opened up new questions --
> not entirely sure if these are best discussed on this list or whether
> occasionally I should open up a JIRA ticket f
On 30/07/2012 21:07, Liviu Tudor wrote:
> * Findbugs: indeed, some of the findbugs warnings are not entirely correct
> -- and we should probably look at using the Findbugs annotations to
> manually annotate the ones which we know to actually be false alarms?
> There were also a couple related to pe
On 30/07/2012 22:04, Gary Gregory wrote:
> Hi All:
>
> I wonder if this change:
>
> POOL-212. If minIdle > maxIdle use maxIdle in place of minIdle (rev 1325476
> by markt)
>
> broke the 4 tests below.
>
> Could the change be bogus or the tests need to be adjusted.
As per my previous message, t
On 30/07/2012 22:33, Gary Gregory wrote:
> On Mon, Jul 30, 2012 at 5:21 PM, Liviu Tudor wrote:
>
>> Mark/Gary/Seb,
>>
>> Just to clarify this: I haven't touched at all the 1.5 branch -- all of
>> these refer strictly to the 1.6 branch (which uses JDK 1.5 according to
>> the pom and also uses Juni
Hi Tommaso,
you may want to take a look at commons-collections, which now has a Trie
implementation (see https://issues.apache.org/jira/browse/COLLECTIONS-225).
The code can be found here
http://svn.apache.org/viewvc/commons/proper/collections/trunk/
Any feedback, help is welcome!
Thomas
On
t; Closure> resultClosure =
>> CollectionUtils.forAllDo(col.iterator(), testClosure);
>> assertSame(testClosure, resultClosure);
>> assertTrue(collectionA.isEmpty() && collectionB
oLargeException: lower
bound (65) must be strictly less than upper bound (65)
at
org.apache.commons.math3.distribution.UniformIntegerDistribution.(UniformIntegerDistribution.java:73)
at
org.apache.commons.math3.distribution.UniformIntegerDistribution.(UniformIntegerDistribution.java:53)
at
org.apache.commons.m
ed by
> you, or where you took an active part in the discussion) and provide
> feedback on their "currentness".
see above.
Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
t; clutter!
>
> Can we stop Checkstyle complaining about it and revert these lines again?
If you have a better solution, I am really willing to include it.
My suggestion to go for java 6 source compatibility to be able to use
@Override tags was so far objected.
Thomas
On Tue, Aug 7, 2012 at 10:24 AM, Jörg Schaible
wrote:
> Hi Thomas,
>
> Thomas Neidhart wrote:
>
> > On 08/06/2012 10:00 PM, Jörg Schaible wrote:
> >>
> >> === %< ==
> >>
> >> Betreff: svn commit: r13
FindBugs issues
>> - Introduced carefully crafted @SuppressWarnings annotations
>
> Please add a comment to each suppression to say why it is safe to ignore.
Will do. May take some time, though.
Bye, Thomas.
-
To unsubscri
e always the
currently configured decimal separator for the expected result (as in
the RealVectorFormatTest class).
For the RealMatrix.toString, I kept the ',' as element separator for
backwards compatibility, but this will f
(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.acces
ntion the exceptions too (but I can fix that).
Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On 08/17/2012 09:15 PM, Gary Gregory wrote:
> On Fri, Aug 17, 2012 at 2:49 PM, Thomas Neidhart
> wrote:
>
>> On 08/16/2012 01:37 PM, Gary Gregory wrote:
>>> (edited message subject to add "[Codec]" prefix)
>>>
>>> Yes, there is a certain a
ess for the very same reason).
Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On 08/21/2012 03:33 PM, Gary Gregory wrote:
> On Mon, Aug 20, 2012 at 5:36 PM, Thomas Neidhart
> wrote:
>
>> On 08/20/2012 10:46 PM, Gary Gregory wrote:
>>> TN (or anyone):
>>>
>>> I get a lot of Checstyle errors "Missing a header - not enough l
On 08/22/2012 02:49 AM, Gary Gregory wrote:
> On Tue, Aug 21, 2012 at 4:50 PM, Thomas Neidhart
> wrote:
>
>> On 08/21/2012 03:33 PM, Gary Gregory wrote:
>>> On Mon, Aug 20, 2012 at 5:36 PM, Thomas Neidhart
>>> wrote:
>>>
>>>> On 08/20/
if their purpose
> > is made explicit.
> >
> OK, so for all rules, we will try to provide a reason.
>
It would be nice to have something in common for all commons (sic!)
components ;-)
It is somehow odd that one has to switch coding style when working on
different components
Thomas
ons). Atm I put FIXME
comments and commented the System.err lines out.
Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
ferences to the NSWC library is fair.
Hi Sebastien,
I have looked briefly at the code so far, but apart from a very minor
thing (static final double HALF_LOG_2_PI is not used anymore), it looks
pretty good imho.
Great work!
Thomas
---
On 22/08/2012 13:51, Phil Steitz wrote:
> Any feedback on the patch? Should I go ahead and apply the [pool]
> patch?
Sorry for the very late review. Some comments/questions on the pool2
part (I haven't looked at DBCP):
- Why not add abandoned support to GKOP as well as GOP?
- I wasn't convinced
On 24/08/2012 16:22, Phil Steitz wrote:
> On 8/24/12 7:42 AM, Mark Thomas wrote:
>> On 22/08/2012 13:51, Phil Steitz wrote:
>>> Any feedback on the patch? Should I go ahead and apply the [pool]
>>> patch?
>> Sorry for the very late review. Some comments/question
stgresql/8.4-701.jdbc3/org/postgresql/util/UnixCrypt.java
http://grepcode.com/file/repo1.maven.org/maven2/org.mortbay.jetty/jetty/6.1.11/org/mortbay/jetty/security/UnixCrypt.java
The jetty version looks the most clean one, and as it is also Apache
license, ma
On 08/28/2012 03:33 AM, Christian Hammers wrote:
> Am Tue, 28 Aug 2012 00:09:41 +0200
> schrieb Christian Hammers :
>
>> Hello
>>
>> Am Mon, 27 Aug 2012 16:39:23 -0400
>> schrieb Gary Gregory :
>>
>>> On Mon, Aug 27, 2012 at 2:53 PM, Thomas Nei
1 - 100 of 2013 matches
Mail list logo