Re: Lost SVN updates following conversion to Git

2019-05-24 Thread Bruno P. Kinoshita
Sounds like a good plan to me. +1 Sent from Yahoo Mail on Android On Sat, 25 May 2019 at 9:00, sebb wrote: Some updates have been made to the Commons 'proper' SVN repos since they were converted to Git. Such changes should not have been made, as they are not automatically reflected in

Re: Lost SVN updates following conversion to Git

2019-05-24 Thread sebb
On Fri, 24 May 2019 at 22:37, Emmanuel Bourg wrote: > > Le 24/05/2019 à 22:59, sebb a écrit : > > > The simplest way to stop further updates is probably to rename the SVN > > directory from /proper to /_moved_to_git. This will still allow > > updates by PMC members, but it's much more obvious

Re: Lost SVN updates following conversion to Git

2019-05-24 Thread Emmanuel Bourg
Le 24/05/2019 à 22:59, sebb a écrit : > The simplest way to stop further updates is probably to rename the SVN > directory from /proper to /_moved_to_git. This will still allow > updates by PMC members, but it's much more obvious that the SVN repo > should no longer be updated. Couldn't we set

Re: [SCXML] Are we close to ready for a 2.0 release?

2019-05-24 Thread James Carman
Guess I should have read the archives. We've already discussed this back in April. I believe the out-of-band request came from my colleague (as well as the request for an RC email today). Sounds like we actually are pretty close other than the documentation/site issues. I have encouraged my

Lost SVN updates following conversion to Git

2019-05-24 Thread sebb
Some updates have been made to the Commons 'proper' SVN repos since they were converted to Git. Such changes should not have been made, as they are not automatically reflected in the Git repos. I think we need to do the following: - revert the spurious changes so SVN reflects the state at

Re: Lost SVN updates following conversion to Git

2019-05-24 Thread sebb
On Sat, 25 May 2019 at 00:13, Gary Gregory wrote: > > I like the pointer idea. This is an example of what we did for the original moves: http://svn.apache.org/repos/asf/commons/proper/io/IoNowUsesGit.txt > Gary > > On Fri, May 24, 2019, 18:35 sebb wrote: > > > On Fri, 24 May 2019 at 22:37,

Re: Lost SVN updates following conversion to Git

2019-05-24 Thread Gary Gregory
I like the pointer idea. Gary On Fri, May 24, 2019, 18:35 sebb wrote: > On Fri, 24 May 2019 at 22:37, Emmanuel Bourg wrote: > > > > Le 24/05/2019 à 22:59, sebb a écrit : > > > > > The simplest way to stop further updates is probably to rename the SVN > > > directory from /proper to

[statitsics] .gitattributes

2019-05-24 Thread Alex Herbert
The recent PR to add a new module to statistics may have suffered from problems with converting line endings. This can be solved by having Windows users run this (optionally with --global): > git config core.autocrlf true But a better fix [1] is to add a .gitattributes file [2] containing: *

Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

2019-05-24 Thread Gary Gregory
-1 We are now on gitbox https://gitbox.apache.org/repos/asf/commons-jcs.git We have to make the old repos read only. Gary On Fri, May 24, 2019, 05:26 wrote: > Author: tv > Date: Fri May 24 09:26:50 2019 > New Revision: 1859859 > > URL: http://svn.apache.org/viewvc?rev=1859859=rev > Log: >

Re: [VOTE] Release Apache Commons Configuration 2.5 based on RC1

2019-05-24 Thread Bruno P. Kinoshita
  [x] +1 Release these artifacts Build failed on JDK 11, but passed with `mvn clean test install site` using the tag on Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-18T06:33:14+12:00) Maven home: /opt/apache-maven-3.5.4 Java version: 1.8.0_212, vendor: Oracle

Re: [IO] NullPrintStream

2019-05-24 Thread Bruno P. Kinoshita
Is it equivalent to JDK 11 Writer#nullWriter? https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/io/Writer.html#nullWriter() If so I'm -0, not a blocker, but I have on a Python project for about 1 year, catching up with the language and libraries, and lost track of JVM release

