[GitHub] commons-text issue #49: TEXT-89: UTF-32 support for WordUtils.initials using...

Github user ecki commented on the issue: https://github.com/apache/commons-text/pull/49 Not sure I understand the question, surrogate Pairs only exist in UTF-16. UTF-8 uses a multi byte encoding for code points outside the BMP and UTF-32 uses 4 bytes (and skips the high/low surrogate

[GitHub] commons-text issue #49: TEXT-89: UTF-32 support for WordUtils.initials using...

Github user ecki commented on the issue: https://github.com/apache/commons-text/pull/49 It does not provide support for UTF-32 (which is a 4 byte encoding not implemented in the patch) but it provides support for UTF-16 surrogate pairs (1..2 x 2bytes). The both encodings

[GitHub] commons-text issue #49: TEXT-89: UTF-32 support for WordUtils.initials using...

Github user ecki commented on the issue: https://github.com/apache/commons-text/pull/49 It still uses missleading UTF-32 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[GitHub] commons-text issue #49: TEXT-89: UTF-32 support for WordUtils.initials

Github user ecki commented on the issue: https://github.com/apache/commons-text/pull/49 I think using UTF-32 to describe UTF-16 with surrogate pairs is a bit misleading. So I would adjust subject and comment, as this does not enable fixed-4-byte characters. --- If your project

[GitHub] commons-fileupload issue #6: improve GC by avoiding FileInput/Output-Streams

Github user ecki commented on the issue: https://github.com/apache/commons-fileupload/pull/6 Note that this might improve slightly the finalizer pressure however FileChannel(InputStreams) have pretty much internal overheads including locks and synchronized, so the actual performance

[GitHub] commons-io pull request #33: [IO-531] JavaDoc to describe accept-any file fi...

GitHub user ecki opened a pull request: https://github.com/apache/commons-io/pull/33 [IO-531] JavaDoc to describe accept-any file filter You can merge this pull request into a Git repository by running: $ git pull https://github.com/ecki/commons-io patch-1 Alternatively you

AW: [compress] Added in-memory support for zip and 7z

