Re: [ALL] Who want's access to @ApacheCommons

> Am 26.12.2017 um 16:41 schrieb Gary Gregory : > > GaryGregory I’ve added you as admin. Regards, Benedikt - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail:

[ALL] Who want's access to @ApacheCommons

Hi, I’ve created the Apache Commons twitter account [1] a few years ago. I try to announce anything that might be of interest for Commons users. Since my activity for the project varies a bit depending on what is going on in my life, I think it would be good if more people would have access to

Where has Benedikt been?

Hi, following the example from Rob in early November, I’d like to explain my recent two month in-actvity. As always this has been work related. I had to go through a pretty tough phase at work, that consumed all my energy. I’m currently working on a green field project for a customer, which

Re: Tagging Daemon 1.1

Hi Gary, > Am 02.11.2017 um 15:28 schrieb Gary Gregory : > > How about calling it 1.1.0? See Emmanuels answer on the other thread. Why would we do that? :-) Regards, Benedikt > > Gary > > On Nov 2, 2017 07:33, "Mark Thomas" wrote: > >> I have

Re: [LOGGING] Logging is Java 1.2 but required Java 1.4 code

t; wrote: >>>> >>>> From a pragmatic POV, the oldest Java byte codes you can get Java 9 to emit >>>> are for Java 1.6. Since we will want, I assume, to produce a module info >>>> class in the jar, we will need to use Java 9 for that (to keep an RM's

[RESULT][VOTE][LAZY] Migrate Apache Commons Validator to git

Hi, > Am 21.10.2017 um 10:22 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > I’d like to move Apache Commons Validator codebase to git, so I’m calling a > vote by lazy consensus. If nobody objects within the next 72 hours this vote > passes and I wi

[RESULT][VOTE][LAZY] Migrate Apache Commons BCEL to git

Hi, > Am 21.10.2017 um 10:21 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > I’d like to move Apache Commons BCEL codebase to git, so I’m calling a vote > by lazy consensus. If nobody objects within the next 72 hours this vote > passes and I wi

Re: [LOGGING] Logging is Java 1.2 but required Java 1.4 code

Gary Gregory <garydgreg...@gmail.com> wrote: >> >> Let's update to at least a minimum of Java 6 such that the build can run >> with Java 9. Builing with Java 9 will be a requirement to add module info. >> >> Gary >> >> On Oct 28, 2017 01:21, &qu

[LOGGING] Logging is Java 1.2 but required Java 1.4 code

Hi all, After I was able to update the the build to the latest parent POM, I’m running into animal sniffer problems. The build is defined to target Java 1.2 but there are classes which require later JDKs: - Jdk13LumberjackLogger - Jdk14Logger This breaks the build because animal sniffer

Re: [LOGGING] Problems updating to lastest commons parent

to how this old build wants to > name jars. Thank you, this fixed the problem. I’ll write a new message for the new problem :-) Benedikt > > Gary > > On Sat, Oct 21, 2017 at 2:30 AM, Benedikt Ritter <brit...@apache.org> wrote: > >> Hi, >> >> when

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

> Am 27.10.2017 um 12:51 schrieb Thomas Vandahl : > > Hi Gary, > > On 25.10.17 05:24, Gary Gregory wrote: >> Our process documented here http://commons.apache.org/releases/prepare.html >> makes it pretty clear that the RC tag should be labeled as such and that a >> tag like

[LANG] Merge PR for adding module-info

Hi, Stephen Colebourne has done a great job adding a module-info.java file to Commons Lang [1]. This can serve as an example for other components. Since Commons is pretty conservative when it comes to adopting new Java features, I’d like to ask a last time for feedback on the PR. Note that

Re: [collections] release 4.2

I‘m planning to work on it soon but I can‘t give you an ETA at the moment. Regards, Benedikt Gary Gregory schrieb am Di. 24. Okt. 2017 um 00:01: > We've had a couple of false starts here. Is the RM ready to fire off an RC? > > Gary >

Re: [lang] [LANG-1360] Add methods to ObjectUtils to get various forms of class names in a null-safe manner

. Done. > > > TIA, > Allon > > [1] https://github.com/apache/commons-lang/pull/302 > > On Sat, Oct 21, 2017 at 11:27 AM, Benedikt Ritter <brit...@apache.org> > wrote: > >> Hello Gary, >> >>> Am 20.10.2017 um 21:19 schrieb ggreg...@ap

