Re: [lang] Considering a new String utility class

On Wed, Mar 15, 2023 at 1:58 PM Gary Gregory wrote: > Instead, I can see adding a new String utility class that tracks such > attributes on its instance such that you'd say something like: > - Strings.caseSensitive().someOperation(...) > - Strings.caseInsensitive().someOperation(...). Agreed

Re: [Beanutils] BeanUtilsBean2

On Thu, Feb 9, 2023 at 1:47 PM Gary Gregory wrote: > > For 2.0, I think we should make the BeanUtilsBean2 class introduced in > 1.8.0 the only behavior, removing the need for the class. I think, these kind of ideas are exactly, what we have major updates for. Jochen -- Philosophy is useless,

Re: [VOTE] Release Apache Commons FileUpload 1.5 based on RC1

Here's my +1. Thanks for your work! On Thu, Feb 9, 2023 at 2:39 PM Mark Thomas wrote: > > Ping. One more PMC member vote required. > > Mark > > On 01/02/2023 12:57, Mark Thomas wrote: > > We have fixed a few bugs and added some small enhancements since > > FileUpload 1.4 was released, so I would

Re: [FILEUPLOAD] State of the 1.6 branch

On Wed, Dec 14, 2022 at 12:20 PM Mark Thomas wrote: > - Delete the b2_0 branch > - Move the head of the b1_4 branch to the 1.4 tag > - Update the b1_4 branch for development of 1.4.1 >(or should that be 1.5 and start a new branch?) > - Back-port my recent file count limit change If you can

Re: Math: Yearly patch for commons-math3

Hi, David, if you want to be sure, that commons-math3 is being maintained, then I suggest that you take a look at the Git repository log. That should be sufficient: https://gitbox.apache.org/repos/asf?p=commons-math.git;a=log Jochen On Tue, Dec 6, 2022 at 3:57 PM Darrell Merryweather wrote: >

Re: [VOTE][LAZY] Release Apache Commons Parent 54 based on RC1

On Sun, Sep 18, 2022 at 5:47 PM Gary Gregory wrote: > Details of changes since 53 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/54-RC1/RELEASE-NOTES.txt > >

Re: [fileupload] Have a FileUpload release (after 3.5 years)

On Tue, Jul 12, 2022 at 4:49 AM Matt Juntunen wrote: > Does anyone know what the state of 2.0 development is here? It looks > like the last feature-related changes were from Sept 2021. Is there > anything preventing a release? Mostly, that it is untested. On the other hand, it should be

Re: [jira] [Resolved] (CRYPTO-158) Illegal reflective access

Has this really been resolved? My understanding is, that Gary's remark applies to the comment by Matthew L. only, but not to the original reporters issue. Just asking, because I have recently learned to use method handles as a solution for this kind of messages. Jochen On Thu, Jun 30, 2022 at

Re: [CRYPTO] Drop support for OpenSSL < 1.1.x

On Wed, Jun 29, 2022 at 7:08 PM Gary Gregory wrote: > > An important aspect to consider is compatibility, we do not want to break > anything within a major version. True, but nothing prevents us from incrementing the major version number at this point. That would also enable us, to address more

Re: [CRYPTO] Multiple Docker files - are they both needed?

On Thu, Jun 16, 2022 at 7:00 PM sebb wrote: > [1] src/docker/Dockerfile > [2] src/conf/Docker/Dockerfile-luw Have to admit, that I wasn't aware of [2], when I created [1]. Mine is incomplete, and can easily be removed. Was basically just an attempt to reproduce the build instructions in the

Re: [Crypto] What is it ?

On Wed, Jun 15, 2022 at 6:33 PM Matt Sicker wrote: > > We could always request a Windows VM from Infra if necessary for building > releases. Same for a Mac VM or Linux VM, though the Linux one can be done > fairly easily via Docker on any OS (even FreeBSD supports Linux containers > now).

Re: [Crypto] What is it ?