Hello, Even when a stream is not thread safe I try at least to make close() safe/atomic as aborts and finalizers or shutdown hooks are natural sources for concurrency – all using close(). Using a AtomicBoolean or flag is good for that. (However I guess it is less problematic for memory

Re: [vfs] Wiki update for Manta VFS provider

Hello Elija, I can do that for you, let me know the wording and link you want to be included. Gruss Bernd -- http://bernd.eckenfels.net >From Win 10 Mobile Von: Elijah Zupancic Gesendet: Montag, 3. Oktober 2016 14:16 An: Commons Developers List Betreff: [vfs] Wiki update for Manta VFS provider

Re: open source projects that are using SCXML

Hello, I guess there are some search engines to do that. Versioneye for example can show all projects using 0.9 in the maven repo: https://www.versioneye.com/java/commons-scxml:commons-scxml/references Gruss Bernd -- http://bernd.eckenfels.net >From Win 10 Mobile Von: Benedikt Ritter

Re: [VOTE][LAZY] Migrate Apache Commons Fileupload to Git

+1 for Git -- http://bernd.eckenfels.net -Original Message- From: Jochen Wiedmann To: Apache Commons Developers List Sent: So., 10 Juli 2016 12:46 Subject: [VOTE][LAZY] Migrate Apache Commons Fileupload to Git Hello, I'd like to

Re: [VFS] CI in POM?

Hello, I will take a look at the failing solaris builds, something in the hadoop test cluster does not work there. Jenkins Karma would be fine, Gary. (e...@apache.org) Can I sent failed jobs announcement to dev@ or maybe the commit@ list, i think we had that for continuum before. I will

Re: [VFS] CI in POM?

Thanks, had found it meanwhile. Should we add Jenkins to the parent POM or a more specific section into the project pom? Can anybody with Jenkins Karma reconfigure the Jobs to use minimum Java 7, the Jobs fail since that change:

Re: [crypto] Logging dependency

Loggin Infrastructure can be quite complex including formatters, filters, api- or file based reconfiguration and so on. It can inckude dynamcally registering loggers and stuff. Switching the loggin backend is a (non-functional) major work in larger products/systems and app servers. It would be

Re: [NET] - FtpClient.getStatus(path) does not seem to be working as documented.

According to RFC959 the STAT command can be used with a pathname (and without while transfer is ongoing). I think your problem in the sample output is, that your FTP command client is not really issuing a STAT command. I would recommand you use a raw TCP connection like netcat/telnet to debug

Re: [crypto] On Java 6, really?

Hello, IBM, SAP and HP also maintain/support Java 6 runtimes for still some time. The audience get smaller and we should not restrict developers to use/provide Java 8 features but if a component team is happy to start a new project with Java 6, why not... (especially since there are also

Re: [crypto] Instructions MUST mention running the tests

Hello, I also make a habit out of using "mvn verify" instead of "mvn package" (for the same reason, do never document circumventing potential tests). Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: Gary Gregory To: Commons Developers List

Re: [ALL] About binary compatibility

Hello, Unhappy with it but agreeing that your definition sounds like it should apply. I would vote for always bumping at least the minor version when requiring newer dependencies (including Java Version). Strictly speaking semver would require a major version but with our policy of using new

[Vfs] to git (was: Apache Commons git repositories now writable for all ASF committers)

I would nominate VFS to move to git, the question is do we keep want to do that one by one? Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: Gary Gregory To: Commons Developers List Cc: annou...@apache.org, Commons

Re: [ANNOUNCE] Apache Commons git repositories now writable for all ASF committers

Hello Jochen, I think the announcement is refering to the Apache hosted Git (writeable) repositories (https://git-wip-us.apache.org/) - not the apache organisation on github or the public git mirror (https://git.apache.org). Those are always read-only mirrors. (Note that most commons projects

[Rdf] Re: Nexus: Promotion Completed

Hello, It would be good if Incubator "releases" would be announced here on the development list. I havent been aware of all the (excellent) work going on in the commons-rdf sub project until I saw this release. The Incubator site and the maven artifacts are all fully commons branded already,

Re: [VFS] Final steps for 2.1

Hello, I understand the dist module as preparing the artifacts for the binary and source distribution of the ASF download. And I agree that those target files must not be attached to the maven repository. As such the POM can be changed to a POM only module (or manually removed from the repo).

Re: [eclipse-dev] Notice that Eclipse Platform plans to no longer provide MD5 and SHA1 checksums for Neon (but still SHA512)

Hello, Fully agree for checksum files no stronger hashes are needed. For the pgp signatures we should however avoid md5/sha1. The advantage isnthat this is pretty transparent (alg encoded in .asc file). It only breaks for some very old invoked pgp binaries. (Theoretically we can add multiple

Re: [VFS] WIP specific release instructions

Hello, BTW: I would use "mvn verify" instead of "mvn package" (I am not sure what has changed for CP40) (And yes the release plugin and the commons procedure for releases is a match in hell ,) Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: Josh Elser

Re: [VOTE] Apache Commons VFS 2.1 rc1

Hello, Java 9 is not supported (only 8), for the other problems I am not sure, do you consider that an blocker? Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: "Jörg Schaible" To: dev@commons.apache.org Sent: Do., 05 Mai 2016 0:39 Subject:

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

Hello, Agree, the sandbox profile should be in the site build enabled, but we cannot distribute the binaries as official release since it has dependencies which are not Apache approved (and potentially unfinished suff). Gruss Bernd -- http://bernd.eckenfels.net -Original Message-

Re: [VFS] 2.1 clirr report

Hello, I will/would vote for releasing 2.1 even when there are some minor problems (if it is well documented). Because I do see a large number of bugs for 2.0 and those users wont easily profit from a 3.0 (and I dont think backporting or removing of all incompatibilities will happen). Having

Re: [VFS] 2.1 Release Plan

The components have been updated multiple times. The more we modernize it (including new java version) the less useful the release will be as a drop-in replacement for 2.0. I had the impression some bug reporters would like that. (Just for the record I wondered about having an additional a

RE: Maintain sub pools within Commons pool - is it possible

Hello, You can programmatically create and configure pools at runtime. (At least if you skip container infrastructures). You can even dynamically register the pools in JNDI. I dont think you need sub-pools for this. (Subpools would be more interesting for partitioning connections by

RE: Maintain sub pools within Commons pool - is it possible

(Ignore my mail, I missed the fact that the initial discussion was about REST clients not JdBC) -- http://bernd.eckenfels.net -Original Message- From: e...@zusammenkunft.net To: dev@commons.apache.org Sent: Fr., 29 Jan. 2016 7:39 Subject: RE: Maintain sub pools within Commons pool - is

Re: [Math] Add 64-bits based RNG (Was: [Math] New base class for all RNGs)

BTW, there are some unsignedLong supporting methods in Java 8, I think some of them are even intrinsics, this includes unsigned parsing, printing, comparision and division/reminder. I think not yet a modular add.

Re: [vfs] New Properties for FtpFileSystemConfigBuilder

Hello, Yes it would be good if you can open a Jira bug. You can then either attach your patch as a file attachment or add an URL to the GitHub pull request. I dont think there will be any point release like 2.0.1 but the next target version is 2.1 (based on the current trunk). This is supposed

Re: Blog post "commons" vulnerability

Hello Sally, Yes it is just a screenshot of a tweet, I could not come up with a useful graohic for the topic and since discussion on Twitter somewhat powered all the fuzz I figured it would fit. Regarding Phils comment I think having some "apache commons" communication on blogs does help the

Re: [collection][security] InvokerTransformer missused in java object serialisation exploits

>> Both sample payloads have "gadget chains" which do start (readObject()) >> in JCL classes and then use pretty generic interfaces like Annotations >> or Comparators, so there is really no link between the types and the >> specific weakness. > I did not see JCL (commons logging?) used in the

Re: [VFS] Jackrabbit

Hello, Unfortunatelly the whole webdav filesystem tests depend on that specific version as it wraps the server as an endpoint. The setUp fails so the whole test suite will get skipped. I havent been able to quickly fix when I tried to bump the dependency (but it is not impossible, as you can

Re: Proposed Contribution to Apache Commons,

Hello, I wish the below cited introduction mail which mentioned how ugly RE for email addresses is, had actually shown a naomi example. Actually for each critisised RE construct. Besides that, scalability and maintenanceability of regular expressions are an old topic: there are for example