[LOGGING] Problems updating to lastest commons parent

Hi, when I update commons-logging to use Commons parent 42, I get build failures: ~/w/a/c/commons-logging > mvn clean verify [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Commons Logging

Re: [lang] [LANG-1360] Add methods to ObjectUtils to get various forms of class names in a null-safe manner

Hello Gary, > Am 20.10.2017 um 21:19 schrieb ggreg...@apache.org: > > Repository: commons-lang > Updated Branches: > refs/heads/master 88654b79c -> 6ea2fc8d3 > > > [LANG-1360] Add methods to ObjectUtils to get various forms of class > names in a null-safe manner I think this belongs to

Re: [codec] Update for Java 7

Go for it. > Am 21.10.2017 um 01:26 schrieb Gary Gregory : > > Now that Codec 1.11 is out, I propose we update from Java 6 to 7. > > Gary - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

[VOTE][LAZY] Migrate Apache Commons Validator to git

Hello, I’d like to move Apache Commons Validator codebase to git, so I’m calling a vote by lazy consensus. If nobody objects within the next 72 hours this vote passes and I will start with the migration. This vote will be open until at least 24-October-2017, 10:30 CEST (UTC+2). Regards,

[VOTE][LAZY] Migrate Apache Commons BCEL to git

Hello, I’d like to move Apache Commons BCEL codebase to git, so I’m calling a vote by lazy consensus. If nobody objects within the next 72 hours this vote passes and I will start with the migration. This vote will be open until at least 24-October-2017, 10:30 CEST (UTC+2). Regards, Benedikt

[RESULT][VOTE] Release Apache Commons IO 2.6 based on RC3

Hello, > Am 15.10.2017 um 12:22 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > we have fixed quite a few bugs and added some nice new features since Apache > Commons IO 2.5 was released, so I would like to release Apache Commons IO 2.6 > based on RC

Re: [VOTE] Release Apache Commons IO 2.6 based on RC3

Hi, here is my +1 for this release. Benedikt > Am 15.10.2017 um 12:22 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > we have fixed quite a few bugs and added some nice new features since Apache > Commons IO 2.5 was released, so I would like to relea

Re: [CANCEL][VOTE] Release Apache Commons IO 2.6 based on RC2

;> On Oct 15, 2017, at 2:45 AM, Benedikt Ritter <brit...@apache.org> wrote: >> >> Hello, >> >>> Am 14.10.2017 um 14:35 schrieb Benedikt Ritter <brit...@apache.org>: >>> >>> Hello, >>> >>> we have fixed quite a few bug

Re: [VOTE] Release Apache Commons IO 2.6 based on RC3

> Gary > > On Oct 15, 2017 04:22, "Benedikt Ritter" <brit...@apache.org> wrote: > >> Hello, >> >> we have fixed quite a few bugs and added some nice new features since >> Apache Commons IO 2.5 was released, so I would like to release Apac

Re: [text] always use static imports for assertion methods

Hello Gilles, > Am 16.10.2017 um 11:07 schrieb Gilles <gil...@harfang.homelinux.org>: > > On Mon, 16 Oct 2017 09:30:01 +0200, Benedikt Ritter wrote: >>> Am 16.10.2017 um 00:34 schrieb Gilles <gil...@harfang.homelinux.org>: >>> >>> On Su

Re: [2/2] [lang] remove unused bcel test dependency

ad Checkstyle does not do that for you! >> >> Gary >> >>> On Oct 14, 2017 10:54, "Benedikt Ritter" <brit...@apache.org> wrote: >>> >>> Nice one! >>> >>> <pascalschumac...@apache.org> schrieb am Sa. 14. Okt. 201

Re: [LANG] Add module-info.java?

> I'd like to establish if there are any fundamental objections to the >> concept of building only on Java 9. I'm also willing to try and find a >> way to get the build to still work on Java 7, but that releases have >> to be on Java 9. >> >> Stephen >> >>

Re: [text] always use static imports for assertion methods

> Am 16.10.2017 um 00:34 schrieb Gilles : > > On Sun, 15 Oct 2017 14:45:09 -0500, Matt Sicker wrote: >> Assertion classes are just containers for static methods. Using "import >> static" is the only way in Java to import the individual methods as if the >> class

Re: [LANG] Introduce JUnit 5

; > Am 15.10.2017 um 11:48 schrieb Benedikt Ritter: >> Hi, >> >> I’d like to update Commons Lang to use JUnit 5. Existing tests will still >> run on the JUnit 5 vintage engine and we can migrate tests step by step to >> JUnit 5 style. >> >> One

[VOTE] Release Apache Commons IO 2.6 based on RC3

Hello, we have fixed quite a few bugs and added some nice new features since Apache Commons IO 2.5 was released, so I would like to release Apache Commons IO 2.6 based on RC3. The changes between RC1 and RC2 are: - Worked on the design of the ByteOrderParser class - Fixed IO-546 - Fixed IO-553

Re: [LANG] Add module-info.java?

long as we can make sure (e.g. with animal sniffer) that the resulting jar will work on Java 7 or what ever we want to support. Regards, Benedikt > > Stephen > > > > On 15 October 2017 at 10:49, Benedikt Ritter <brit...@apache.org> wrote: >> Okay, let’s get back to topic

Re: [LANG] Add module-info.java?

t;> up all over itself because it was incorrectly trying to do something with >>> these Java 9 class file :-( >>> >>> Gary >>> >>> On Sat, Oct 14, 2017 at 7:53 AM, Stephen Colebourne < >> scolebou...@joda.org> >>> wrote: >

[LANG] Introduce JUnit 5

Hi, I’d like to update Commons Lang to use JUnit 5. Existing tests will still run on the JUnit 5 vintage engine and we can migrate tests step by step to JUnit 5 style. One nice feature I’d like to use are nested tests. With these we could for example create a nested test class for each method

[CANCEL][VOTE] Release Apache Commons IO 2.6 based on RC2

Hello, > Am 14.10.2017 um 14:35 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > we have fixed quite a few bugs and added some nice new features since Apache > Commons IO 2.5 was released, so I would like to release Apache Commons IO 2.6 > based on RC2.

Re: [VOTE] Release Apache Commons IO 2.6 based on RC2

directly called mvn deploy without running clean. I will update the release documentation and push out a new RC. Thank you! Benedikt > > Oliver > > Am 14.10.2017 um 14:35 schrieb Benedikt Ritter: >> Hello, >> >> we have fixed quite a few bugs and added some nice new

Re: commons-collections git commit: MapUtilsTest: fix order of expected and actual parameter in assertions (closes #32)

About time we migrate to AssertJ. :-) Gary Gregory schrieb am Sa. 14. Okt. 2017 um 18:55: > Thank you for doing that! That was driving me nuts! > > Gary > > On Oct 14, 2017 10:53, wrote: > > > Repository: commons-collections > > Updated

Re: [2/2] [lang] remove unused bcel test dependency

Nice one! schrieb am Sa. 14. Okt. 2017 um 15:27: > remove unused bcel test dependency > > > Project: http://git-wip-us.apache.org/repos/asf/commons-lang/repo > Commit: > http://git-wip-us.apache.org/repos/asf/commons-lang/commit/66226ec1 > Tree:

Re: [LOGGING] Release with Java 9 Module support

> Am 01.10.2017 um 21:27 schrieb Stephen Colebourne : > > On 1 October 2017 at 11:34, Stefan Bodewig wrote: >> - only add the automatic module name to commons-logging and release api >> and adapter as they are. > > Exactly. This is the right approach.

[LANG] Add module-info.java?

Hi, Stephen Colebourne has raised a PR on GitHub to add a module-info.java file to Commons Lang [1]. The build is configured in a way, that the resulting jar will also work on Java 7 and 8. Since module-info is a Java 9 feature, the build will only work on Java 9. I’d like to hear opinions on

[VOTE] Release Apache Commons IO 2.6 based on RC2

Hello, we have fixed quite a few bugs and added some nice new features since Apache Commons IO 2.5 was released, so I would like to release Apache Commons IO 2.6 based on RC2. The changes since RC1 are: - Worked on the design of the ByteOrderParser class - Fixed IO-546 - Fixed IO-553 Commons

Re: [COLLECTIONS] Test failures on Windows

e/c >>> ommons-collections/commit/eed8a7adb3de7441751e846f4a75d110dd205f23. >>> I closed the pull request. >>> Thanks to all that helped testing & troubleshooting this interesting >>> issue! >>> I believe Commons Collections should now be in a state r

Re: [codec] Releasing 1.11 and the binary "cli" jar

Hi, > Am 12.10.2017 um 23:42 schrieb Gary Gregory : > > Hi all, > > I starting preparing RC1 to release 1.11 and I see a "cli" jar being > generated as documented in the POM: > > > > But the cli jar _is_ deployed when I run 'mvn clean deploy

Re: Commons IO 2.6 RC1 still in Nexus

Done! Sorry, I didn’t get the time yet to prepare RC2. Hope to have some time this evening or tomorrow. Benedikt > Am 08.10.2017 um 19:40 schrieb Benedikt Ritter <brit...@apache.org>: > > Yes, I will take of that. > > Benedikt > > Gary Gregory <garydgreg...@gm

Re: [COLLECTIONS] Test failures on Windows

res with jdk-1.7.0_67, jdk-1.8.0_131 and >> 9+181 >>>>> >>>>> Gary: >>>>> To get around the issue with ServiceConfiguration sun.util.locale... I >>>>> added the following profile to the pom.xml. After that I only got the >> 44 >

Re: Commons IO 2.6 RC1 still in Nexus

Yes, I will take of that. Benedikt Gary Gregory schrieb am So. 8. Okt. 2017 um 19:20: > Hi All, > > I see that Commons IO 2.6 RC1 is still in Nexus. We canceled the VOTE so we > can drop that RC. Right? > > Gary >

Re: [DISCUSS] - Move commons-chain to dormant?

> Am 07.10.2017 um 12:35 schrieb Pascal Schumacher : > > Hello everybody, > > the last commons-chain release is from 2008. > > The last bugfix/feature commits are from 2013. > > Since 2013 only one bugfix/feature released issue was created in JIRA. > > Maybe it is

Re: [lang] ExceptionUtils

Hello, > Am 06.10.2017 um 17:18 schrieb Zheng Xie : > > Hi. > > I have found the design of three root cause related methods inconsistent > when the input Throwable does not wrap up another Throwable. > > These three methods are > > 1. getRootCause(Throwable t) > 2.

Re: [IO] Design of ByteOrderFactory (Was: svn commit: r1301835 - in /commons/proper/io/trunk: RELEASE-NOTES.txt src/changes/ src/changes/changes.xml src/changes/release-notes.vm)

Hello Gary, > Am 03.10.2017 um 15:07 schrieb Gary Gregory <garydgreg...@gmail.com>: > > On Oct 3, 2017 03:47, "Benedikt Ritter" <brit...@apache.org> wrote: > > Hello Gary, > >> Am 02.10.2017 um 19:00 schrieb Gary Gregory <garydgreg...@gmail.

Re: [lang] Commons Lang 2.x release for Java 9

> Am 29.09.2017 um 10:08 schrieb Emmanuel Bourg : > > Hi all, > > I'd like to prepare a new release of Commons Lang 2 that addresses the > Java 9 compatibility. I have two items in mind for this update, the > automatic module name in the manifest of course, but also the >

Re: [IO] Design of ByteOrderFactory (Was: svn commit: r1301835 - in /commons/proper/io/trunk: RELEASE-NOTES.txt src/changes/ src/changes/changes.xml src/changes/release-notes.vm)

been to fast changing this class without giving others the chance to review and comment my changes. For this reason I canceled the release of IO 2.6. Let’s find a class design that everybody is happy with. Cheers, Benedikt > > Cheers, > Gary > > > Gary > > > >

[CANCEL][VOTE] Release Apache Commons IO 2.6 based on RC1

to find consensus about this new API before pushing 2.6. You can read more about this here [1] Regards, Benedikt [1] http://markmail.org/message/2o5gdwwv4eu53xwi > Am 30.09.2017 um 18:00 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > we have fixed quite a fe

[IO] Design of ByteOrderFactory (Was: svn commit: r1301835 - in /commons/proper/io/trunk: RELEASE-NOTES.txt src/changes/ src/changes/changes.xml src/changes/release-notes.vm)

Hey Gary, > Am 02.10.2017 um 16:15 schrieb Gary Gregory : > > I am not happy about the change of class name from ByteOrderFactory to > ByteOrderUtils. I am also did a knee jerk -1 when I saw the commit go by > but I have in the middle of moving. > > - A ByteOrderFactory

Re: [LOGGING] Release with Java 9 Module support

> Ralph > >> On Oct 1, 2017, at 1:25 AM, Benedikt Ritter <brit...@apache.org> wrote: >> >> Okay, so we agree to drop the api and adapters jars from the build and the >> distribution? If that is the case, I think we are ready to release this. >> >> B

Re: [LOGGING] Release with Java 9 Module support

n’t think that is going to happen :-) So what options are we left with? - Do nothing -> logging can’t be used as a Java 9 module - Drop api and adapters -> users have to change their dependencies and get more code than they want Anything else? Benedikt > >> Cheers,

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

Hello Gary, - signatures are good - Release notes look good - Website looks good With Java 7 and Java 8 I get these test failures: Results : Failed tests: ZipFileObjectTestCase.testReadingFilesInZipFile:98->readAndAssert:61

Re: [LOGGING] Release with Java 9 Module support

arizing commons-logging.jar and ignoring the other two. > > > Makes sense to me. > > Gary > > > Ralph > > > On Sep 30, 2017, at 1:28 AM, Benedikt Ritter <brit...@apache.org> wrote: > > > > > >> Am 26.09.2017 um 23:34 schrieb Stephen Colebourne

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

> Am 29.09.2017 um 15:47 schrieb Gary Gregory : > > Would a few of you please find the time to review this RC? Sorry for the delay. I will take a look tomorrow. Preparing IO 2.6 RC1 took longer than I thought… Benedikt > > Thank you in advance for your input, > Gary

[VOTE] Release Apache Commons IO 2.6 based on RC1

Hello, we have fixed quite a few bugs and added some nice new features since Apache Commons IO 2.5 was released, so I would like to release Apache Commons IO 2.6 based on RC1. Commons IO 2.6 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/io/commons-io-2.6-RC1

Re: [IO] Releasing 2.6

Okay, I'll cut RC1 this afternoon. Benedikt Pascal Schumacher <pascalschumac...@gmx.net> schrieb am Sa. 30. Sep. 2017 um 10:47: > Am 30.09.2017 um 10:26 schrieb Benedikt Ritter: > > Am 28.09.2017 um 09:39 schrieb Pascal Schumacher > > <pascalschumac...@gmx.net>:

Re: [LOGGING] Release with Java 9 Module support

proper/commons-logging/guide.html#Jars_Included_in_the_Standard_Distribution > Stephen > > On 26 September 2017 at 22:05, Benedikt Ritter <brit...@apache.org> wrote: >> >>> Am 26.09.2017 um 22:54 schrieb Stephen Colebourne <scolebou...@joda.org>: >>> >>> On

Re: [IO] Releasing 2.6

> Am 28.09.2017 um 09:39 schrieb Pascal Schumacher : > > Am 28.09.2017 um 00:14 schrieb Stian Soiland-Reyes: >> The new error is: >> FileSystemUtilsTestCase.testGetFreeSpace_String:89 >> expected:<1.02861164E8> but was:<1.0286066E8> >> >> I have: >>5

Re: [lang][text] TEXT-101: RandomStringUtils

> Am 29.09.2017 um 10:11 schrieb Pascal Schumacher : > > After thinking more about it, I came the conclusion that RandomStringUtils > fits into [lang], so I'm for option (b). +1 > > Cheers, > Pascal > > Am 28.09.2017 um 23:26 schrieb Rob Tompkins: >> Options: >>

Re: [SECURITY] CVE-2017-12621 Apache Commons Jelly connects to URL with custom doctype definitions.

I would like to give kudos to Rob for handling this issue. The kind of dedication you put into fixing this issue and releasing a component that has not been touched for ages is what I’m looking for in PMC members. Great work! Benedikt > Am 27.09.2017 um 15:05 schrieb Rob Tompkins

Re: [IO] Releasing 2.6

ion.run(TestExecution.java:38) > > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:539) > > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:761) > > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(Remot

Re: [LOGGING] Release with Java 9 Module support

> Am 26.09.2017 um 22:54 schrieb Stephen Colebourne : > > On 26 September 2017 at 18:48, Jörg Schaible wrote: >> AFAICS we have only commons-logging. The other artifacts have not been part >> of any release in the last decade. > > Simple then!

[IO] Releasing 2.6

Hey, I’m going through the list of components I happen to work with and make them ready for Java 9. Since I’m blocked in the release process of collections because of the Windows test failures, I’m going to cut a RC for IO 2.6 probably tomorrow night. Regards, Benedikt

Re: [LOGGING] Release with Java 9 Module support

Hello Jörg, > Am 26.09.2017 um 19:48 schrieb Jörg Schaible <joerg.schai...@gmx.de>: > > Hi Stephen, > > Stephen Colebourne wrote: > >> On 26 September 2017 at 16:06, Benedikt Ritter <brit...@apache.org> wrote: >>> commons-logging.jar >>> co

Re: [LOGGING] Release with Java 9 Module support

Hi again, > Am 26.09.2017 um 16:54 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > since LOGGING-165 [1] has been raised, I’m planning to add the > Automatic-Module-Name to logging and get a new release out of the door. Looks like I was a bit over enthus

[LOGGING] Release with Java 9 Module support

Hello, since LOGGING-165 [1] has been raised, I’m planning to add the Automatic-Module-Name to logging and get a new release out of the door. Regards, Benedikt [1] https://issues.apache.org/jira/browse/LOGGING-165 - To

[ALL] Failing Jenkins Builds

Hi, Jenkins Jobs for Commons Lang started to fail a while ago. The build log said, that Maven can not be found. I raised and issue yesterday [1]. Solution was to use Maven (latest) and JDK 1.8. Cheers, Benedikt [1] https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15167

Re: [ALL] Javadoc.io - a new GitHub badge for our projects?

I’ve added this to commons-lang. It can be reviewed on the GitHub mirror. > Am 18.09.2017 um 12:17 schrieb Amey Jadiye <ameyjad...@gmail.com>: > > +1, LGTM. > > Regards, > Amey > > On Mon, Sep 18, 2017, 3:24 PM Benedikt Ritter <brit...@apache.org> wrote:

[COLLECTIONS] Test failures on Windows

Hi, who can help with the test failures on Windows? I’d like to push out the next release soon to get Collections Java 9 ready. I don’t have access to a Windows installation and I don’t feel like debugging inside a VM :o) Regards, Benedikt