[IO] NullPrintStream

2019-05-24 Thread Gary Gregory
Hi All: We have a handy NullOutputStream. I'd like to add a convenience NullPrintStream, which would dead simple: /** * This PrintStream writes all data to the famous /dev/null. * * This print stream has no destination (file/socket etc.) and all bytes written to it are ignored and lost. *

Re: [VOTE] Release Apache Commons Configuration 2.5 based on RC1

2019-05-24 Thread Gary Gregory
On Fri, May 24, 2019 at 8:53 AM Bruno P. Kinoshita wrote: >[x] +1 Release these artifacts > > > Build failed on JDK 11, but passed with `mvn clean test install site` > using the tag on > Note that the Java 11 build passes on https://travis-ci.org/apache/commons-configuration, only Java

Re: [VOTE] Release Apache Commons Configuration 2.5 based on RC1

2019-05-24 Thread Bruno P. Kinoshita
Funny, I think I hit some wrong key when writing the command for Java 11 and did not pay attention to the message or command line, sorry. Build passing with `mvn clean test install site` with Java 11: Maven home: /opt/apache-maven-3.5.4 Java version: 11.0.2, vendor: Oracle Corporation, runtime:

Re: [IO] NullPrintStream

2019-05-24 Thread Gary Gregory
On Fri, May 24, 2019 at 9:38 AM Bruno P. Kinoshita wrote: > Is it equivalent to JDK 11 Writer#nullWriter? > > > https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/io/Writer.html#nullWriter() > > If so I'm -0, not a blocker, but I have on a Python project for about 1 > year,

Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

2019-05-24 Thread sebb
On Fri, 24 May 2019 at 11:34, Gary Gregory wrote: > > -1 > > We are now on gitbox https://gitbox.apache.org/repos/asf/commons-jcs.git > > We have to make the old repos read only. We did make commons/proper read-only for most people. However members of the Commons PMC are still allowed to update

crash in prunsrv

2019-05-24 Thread Lode Leroy
Hi, I see frequent crashes in prunsrv.exe on Windows 10. Here is a stack trace from a minidump: ntdll.dll!7ff903af6e1e()Unknown AcLayers.dll!7ff87cd77a56()Unknown prunsrv.exe!HeapFREE(void * hHeap, unsigned long dwFlags, void * lpMem) Line 71C

Re: crash in prunsrv

2019-05-24 Thread Gary Gregory
Which version of Commons Daemon are you using? Gary On Fri, May 24, 2019 at 10:33 AM Lode Leroy wrote: > Hi, > > I see frequent crashes in prunsrv.exe on Windows 10. > > Here is a stack trace from a minidump: > > ntdll.dll!7ff903af6e1e()Unknown >

Jsvc won't compile on synology NAS

2019-05-24 Thread Kelterino
Hi, i've tried to compile Jsvc on my synology 214play with a Intel Atom CE5335  but it appear there are some problems with pthreadlib (cd native; make  all) make[1]: Entering directory `/root/commons-daemon-1.1.0-src/src/native/unix/native' gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -Wall

Re: [statitsics] .gitattributes

2019-05-24 Thread Eric Barnhill
+1 Users should also beware that working on a repo in Windows in an IDE can cause the file to take on a pile of Windows line endings which git then pushes. This has happened to me elsewhere. Maybe this fix takes care of it. On Fri, May 24, 2019, 00:28 Alex Herbert wrote: > The recent PR to add

RC release request for SCXML

2019-05-24 Thread Nygard, Carl J
All, We are interested in using the SCXML project, but we have strict no-SNAPSHOTS-in-production policies in place that (currently) prohibit using SCXML. I'm wondering if it would be possible to cut an -RC release of SCXML as-is, with the idea that the additional work that Ate Douma outlined

Re: [statitsics] .gitattributes

2019-05-24 Thread Alex Herbert
On 24/05/2019 15:55, Eric Barnhill wrote: +1 Users should also beware that working on a repo in Windows in an IDE can cause the file to take on a pile of Windows line endings which git then pushes. This has happened to me elsewhere. Maybe this fix takes care of it. From what I understand