On Thu, Jun 16, 2022 at 1:03 AM sebb wrote: > But unless one can host macOS on Windows or vice-versa, AFAICT it will > still require two hosts to generate a release. Well, that's the advantage of your suggestion to release the binaries separately. Jochen

Re: [Crypto] What is it ?

s Gary can find it and check > it in. In the meantime, I'll see if I can build one and provide it for > review. I think it would address many of the frustrations that people have > voiced here lately. Thanks for bringing up the issue. > > Alex > > On Wed, Jun 15, 2022

Re: [Crypto] What is it ?

On Wed, Jun 15, 2022 at 12:51 AM sebb wrote: > However, it might make it easier to release the binaries if they were > packaged separately, one per OS. That is a good point, of course! I would completely support that! Jochen

Re: [Crypto] What is it ?

On Tue, Jun 14, 2022 at 3:08 PM Gilles Sadowski wrote: > Is it a Java wrapper around a specific library ("openssl")? > Is it a set of tools (a.o. strong random number generators) for developing > cryptographic applications in Java? > Is it both? Does it intend to be more? > > In order to

Re: [Crypto] How to build?

Thanks, Bruno. Big help! On Thu, May 19, 2022 at 4:05 AM Bruno Kinoshita wrote: > There's a Dockerfile in the commons-crypto repo on GitHub. Not sure if it's > used for building it... but just in case it helps. - To

Re: [Crypto] How to build?

On Wed, May 18, 2022 at 9:15 PM Gary Gregory wrote: > > Yeah, I recall wanting to add a dockerfile... but if it's not there I'll > have to go hunt around for it and the notes I might have from that > release... Please do, Gary. Thanks, Jochen

[Crypto] How to build?

Hi, I recently had the questionable pleasure to get in touch with Commons Crypto, and could not build it. There are some instructions in the BUILDING.txt file, but they aren't really helpful. In case, you don't know: Crypto is not a simple Java library. Instead, it requires building some shared

[crypto] How to get the native library?

Hi, trying to run the unit tests for commons-crypto, I get the error message Native library is not loaded I understand, what it tells me. However, I do not find any hints on how to get the native library. Not on the website, not in the top-level docs. Can anyone help with that? Thanks,

Re: [lang] What does the animal-sniffer-maven-plugin compare against?

repo1.maven.org/maven2/org/codehaus/mojo/signature/ > > Older major versions have vendor specific suffixes, none of them use minor > version numbers. > > Gruss > Bernd > -- > http://bernd.eckenfels.net > ____ > Von: Jochen Wiedmann > Gesen

Re: [lang] What does the animal-sniffer-maven-plugin compare against?

}${javaTarget.minorVersion} java${javaTarget.majorVersion}${javaTarget.minorVersion} On Mon, May 2, 2022 at 7:57 PM Jochen Wiedmann wrote: > > Hi, > > I am currently preparing a feature for Lang, that makes use of > MethodHandle.invoke(Object...) > > According to the Java

[lang] What does the animal-sniffer-maven-plugin compare against?

Hi, I am currently preparing a feature for Lang, that makes use of MethodHandle.invoke(Object...) According to the Javadocs [1], this should be fine, but I am getting this from the animal-sniffer-maven-plugin: [INFO] --- animal-sniffer-maven-plugin:1.21:check (checkAPIcompatibility) @

Re: [VOTE] Release Compress 1.21 based on RC1

On Fri, Jul 9, 2021 at 10:09 PM Gary Gregory wrote: > "Details of changes since 1.19 are in the release notes:" > > 1.19 -> 1.20 ;-) Well observed. That said, I'd recommend to ignore this, since we want this release to be out of the door. Jochen -- Look, that's why there's rules,

Re: [compress] [Poll] Dealing with uncaught RuntimeExceptions

On Tue, Jun 29, 2021 at 10:24 PM Stefan Bodewig wrote: > (4) don't catch RuntimeExceptions at all, just document broken archives > can cause arbitrary RuntimeExceptions and code that tries to read > archives from untrusted sources is expected to deal with them > itself. Strongly in