Re: [chain] Is anybody still interested

Hello Manfred. > Am 19.09.2017 um 09:03 schrieb Manfred Wolff : > > Hi everybody > > In the early 2000 I used to use commons chain very often. The approach is > nice: Small pieces of software, well testable, configurable via XML or > Spring, what ever. > > I have an own

Re: [RESULT][VOTE] Release commons-jelly-1.0.1 based on RC6

> Am 24.09.2017 um 02:50 schrieb Rob Tompkins : > > The following votes were case: > > Gary Gregory +1 (binding) > Oliver Heger +1 (binding) > Rob Tompkins +1 (binding) > > Thus, the vote passes. > > Many thanks to all who voted. I will proceed with the release

[COLLECTIONS] module-info.java and Java 9 (Was: [COLLECTIONS] Time for 4.2)

ould be included? Or do we have to create a Multi-Release jar? The build will definitely require Java 9. Cheers, Benedikt > > Stephen > > > > On 20 September 2017 at 17:03, Benedikt Ritter <brit...@apache.org> wrote: >> Hi, >> >>> Am 20.09.2017 um 1

Re: commons-collections git commit: COLLECTIONS-658: Add Automatic-Module-Name MANIFEST entry for Java 9 compatibility.

e >> Tree: http://git-wip-us.apache.org/repos/asf/commons-collections/ >> tree/80ec288e >> Diff: http://git-wip-us.apache.org/repos/asf/commons-collections/ >> diff/80ec288e >> >> Branch: refs/heads/master >> Commit: 80ec288ee76bc278d70aa234cbea407a2c9

