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 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
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
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
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
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
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
Gilles Sadowski wrote:
>If you do find it ridiculous, it is indeed only because of habit;
>others
>might be used to (and thus prefer)
>
> y
> - x
Personally, I find:
a = y -
x;
easier to read than:
a = y
- x;
In the former I tend to miss that there isn't a ';' at the end of the line and
Thomas Neidhart wrote:
>On 09/14/2012 05:23 PM, Gary Gregory wrote:
>> Who is that then:
>
>I do not know what you mean, I just wanted to point out that I am not a
>PMC member, thus my vote should not be counted as such to avoid any
>confusion in the future.
>
>Thomas
>
>> On Fri, Sep 14, 2012 at
On 15/09/2012 18:43, Gary Gregory wrote:
> There were 3 PMC +1 in addition to Thomas', so we are good.
Cool. I thought it was odd the RM wasn't in the list. I didn't realise
Thomas snipped the remaining vote.
I assume you looked at the commons list rather than the commons-pms list.
Mark
--
On 04/10/2012 14:12, Gary Gregory wrote:
> Who do we push this to? Apache Infra or Altassian directly?
Jira was being restarted when you saw this. It works for me now. And in
future infra in the first instance but check the twitter feed and
monitoring.a.o for known issues / maintenance first.
Mar
On 14/10/2012 20:45, Paul Libbrecht wrote:
> Gary,
>
> please read commons-dev netiquette. You definitely need to express
> the sub-project name.
>
> paul
>
>
> Le 14 oct. 2012 à 05:32, Gary Lucas a écrit :
>
>> Damjan,
>>
>> I just submitted a new Tracker Item, #93, and a patch.
>> Unfortuna
On 08/11/2012 11:59, Emmanuel Bourg wrote:
> Le 08/11/2012 12:53, Emmanuel Bourg a écrit :
>
>> I don't think it's necessary to bug the Infra for this, we can configure
>> it ourself.
>
> I'm pretty sure I have been able to do that once, but I can't find how
> to do it now. So let's ask to the In
On 26/11/2012 17:23, sebb wrote:
> On 26 November 2012 17:01, Ralph Goers wrote:
>> Actually, if you use the Release plugin the artifacts will be uploaded to
>> the staging repository. At least that is what VFS does. They can be voted
>> on there and then checked into SVN. You can easily verif
On 04/12/2012 22:54, Matt Benson wrote:
> Well, it looks like the most comfortable avenue for everyone is Commons
> [weaver]. IMO [weaver] would look like a framework for implementing any
> kind of code weaving, so the most important decision is the look of the
> API, and it would seem that eating
On 10/01/2013 16:21, Gary Gregory wrote:
> Should this be ported to the 1.6 branch?
Don't think so. That looks to be specific to pool2.
Mark
>
> Gary
>
>
> On Sat, Dec 29, 2012 at 1:23 PM, wrote:
>
>> Author: psteitz
>> Date: Sat Dec 29 18:23:33 2012
>> New Revision: 1426799
>>
>> URL: htt
On 10/01/2013 17:36, Continuum@vmbuild wrote:
> Default Maven 2 Build Definition (Java 1.7)
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> X-Continuum-Build-Host: vmbuild
> X-Continuum-Project-Id: 73
> X-Continuum-Project-Name: Commons
Phil Steitz wrote:
>On 1/10/13 8:57 AM, ma...@apache.org wrote:
>> Author: markt
>> Date: Thu Jan 10 16:57:07 2013
>> New Revision: 1431496
>>
>> URL: http://svn.apache.org/viewvc?rev=1431496&view=rev
>> Log:
>> Update DBCP2 to require JDBC 4.1 (Java 7) since Java 6 is close to
>end of life and
On 11/01/2013 11:31, sebb wrote:
> On 11 January 2013 02:38, Phil Steitz wrote:
>> On 1/10/13 8:57 AM, ma...@apache.org wrote:
>>> Author: markt
>>> Date: Thu Jan 10 16:57:07 2013
>>> New Revision: 1431496
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1431496&view=rev
>>> Log:
>>> Update DBCP2 to
On 12/01/2013 17:36, Christian Grobmeier wrote:
> Basically I am +1 on moving to newer JDKs. But in this case I just see
> use for old and older applications.
> That said, I just checked and saw tomcat is still using commons-logging:
> http://svn.apache.org/repos/asf/tomcat/trunk/build.xml
>
> Ma
On 12/01/2013 19:29, Christian Grobmeier wrote:
> On Sat, Jan 12, 2013 at 8:27 PM, Mark Thomas wrote:
>> On 12/01/2013 17:36, Christian Grobmeier wrote:
>>
>>> Basically I am +1 on moving to newer JDKs. But in this case I just see
>>> use for old and older ap
On 29/01/2013 13:11, ma...@apache.org wrote:
> Author: markt
> Date: Tue Jan 29 13:11:04 2013
> New Revision: 1439882
>
> URL: http://svn.apache.org/viewvc?rev=1439882&view=rev
> Log:
> First pass at getting DBCP to compile with Java 7 to keep Gump happy. Whether
> or not we create a DBCP_1.5 bra
On 31/01/2013 09:29, Continuum@vmbuild wrote:
> Default Ant Build Definition
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> X-Continuum-Build-Host: vmbuild
> X-Continuum-Project-Id: 283
> X-Continuum-Project-Name: Commons DBCP 1.4.x
>
On 31/01/2013 09:52, sebb wrote:
> On 31 January 2013 09:33, Mark Thomas wrote:
>> On 31/01/2013 09:29, Continuum@vmbuild wrote:
>>> Default Ant Build Definition
>>> MIME-Version: 1.0
>>> Content-Type: text/plain; charset=us-ascii
>>> Co
On 31/01/2013 12:12, sebb wrote:
> On 31 January 2013 10:54, Mark Thomas wrote:
>> I've seen some strangeness. I'll keep an eye on it.
>
> BTW, there are two indentical DBCP2 builds - one uses
> COMMONS_SCHEDULE, the other DEFAULT_SCHEDULE.
> The latter should pr
On 10/08/2020 17:26, Gary Gregory wrote:
> As recently done for [EMAIL], I propose we update [LOGGING] and [DAEMON]
> from Java 6 to 7 to streamline building on CIs.
-1 for DAEMON. Tomcat 7 depends on it and has a specification mandated
requirement to run on Java 6.
Are there any features / bugs
Hi,
I am seeing an awful lot of list traffic generated for patch updates to
github actions e.g. updating from v1.4.0 to v1.4.1
Having read [1], my understanding is that we can specify v1 and that
will always point to the latest 1.x.x release.
Would it not be better to specify v1 for these action
On 15/08/2020 19:00, Gary Gregory wrote:
> On Sat, Aug 15, 2020 at 1:14 PM Mark Thomas wrote:
>
>> On 10/08/2020 17:26, Gary Gregory wrote:
>>> As recently done for [EMAIL], I propose we update [LOGGING] and [DAEMON]
>>> from Java 6 to 7 to streamline building on CI
grades happen. The option is there for components that want to use it.
> Mailing list volume is a different topic.
Indeed.
Mark
>
> Gary
>
> On Sun, Aug 16, 2020, 05:55 Mark Thomas wrote:
>
>> Hi,
>>
>> I am seeing an awful lot of list traffic generated
his thread, Tomcat needs a version that compiles on
>> Java 6
>>
>>> 3. if no users argue about this, we just go forward to 7. Otherwise, we
>>> re-consider about this.
>>
>>
>>>
>>> Mark Thomas 于 2020年8月16日周日 下午6:08写道：
>>>
there is therefore no need to change the minimum version merely
>> to make CI easier.
>>
>> On Sun, 16 Aug 2020 at 16:05, Mark Thomas wrote:
>>>
>>> On 16/08/2020 15:45, sebb wrote:
>>>> I've pushed change to the pom which allows compila
Hi all,
It is about time we had another DAEMON release. I'd like to tag and get
the process started in the next day or so.
If there is anything you'd like to get done before the DAEMON 1.2.3
release, now is the time to do it.
Mark
On 27/08/2020 00:21, Gilles Sadowski wrote:
> Hi.
>
> Something happening recently (apparently unrelated to changes
> in the repository):
> https://ci-builds.apache.org/job/Commons/job/commons-statistics/3/console
> https://ci-builds.apache.org/job/Commons/job/commons-numbers/2/console
> htt
Apologies for the slight delay between the tag and the vote. There was
an issue with the code signing service we use to sign the Windows binaries.
It has been almost a year since the last Commons Daemon release. Notable
changes since 1.2.2 include:
- Improved debug logging for error conditions
- A
On 01/09/2020 19:25, Mark Thomas wrote:
> [X] Approved - go ahead and release Commons Daemon 1.2.3 RC1 as 1.2.3
Tested with Apache Tomcat.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additio
On 31/08/2020 01:05, Phil Steitz wrote:
> If others agree it is a good idea for dbcp, I can do it. I can see the
> argument that its better to stay with close() even for abandoned and I
> have not been able to get the deadlock to happen, so I would like to
> wait a bit and allow others to weigh
to hash the files twice on
> https://dist.apache.org/repos/dist/dev/commons/daemon/)
See previous Commons Daemon release vote threads for why I won't be
doing that.
Mark
>
> Thank you,
> Gary
>
> On Tue, Sep 1, 2020 at 2:25 PM Mark Thomas wrote:
>
>> Apo
On 03/09/2020 15:37, Gary Gregory wrote:
> On Thu, Sep 3, 2020 at 10:17 AM Mark Thomas wrote:
>
>> On 03/09/2020 14:06, Gary Gregory wrote:
>>> Mark,
>>>
>>> The vote email must contain SHA256 or 512 hashes for the file bin and gz
>>> files i
ovided in
the vote email. Isn't it?
Generating the list the artefacts and their hashes for the vote mail
takes time I would rather be spending fixing other issues.
Mark
>
> Cheers,
> -Rob
>
>> On Sep 1, 2020, at 2:25 PM, Mark Thomas wrote:
>>
>> Apologies for the
On 07/09/2020 15:40, Rob Tompkins wrote:
> Also, I would think we should be as accommodating as possible to Mark as he
> is indeed the top maintainer on [daemon]. I doubt we’d be making progress
> there with out him.
>
> I’ve found his [VOTE] threads to be entirely sufficient for validation
>
On 07/09/2020 15:26, sebb wrote:
> Suppose we take the following example:
>
> https://lists.apache.org/thread.html/c99519e1c8e0a4af5be02f40e8e44b408cbc3d4568a334f3a400b94f%40%3Cdev.commons.apache.org%3E
>
> This is Commons Daemon 1.2.0 based on RC2.
>
> Take for example:
>
> https://archive.apa
On 07/09/2020 18:18, sebb wrote:
> Such automation already exists, and is used to generate the VOTE
> emails used by many Commons RMs
>
> $ mvn commons-release:vote-txt
Thanks for that.
I tried it out on the 1.2.3-RC1 release directory and it looks like it
depends on various naming convention
On 09/09/2020 09:47, ma...@apache.org wrote:
> Author: markt
> Date: Wed Sep 9 08:47:17 2020
> New Revision: 41370
>
> Log:
> In an effort to unblock the Commons Daemon release, create a copy of the
> release artefacts in the location expected by the release plugin for the
> automatic generatio
On 09/09/2020 09:59, Mark Thomas wrote:
> On 09/09/2020 09:47, ma...@apache.org wrote:
>> Author: markt
>> Date: Wed Sep 9 08:47:17 2020
>> New Revision: 41370
>>
>> Log:
>> In an effort to unblock the Commons Daemon release, create a copy of the
>>
1 - 100 of 828 matches
Mail list logo