Announce: CVE-2021-29425 (Possible limited path traversal vulnerabily in Apache Commons IO up to version 2.6)

, Jochen Wiedmann Description: In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not

Re: [lang] Introduce @NonNull, and @Nullable

On 2021/02/02 08:10:33, Julian Reschke wrote: > Please see . I may be missing the point here, so help me: My impression is, that the user doesn't need the jsr305 jar in the classpath, if we use it in out sources. If so, how should the Java 9 JRE detect

Re: [lang] Introduce @NonNull, and @Nullable

On 2021/02/02 11:34:09, sebb wrote: > In which case it should surely be listed as a compile dependency so > that it is picked up automatically? It is also picked up automatically with scope=provided. - To unsubscribe,

Re: [lang] Introduce @NonNull, and @Nullable

On 2021/02/01 16:45:46, Tomo Suzuki wrote: > I like "javax.annotation namespace" too. > > Would you be willing to share more about why the annotation dependency > should have "provided" scope? If a library (commons-lang) requires a > dependency at runtime, I believe it should declare it as

Re: [lang] Introduce @NonNull, and @Nullable

On Mon, Feb 1, 2021 at 2:34 PM Gary Gregory wrote: > 1) Don't add and use custom annotations, this opens the door to each of our > 20+ components doing the same thing, so pick a library and stick with it. I suggested starting with lang, because that would be the template for most others. (At

[lang] Introduce @NonNull, and @Nullable

Hi, as a followup to a discussion, that we had in August 2020, I'd like to propose, that we introduce the @NonNull, and @Nullable annotations into commons-lang. Since that discussion, I began to gradually introduce those annotations into my own code. From that, I have learned three things:

History blocked on Gitbox

Hi, on Gitbox, I noted the following: Clicking on any file in the tree, and then on the files history, I get the message "Forbidden You don't have permission to access this resource.". I'd expect that our Gitbox repos are completely open, so that came as a surprise to me. What do you think?

Re: [All] About Commons snapshot versions

On Thu, Sep 10, 2020 at 4:18 AM Peter Lee wrote: > I noticed that some Commons components snapshot versions released in > https://repository.apache.org/content/groups/snapshots/org/apache/commons > have not been updated for some time. > > Just curious about how do we publish snapshot versions

Re: No more dependabot

On Wed, Sep 16, 2020 at 2:38 PM Gilles Sadowski wrote: > Isn't what >https://spamassassin.apache.org/ > is about? Not that I am uptodate, but at least historically it hasn't. It's mostly about blocking spam. Related, but not necessarily reusable for the suggested purpose. Jochen --- Look,

Re: [All] New repo for all proper components as submodules?

On Sun, Aug 30, 2020 at 12:53 AM Gary Gregory wrote: > Any thoughts for or against creating a new git repository which would > contain all 'proper' Commons components as git submodules? > > The idea is to be able to checkout all of Commons 'proper' in one go in one > place. Sounds to me like a

Re: [vfs] consider about making FileObjectUtils be more like FileUtils in commons-io?

On Sun, Sep 6, 2020 at 3:39 PM Gary Gregory wrote: > The idea behind making *Util constructors private is that it does not make > sense to instantiate a class that only has static methods. True, but that also eliminates reuse by subclassing, and similar techniques. In my opinion, static utility

Re: No more dependabot

On Wed, Sep 16, 2020 at 12:37 PM Gilles Sadowski wrote: > As I've already stated in the previous "discussion" (from > where I was left with the only solution of filtering out), a lot > of the bot-generated messages is just spam. > IMO, it's not needed for traceability, and nobody/norobot is >

Re: No more dependabot

On Mon, Sep 14, 2020 at 2:48 PM Gary Gregory wrote: > - Jochen: What you do with your inbox is your business ;-) What is > the happy compromise here? Do you want a separate email list? Zero > Dependabot emails anywhere? If you feel strongly about this, please > create a [POLL] thread for what