Re: [COLLECTIONS] Time for 4.2

her the component is ready to be released as Java 9 module. For this reason we wanted to add this to every component individually. At least that is what I recall. Benedikt > > Gary > > On Wed, Sep 20, 2017 at 1:20 AM, Benedikt Ritter <brit...@apache.org> wrote: > >> Hi, &

[COLLECTIONS] Time for 4.2

Hi, I’d like to release Commons Collections 4.2 soon, because I want to get COLLECTIONS-658 [1] (Automatic-Module-Name MANIFEST header) out of the door. Please let me know if you want to add something. Regards, Benedikt [1] https://issues.apache.org/jira/browse/COLLECTIONS-658

[ANNOUNCE] Apache Commons BCEL 6.1 released!

For complete information on Commons BCEL, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the Apache Commons BCEL website: http://commons.apache.org/proper/commons-bcel/ Best regards, Benedikt Ritter on behalf of the Apache Commons community

Re: [RESULT][VOTE] Release Apache Commons BCEL 6.1 based on RC1

il.org/message/75hwfovacb2f4t4w > > Gary > > On Sep 18, 2017 01:02, "Benedikt Ritter" <brit...@apache.org> wrote: > > >> Am 14.09.2017 um 22:29 schrieb Benedikt Ritter <brit...@apache.org>: >> >> Hi, >> >> we’ve fixed some bugs an

