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 m
Github user jochenw commented on the issue:
https://github.com/apache/commons-fileupload/pull/6
@jvz I don't see anyone passing along any money. This is true open source
software. We're doing, what we consider to be best for our users in general.
@alexander-riss Please note, t
Github user thereallacas closed the pull request at:
https://github.com/apache/commons-rdf/pull/35
---
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 and wishes so, or if the featu
Github user jvz commented on the issue:
https://github.com/apache/commons-fileupload/pull/6
I don't see Oracle passing along that money to the ASF to continue
maintaining Java 6 software, though. ;)
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user thereallacas opened a pull request:
https://github.com/apache/commons-rdf/pull/35
Codereview
A manuális code review során felmerült apróbb és nagyobb code smellek
javÃtása.
You can merge this pull request into a Git repository by running:
$ git pull https://
On Apr 27, 2017 8:21 AM, "Gilles" wrote:
On Thu, 27 Apr 2017 10:10:57 -0500, Matt Sicker wrote:
> Choosing Java 8 or 7 for a new component depends on the APIs you want to
> use for it more so than what's current.
>
Indeed, the question could be rephrased as: Is there anything to loose
(for a ne
On Thu, 27 Apr 2017 10:10:57 -0500, Matt Sicker wrote:
Choosing Java 8 or 7 for a new component depends on the APIs you want
to
use for it more so than what's current.
Indeed, the question could be rephrased as: Is there anything to loose
(for a new component) if we allow the larger API of Jav
Choosing Java 8 or 7 for a new component depends on the APIs you want to
use for it more so than what's current. I hear people are still using Java
6, but I doubt those projects are adapting new libraries or upgrading any
of their dependencies as it is...
On 27 April 2017 at 09:41, Gilles wrote:
On Thu, 27 Apr 2017 14:49:01 +0200, Gilles wrote:
Hi.
The POM indicates:
1.6
1.6
but also:
(requires Java 7+)
Which is wrong?
Also, please not that keeping 1.6 compatibility seems to complicate
the Jenkins configuration:
https://builds.apache.org/view/Apache%20Commons/job/C
Hi guys,
If you add WordUtils.java back "as is", you can probably create a couple of
good "newbie" entries on the Apache "Help Wanted" site to attract people to
Commons-Text.
Cheers,Eyal
On Saturday, April 22, 2017 3:58 PM, Rob Tompkins
wrote:
> On Apr 22, 2017, at 8:44 AM, Pascal
Hi.
The POM indicates:
1.6
1.6
but also:
(requires Java 7+)
Which is wrong?
Regards,
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.
On 25 April 2017 at 22:35, sebb wrote:
> On 25 April 2017 at 20:36, Emmanuel Bourg wrote:
>> Le 25/04/2017 à 21:20, sebb a écrit :
>>
>>> Problem is that the short form does not generate the correct relative
>>> links from component pages to the Commons parent site.
>>> Such links need an extra .
Github user sebbASF commented on the issue:
https://github.com/apache/commons-fileupload/pull/6
Note that Oracle still offers (paid) support for versions of Java before 7:
http://www.oracle.com/technetwork/java/javase/eol-135779.html#java-commercial-offerings
---
If your pro
Github user alexander-riss commented on the issue:
https://github.com/apache/commons-fileupload/pull/6
as java < 1.7 is no longer supported through oracle it would be the
question how many of the app-servers which would integrate this version (as in:
latest-version) still support java
14 matches
Mail list logo