No more dependabot

For the record: Mails from dependabot are now being deleted automatically from my inbox. I consider this to be a failed experiment, and would like us to terminate it. Jochen -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett,

Re: opinions about @NotNull and @Nullable ?

On Tue, Aug 25, 2020 at 9:08 PM sebb wrote: > AFAIK that means Maven won't download the dependency. > Surely that makes it harder for the developer? No, it means that Maven won't add the dependency to a distribution. However, I've got a question: These annotations have @Retention(Runtime).

Re: [LOGGING][DAEMON] Update Java 6 to 7

On Sun, Aug 16, 2020 at 12:13 PM Xeno Amess wrote: > 2. we wait for user argue about this. Mark Thomas just did, no need to wait. :-) -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time)

Re: [COMPRESS] Java 7- > 8

> > On Sat, 8 Aug 2020 at 13:05, Gary Gregory wrote: > > > > > > Hi All: > > > If we can update to Java 8, I can drop some code duplication very > > cleanly. Go for it. -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of

Re: [lang] org.apache.commons.lang3.concurrent.Locks is missing Javadocs for ALL public methods

On Thu, Jun 18, 2020 at 2:19 PM Gary Gregory wrote: > > Hi All and to the author of the new Locks class: It is missing Javadocs for > ALL public methods. > > May you please add them? I will. Sorry for missing this. -- Look, that's why there's rules, understand? So that you think before you

Re: About binary compatibility

On Tue, Jun 16, 2020 at 1:07 AM Gary Gregory wrote: > I kind of like inaging1 even if it is weird and even though we do not have > a precedent here in Commons. I'm curious what others think. I'm always in favour of saving characters. So, let's avoid the additional 1. It is not strictly

Re: [Graph] moving to git

On Tue, Jun 2, 2020 at 3:30 AM Amey Jadiye wrote: > I wanted to fetch opinion about moving commons-graph to git and possibly > creation of github mirror. We still haven't completed the move? Sure, as quick as possible. - To

Re: [IO] org.apache.commons.io.FileSystem for 2.7 or later