[ALL] Javadoc.io - a new GitHub badge for our projects?

Hi, I just became aware of https://javadoc.io/ a website which provides hosting for all javadocs on Maven Central. They also provide badges for GitHub. Do we want to add this to our README.md files? Cheers, Benedikt

[RESULT][VOTE] Release Apache Commons BCEL 6.1 based on RC1

> Am 14.09.2017 um 22:29 schrieb Benedikt Ritter <brit...@apache.org>: > > Hi, > > we’ve fixed some bugs and added some new feature since Commons BCEL 6.0 was > released, so I’d like to call a vote to release Commons BCEL 6.1 based on RC1. > > BCEL 6.1 R

Re: [VOTE] Release Apache Commons BCEL 6.1 based on RC1

My +1 for this RC. Benedikt > Am 14.09.2017 um 22:29 schrieb Benedikt Ritter <brit...@apache.org>: > > Hi, > > we’ve fixed some bugs and added some new feature since Commons BCEL 6.0 was > released, so I’d like to call a vote to release Commons BCEL 6.1 based o

[VOTE] Release Apache Commons BCEL 6.1 based on RC1

Hi, we’ve fixed some bugs and added some new feature since Commons BCEL 6.0 was released, so I’d like to call a vote to release Commons BCEL 6.1 based on RC1. BCEL 6.1 RC1 is available for review her: https://dist.apache.org/repos/dist/dev/commons/bcel (rev 21612) The tag is here:

Re: [BCEL] Releasing 6.1

Hi, BCEL-286 has now been resolved and I’m slowly working towards RC1. Regards, Benedikt > Am 30.08.2017 um 21:37 schrieb Benedikt Ritter <brit...@apache.org>: > > Hello, > > I’ve committed the patches. BCEL-286 [1] can not be applied to trunk because > it updates a

Re: [collections] unit test failures

I'm not on my laptop, giving it a try later. What do Travis and Jenkis say? Benedikt Gary Gregory schrieb am Di. 12. Sep. 2017 um 16:47: > Hi All: > > I currently get 44 unit test failures in [collections] master. > > Can anyone duplicate this? > > Thank you, > Gary >

[LANG] Releasing 3.6.1

Hi, since we’re getting more and more requests about the deprecation of RandomStringUtils, I’m thinking about releasing the current state of the master branch as 3.6.1. I may have time to push an RC sometime this week. So if you have some fixes you want to include, please do so now. Regards,

Re: [ANNOUNCE] Apache Commons CSV 1.5 has been released

Great work, thank you! > Am 03.09.2017 um 08:21 schrieb Bruno P. Kinoshita : > > Hello, > > The Apache Commons Community is happy to announce the release of Apache > Commons > CSV 1.5. The Apache Commons CSV library provides a simple interface for > reading > and writing CSV