Looking at that class, it certainly seems to be a candidate for refactoring. For example, I could imagine to split the actual enumeration, and the implementation code into separate classes. But that can be done after a release, just as well. So, I'd say: Just go for it, and don't bother ("Include

JEXL: How to use non-map objects

Hi, slightly off-topic for the dev list (sorry!), but still: Any changes, one of you guys (and girls, of course) would be able to help with https://stackoverflow.com/questions/60632217/jexl-how-to-use-non-map-objects Thanks, Jochen -- Look, that's why there's rules, understand? So that you

Re: [VOTE] Release Apache Commons Configuration 2.7 based on RC2

+1 (Binding) On Mon, Mar 9, 2020 at 3:55 PM Rob Tompkins wrote: > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons Configuration 2.6 was released, so I would like to release > Apache Commons Configuration 2.7. > > Apache Commons Configuration 2.7

Re: [all] How PRs could be better

I understand your intention, *if* the PR is a bug fix. But, what about the others? On Thu, Feb 20, 2020, 14:53 Gary Gregory wrote: > Hi All: > > I wonder if any of you have an ideas regarding the following. > > When looking at _some_ PRs (that are green on GitHub, build with tests and > other

Re: [lang] New Streams code breaks build

Hi, Alex, On Tue, Feb 4, 2020 at 10:06 PM Alex Herbert wrote: > Travis just uses ‘mvn’. This triggers the default goal in the pom which does > this: Thanks for the information. I wasn't even aware, that there is a default goal. > I did note when I had a look that the main javadoc gives the

Re: [lang] New Streams code breaks build

On Mon, Feb 3, 2020 at 3:57 PM Gary Gregory wrote: > The commit > https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=2ea44b2adae8da8e3e7f55cc226479f9431feda9 > broke > the Travis build due to Checktyle errors. As the responsible person, I apologize for that. I am sure, that I did

Re: New Sub-project Proposal.

Hi, Claude, having read, what a bloom filter is, a subproject sounds unnecessary to me. I'd recommend, that you contribute your code to Commons Collections, which seems to me to be a logical target. Jochen On Tue, Sep 10, 2019 at 8:45 PM Claude Warren wrote: > > Having spoken with several

Re: [lang] Giant StringUtils vs. NullSafeStrings.

On Tue, Jun 4, 2019 at 1:07 PM Xeno Amess wrote: > > Then 10 years later JDK has its own Strings, and users get confused then. If we (and the users) wouldn't be ready to accept that risk, then we could forget the whole project. Jochen

Re: [All] Help with GitHub "support"

I think, that Gilles is right in pointing out, that the current policy (accept patches only with explicit, or implicit, acceptance of contribution under the ASL) clashes somehow with Github PR's in that it is difficult to assume implicit acceptance in that cases. However, I don't think that this

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

On Tue, Apr 9, 2019 at 3:51 PM sebb wrote: > We already have a process for ensuring that Maven coords and package > names are changed when API breaks. > Do we really want to have yet another name that has to be maintained? What's the alternative? > Being able to define the module name

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

On Tue, Apr 9, 2019 at 2:43 PM sebb wrote: > Unless I am misunderstanding this, the property value won't be checked > to see if i is changed when an incompatible versioni s released. True, but that applies in either case, as soon as we have module names, doesn't it? So, I'd like to keep this

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

On Tue, Apr 9, 2019 at 12:43 PM Gilles Sadowski wrote: > ${commons.automatic.module.name} Fine with me. > Then the release plugin could be enhanced (?) so that it would check > whether the variable has been defined for each JAR to be created (and > fail the build otherwise). As already

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

On Tue, Apr 9, 2019 at 2:37 PM Gary Gregory wrote: > Can't we do this in a more lightweight manner in Checkstyle or in our build > Maven plugin? I'll leave the former idea to you, and the latter to Rob. Myself, I don't know in both cases. But I am open. Jochen

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

On Tue, Apr 9, 2019 at 1:22 PM Gilles Sadowski wrote: > From > https://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html > ---CUT--- > Module names must be valid Java identifiers! E.g. no Java keywords, no > dashes, no... > ---CUT--- Wasn't aware of that, thanks for the hint. Jochen

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

On Tue, Apr 9, 2019 at 10:48 AM John Patrick wrote: > As commons-lang3 has the module name org.apache.commons.lang3, not > commons-lang3 which is the artifactId, because "-" is invalid in a > real module name and they realised this when starting to support jpms. Commons-lang, and others, can

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

On Tue, Apr 9, 2019 at 9:54 AM sebb wrote: > > I have studied EMAIL-186. My impression is, that all commons jar files > > should provide a fixed module name, rather than trusting in the choice > > of the JDK. Thus, it seems best to handle this in parent. So, here's > > my proposal for a change.

***UNCHECKED*** [parent] Introducing Automatic-Module-Name

Hi, I have studied EMAIL-186. My impression is, that all commons jar files should provide a fixed module name, rather than trusting in the choice of the JDK. Thus, it seems best to handle this in parent. So, here's my proposal for a change. Please, let me know, what you think of that, so that I

Re: [lang] Towards 3.9

On Fri, Apr 5, 2019 at 4:27 AM Rob Tompkins wrote: > > > On Apr 4, 2019, at 9:20 AM, Gilles Sadowski wrote: > > > >> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us > >> to go up with what we have. Any thoughts for or against doing a release? > > > > Any objection to

Re: New Confluence space created: COMMONS

FYI (Migration of the Moinmoin wiki has been requested). On Mon, Mar 25, 2019 at 8:55 PM ASF Self-Service Platform wrote: > > > Hi there, > As requested by joc...@apache.org, a new Confluence space has been set up at: > https://cwiki.apache.org/confluence/display/COMMONS > > > > With regards, >

GitHub Pull Requests (and Confluence)

Hi, just FIY: Today I tried to accept a pull request from Github, following the procedure, as outlined on https://cwiki.apache.org/confluence/display/ROLLER/How+to+accept+a+GitHub+Pull+Request (Of course, the Git URL has to be adjusted to your subproject, in my case

Re: [Parent] RAT check

On Mon, Mar 11, 2019 at 5:58 PM Gary Gregory wrote: > The idea, for me, is that a contributor should not be able to test and > submit a PR with a failing RAT check. If so, then I'd suggest a server-side Git hook for that. Jochen

Re: [Parent] RAT check

On Sat, Mar 9, 2019 at 11:45 PM Gary Gregory wrote: > How about making apache-rat:check run automatically in commons-parent? In > the Maven validate phase? Not being a Maven expert: When would that check run, exactly? If that would include a simple "mvn clean install", then I'd definitely be

Re: [CSV] Update from Java 7 to 8

Go! On Sat, Feb 23, 2019 at 2:16 PM Gary Gregory wrote: > > Hi All: > > I plan on updating Commons CSV from Java 7 to 8. > > Gary - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail:

Re: [LANG] Checked Functions PR

On Tue, Jan 29, 2019 at 1:04 AM Aleksander Ściborek wrote: > The idea behind this is that you can create an instance of a function which > throws a checked exception and then using a static method create an > instance of standard function which invocation of a checked functions. Have you seen

Re: [VOTE][LAZY] Move all proper svn repos to gitbox

On Tue, Jan 8, 2019 at 5:33 PM Rob Tompkins wrote: > > Vote statement: "I propose we move all ‘proper' svn repos to gitbox." > I’m not quite sure if this list is complete. It would be good to have someone > come behind me to check the list. After this vote my plan is to work peace > meal

Re: [VOTE][LAZY] Move commons-codec to gitbox after 1.12 release.

Weren't we going to fo that for *all* of our projects? On Fri, Dec 28, 2018 at 4:17 PM Pascal Schumacher wrote: > > +1 > > Am 28.12.2018 um 15:51 schrieb Rob Tompkins: > > After doing the 1.12 release I propose we move commons-codec to gitbox. > > This is a [LAZY] consensus [VOTE] for doing

Re: [commons-fileupload] branch master updated: Changing Maven Coordinates, and package name, as required for binary incompatible changes.

Hi, Rob, On Thu, Dec 27, 2018 at 2:35 PM Rob Tompkins wrote: > > @Jochen I’m going to have a go at merging in 1.4 to master such that it > causes no conflicts. Is that ok??? I wasn't aware of that, so excuse me, if I have been too fast. Just commit, whatever seems to make sense, or rollback my

Re: Move fileupload to Gitbox

In light of Rob Tompkins proposal to move all, I retract my suggestion. On Mon, Dec 10, 2018 at 5:25 PM Gary Gregory wrote: > > Go for it :-) and thank you. > > Gary > > On Mon, Dec 10, 2018 at 8:58 AM Jochen Wiedmann > wrote: > > > Hi, > > > > as a f

Re: [VOTE][LAZY] move commons git-wip repos to gitbox

+1 And, may I suggest, that we add bcel, beanutils, etc. (those still in svn) to the list? On Mon, Dec 10, 2018 at 7:51 PM Matt Sicker wrote: > > +1 (non-binding) > > Though if it helps move things faster, I already held this vote a while > ago: >

Move fileupload to Gitbox

Hi, as a followup to [1] I'd like to move fileupload to Gitbox. (It's better to know in advance, so that pointers to the repository can be adjusted, rather than react later on.) If noone intervenes within three days, I'll file a Jira issue. Jochen 1:

Re: [jira] [Commented] (IO-588) IOUtils.writeLines() should accept an Iterable<>

On Fri, Oct 12, 2018 at 6:06 PM Gary Gregory (JIRA) wrote: > Thank you for your patch but... -1 to this patch as it breaks binary > compatibility. Could you explain that, please? A Collection is, in particular, an Iterable, thus the compiler should use the new methods, instead, as far as I can

Re: [beanutils] Java version

On Fri, Oct 12, 2018 at 11:36 PM Gary Gregory wrote: > For 2.0.0, we've update [beanutils] from Java 6 to 7, but should we move to > Java 8 instead since anything older is deader than a doornail? Go on. People need to upgrade their VM anyways,

Re: unsubscribing - feel free to contact me directly

On Mon, Aug 20, 2018 at 2:01 AM Remko Popma wrote: > > I've taken on too much work and need to scale back, so unsubscribing from > this list. Quite understandable. I take it, this doesn't affect your work on log4j? Regards, Jochen

Re: [dbcp] Next

On Sun, Jun 17, 2018 at 2:42 PM Gary Gregory wrote: > 3.0.0 somewhat implies API breakage which has not happened yet so 2.5.0 is > better for now IMO... +1 for going to 3.0.0 anyways. This would perhaps fix the problem for Tomcat, assuming that we keep a maintenance branch for 2.x. Jochen