Re: [BCEL] Breaking changes in 6.1 needed by Tomcat (?)

Hi again, > Am 31.08.2017 um 01:38 schrieb sebb <seb...@gmail.com>: > > On 30 August 2017 at 20:11, Benedikt Ritter <brit...@apache.org > <mailto:brit...@apache.org>> wrote: >> Hi, >> >> looking through the JavaDoc comments in the Visitor

Re: [BCEL] Releasing 6.1

erts <mar...@cs.washington.edu>: > > Found another issue that needs to be corrected. I have updated the patch > file for https://issues.apache.org/jira/browse/BCEL-276. > > Thank you > Mark > > -Original Message- > From: Benedikt Ritter [mailto:brit...@ap

Re: [BCEL] Breaking changes in 6.1 needed by Tomcat (?)

or 3rd party visitor implementations. >> >> IIRC it was that BCEL will expect to be able to invoke the new >> methods; this will fail. >> There may be ways around this by catching the exception. >> >> The dev list should have the details. >> >> [1] ht

[BCEL] Breaking changes in 6.1 needed by Tomcat (?)

Hi, Rev. 1782852 [1] has introduced two breaking changes by adding the methods: public void visitAnnotation(org.apache.bcel.classfile.Annotations) public void visitAnnotationDefault(org.apache.bcel.classfile.AnnotationDefault) to the interface org.apache.bcel.classfile.Visitor. The commit