Re: [jira] [Commented] (IO-579) FilenameUtils.isExtension() is case-sensitive

On Fri, Jun 8, 2018 at 5:07 PM Gary Gregory (JIRA) wrote: > Case-sensitivity for file names depends on the file system. The Javadoc for > this method specifies "The extension check is case-sensitive on all > platforms." There is nothing to fix in this API IMO. To me, this sounds like a strong

Re: [FileUpload] broken src/changes/changes.xml

Which branch? On Mon, May 21, 2018 at 4:11 PM Gary Gregory wrote: > The file src/changes/changes.xml is broken. It looks like a merge did not > apply cleanly. > Gary - To unsubscribe, e-mail:

Re: [VOTE][LAZY] Release Commons Release Plugin 1.2 based on RC1

On Thu, Apr 5, 2018 at 5:20 PM, Rob Tompkins wrote: > Here’s my +1. And mine. (+1) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [All][Math] "Commons Geometry": first step?

On Mon, Apr 2, 2018 at 3:17 AM, Matt Juntunen wrote: > Should I make one on github? Whatever the response: *Please*, do never create source code repositories, forums, build jobs, or the like, on external servers. At least not, without prior acknowledgement by Apache

Re: [httpclient] Better user agent header?

On Fri, Mar 30, 2018 at 12:20 AM, Gary Gregory wrote: > User-Agent: Apache-HttpClient/4.5.5 (Oracle Corporation/Java/1.8.0_162) > Windows/10.0 (amd64) > > Any thoughts for or against adding this to the user agent string? You are aware, that you can configure your own

Re: [configuration] Java 8 types

+1 On Wed, Mar 28, 2018 at 9:06 PM, Gary Gregory wrote: > Hi All: > > I say it is time to update Commons Configuration to Java 8 and support the > types in java.time. > > Thoughts? > > Gary - To

Re: [lang] Todo utility class

On Fri, Mar 16, 2018 at 12:05 AM, Gilles wrote: > Perhaps "Commons Testing". > IIUC, such calls are not meant to appear in released code. Neither would testing. I like the idea of a Todo class. Makes searching for such places extremely neat, and simple. Jochen

Re: [LAZY][VOTE] Release Commons Parent 44 based on RC1

On Tue, Mar 6, 2018 at 2:24 PM, Gilles wrote: > (1) > "FindBugs" should be replaced by "SpotBugs" (or there will > be failures when creating "module-info" files). +1 to doing this change quickly, possibly blocking a release. Jochen

Updating the web site

Hi, I urgently need to update the page on [1]. Now, could someone, please explain to me in plain, simple words (suitable for a 54 years old, or, even worse: Me), how to do that using cms.apache.org? Or, even better: Could we agree to switch to plain SVN, or Git as the Web site repository? With

Re: Releases of JCS

On Thu, Feb 22, 2018 at 5:58 PM, Gilles wrote: > From the "announce" ML archives[1] it seems there weren't. Thanks. That helps! - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For

Re: [text] Upper/Lower case enum

On Thu, Feb 22, 2018 at 11:14 PM, Otto Fowler wrote: > What problem does it solve? Good for functional programming? - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands,

Releases of JCS

Hi, with regards to a bug, I need to find out, whether that bug has been present in any official release. Looking into archive.apache.org, I find Commons JCS 1.3, and Jakarta JCS 1.3, both of which don't contain the bug, because it had already been fixed, at the time. The only SVN tags I find,

Re: Commit => Update Jira Issue

Hi, Pascal, On Wed, Feb 21, 2018 at 6:29 PM, Pascal Schumacher wrote: > you did not miss anything. Commons does not have any synchronization between > commit messages and jira issues (or at least the projects I am aware of). if so: Wouldn't this be worth changing?

Commit => Update Jira Issue

Hi, I notice that my commit in [1] did not update the Jira issue in [2], although I used the prefix "PR: IO-567" Did I miss something? Thanks, Jochen 1: https://git-wip-us.apache.org/repos/asf?p=commons-io.git;a=commit;h=748eef8b96068cadc45894967f58f015860afb1b 2:

Re: [VFS] HttpClient version 3, 4 and 5

On Sun, Feb 18, 2018 at 9:21 PM, Gary Gregory wrote: > - Create a new package org.apache.commons.vfs2.provider.http4, or > - Break BC on the classes in org.apache.commons.vfs2.provider.http Break BC, and do it right: Don't expose HttpClient in the API. Emphasis being on

Re: [All][RNG] FindBugs discontinued

Hi, Gilles, are you aware of https://spotbugs.github.io/ Apart from the name change: A lot of commits in January. Doesn't look dead to me. Jochen On Fri, Feb 16, 2018 at 9:04 AM, Jacques Le Roux wrote: > Le 14/02/2018 à 19:02, Gilles a écrit : >> >> FindBugs

Re: [text] Update from Java 7 to Java 8?

On Tue, Feb 13, 2018 at 11:13 PM, Gary Gregory wrote: > Fine with me. Let's see if anyone objects... As there seem to be other incompatible changes in the pipeline (StrBuilder, etc.), this should be a good opportunity. Jochen

Re: [compress] cut 1.16.1 very soon?

On Wed, Feb 7, 2018 at 9:54 AM, Stefan Bodewig wrote: > I know I asked before (I really am not an OSGi guy at all) and was > pointed into a direction for writing a test that would start a small > container and load the bundle. This should help, but unfortunately the > very

Re: [compress] cut 1.16.1 very soon?

On Tue, Feb 6, 2018 at 4:43 PM, Stefan Bodewig wrote: > it looks as if I again managed to break the OSGi manifest without > anybody noticing (I'd be the last one to notice): Can't the Felix folks help with that? Perhaps a suitable Maven plugin for the validate phase. Seems

Re: [io] New filevisitor package

My impression is, that you are referring to Files.walkFileTree? Jochen On Fri, Feb 2, 2018 at 9:39 PM, Gary Gregory wrote: > Hi All: > > I propose a new package for [IO]: org.apache.commons.io.filevisitor. > > This package will implementations of FileVisitor just like

Re: [Email] Using SVN, but Github mirror

On Sat, Jan 20, 2018 at 2:53 PM, Stefan Bodewig wrote: > This is probably true for almost every svn codebase we've got. May be. I am just surprised, that mirroring from SVN to Git works. Jochen - To

[Email] Using SVN, but Github mirror

Hi, I just noticed, that commons-email is still in SVN, but has a Github mirror nonetheless. Seems strange to me? Thanks, Jochen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail:

  1   2   3   4   5   >