Re: [BCEL] Releasing 6.1

look into these. > > - Is the svn repo still the master? Yes, but we can migrate to git after this release. > Will you be creating a branch for the release? For SVN based components I usually don’t create a release branch. Benedikt > > Thank you, > Mark Roberts >

[BCEL] Releasing 6.1

Hi, I’m hereby announcing, that I’m going to work on BCEL 6.1 release very soon. Since I’m not a developer of BCEL, I’m only going to fix code style issues etc. So if there is anything missing from a functionality PoV, please go ahead and implement it now. Regards, Benedikt

Re: [old comonents/jelly] ant builds and releases.

Do we really want to go through this pain? Oliver Heger schrieb am Mi. 23. Aug. 2017 um 21:19: > > > Am 23.08.2017 um 12:15 schrieb sebb: > > On 23 August 2017 at 05:13, Rob Tompkins wrote: > >> Hello all, > >> > >> Does anyone remember how to,

Re: Move of Commons Transaction dormant incomplete

> Am 20.08.2017 um 12:30 schrieb Pascal Schumacher : > > Hello everybody, > > there is a jira issue https://issues.apache.org/jira/browse/TRANSACTION-39 > from 2010 with the steps to move Transaction to dormant. > > Some steps seem to have been completed (component

Re: [VOTE] Move Apache Commons Discovery to dormant?

+1 > Am 20.08.2017 um 12:14 schrieb Pascal Schumacher : > > Hi all, > > as discussed, I'd like to propose to move Apache Commons Discovery to dormant. > > Reasons: > - Last release was version 0.5 in 2011. > - The last bugfix and feature commits are from 2011. > - Not

Re: [All][Math] New component: "Commons Geometry"?

> Am 20.08.2017 um 23:11 schrieb Ralph Goers : > > I have to agree with Jochen and am -1 to this proposal. I have stated before > that I don’t want to see Commons become the placeholder for all the Math > related components. If Math has stuff that can’t be

Re: [VOTE] Move Apache Commons Launcher to dormant?

+1 > Am 20.08.2017 um 12:11 schrieb Pascal Schumacher : > > Hi all, > > as discussed, I'd like to propose to move Apache Commons Launcher to dormant. > > Reasons: > - The last release is from 2007. > - No bugfix or feature addition commits since 2007. > > So please

Re: commons-csv git commit: Better ivar name.

IMHO that's a bad name as well :o) Gary Gregory <garydgreg...@gmail.com> schrieb am Fr. 18. Aug. 2017 um 17:37: > We already have header*Map* ... > > Gary > > On Fri, Aug 18, 2017 at 9:23 AM, Benedikt Ritter <brit...@apache.org> > wrote: > > > Hello, >

Re: commons-csv git commit: Better ivar name.

Hello, I don't think this is a better name. In my opinion it's bad style to add types to variable names. How about recordContents or simply content/s ? Regards, Benedikt schrieb am Fr. 18. Aug. 2017 um 17:02: > Repository: commons-csv > Updated Branches: >

<    1   2   3   4   5   6   7   8   9   10   >