On 26 January 2015 at 11:47, Benedikt Ritter wrote:
> 2015-01-26 12:25 GMT+01:00 sebb :
>
>> On 26 January 2015 at 07:30, Benedikt Ritter wrote:
>> > Hello sebb,
>> >
>> > 2015-01-25 12:55 GMT+01:00 sebb :
>> >
>> >> On 25 January 201
> IMO and can be fixed for next one
Given how infrequently releases are made, I don't think that is a good idea.
>
>
>
> Romain Manni-Bucau
> @rmannibucau
> http://www.tomitribe.com
> http://rmannibucau.wordpress.com
> https://github.com/rmannibucau
>
>
nni-Bucau
> wrote:
>> Ok so you only speak about dist src bundle?
>>
>> Not sure it does need to cancel the vote, this is not a major issue
>> IMO and can be fixed for next one
>>
>>
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau
>> h
On 26 January 2015 at 16:47, Romain Manni-Bucau wrote:
> 2015-01-26 17:41 GMT+01:00 sebb :
>> On 26 January 2015 at 12:20, Romain Manni-Bucau
>> wrote:
>>> Ok so you only speak about dist src bundle?
>>
>> No, it also affects the binary bundle, and it aff
On 26 January 2015 at 17:38, Mark Struberg wrote:
> Sebb, this is nowhere stated in the bylaws. There is just no ground for
> totally blasting a release!
This has come up several times, and the rules are still at:
http://www.apache.org/dev/licensing-howto.html#mod-notice
> It'
On 27 January 2015 at 08:10, Benedikt Ritter wrote:
> 2015-01-25 12:15 GMT+01:00 sebb :
>
>> Hello All,
>>
>> The Apache Commons Parent POM provides common settings for all Apache
>> Commons components.
>>
>>
>> This is a VOTE to release Common
It also fails for me using Java 8 on MacOSX.
I am looking into it now.
On 27 January 2015 at 12:42, sebb wrote:
> On 27 January 2015 at 08:10, Benedikt Ritter wrote:
>> 2015-01-25 12:15 GMT+01:00 sebb :
>>
>>> Hello All,
>>>
>>> The Apache Commons P
be that we will need a CP38 to fix the Java8 issue, but that's
for another day.
On 27 January 2015 at 13:23, Benedikt Ritter wrote:
> 2015-01-27 13:42 GMT+01:00 sebb :
>
>> On 27 January 2015 at 08:10, Benedikt Ritter wrote:
>> > 2015-01-25 12:15 GMT+01:00 sebb :
&
The problem is that Java8 class files include some new constant types
that the currently available release of BCEL cannot handle.
A work-round is to use Java 7 to run Maven when building the site.
On 27 January 2015 at 13:31, sebb wrote:
> It's not CP37 because Java8 also fails w
It's Clirr Report as far as I can tell.
On 27 January 2015 at 14:04, Benedikt Ritter wrote:
> 2015-01-27 14:50 GMT+01:00 sebb :
>
>> The problem is that Java8 class files include some new constant types
>> that the currently available release of BCEL cannot handle.
>>
72 hours have elapsed with no objections, so the lazy consensus vote passes.
The staging repo will be published shortly.
On 27 January 2015 at 14:07, sebb wrote:
> It's Clirr Report as far as I can tell.
>
> On 27 January 2015 at 14:04, Benedikt Ritter wrote:
>> 2015-01-27
Commons Parent 37 has been released.
The main changes are:
* addition of Animal Sniffer (profile: animal-sniffer) which is
enabled by default.
* site-basic profile which disables as many reports etc as possible to
make it easy to test component documentation
* updates to plugin versions
Release
On 28 January 2015 at 20:46, Romain Manni-Bucau wrote:
> Build takes ~15mn on my computer but my hard drive is slow (compared
> to a mac I'm at least twice slower cause of it).
>
> BTW I'll remove aspectj dir on trunk.
>
> About Java 8: while it is javadoc only I think we don't care - in
> particu
e been fixed then, but appears to have been overlooked.
> Le 29 janv. 2015 00:45, "sebb" a écrit :
>
>> On 28 January 2015 at 20:46, Romain Manni-Bucau
>> wrote:
>> > Build takes ~15mn on my computer but my hard drive is slow (compared
>> > to a mac I
On 29 January 2015 at 10:57, Gonçalo Marques
wrote:
> Hello,
>
> I'm creating this thread in order to discuss issue COLLECTIONS-551.
>
> I don't know the deprecation policies of the Commons project in detail, but
> based on the last comment posted by Thomas on issue COLLECTIONS-550 I
> assume that
On 30 January 2015 at 08:20, Stefan Bodewig wrote:
> On 2015-01-28, Benedikt Ritter wrote:
>
>> - PROPOSAL.txt is not in the src archives. Should it be?
>
> This is only there for historical reasons, I don't even think the other
> components still have a file like this. I've removed it completely
On 30 January 2015 at 16:48, Gary Gregory wrote:
> On Fri, Jan 30, 2015 at 6:06 AM, Stefan Bodewig wrote:
>
>> On 2015-01-30, sebb wrote:
>>
>> > On 30 January 2015 at 08:20, Stefan Bodewig wrote:
>> >> On 2015-01-28, Benedikt Ritter wrote:
>>
>
I've just had a look at the new class ZCompressorInputStream.
This has lots of mutable protected fields.
For example,
protected int clearCode = -1;
protected int codeSize = 9;
clearCode has a protected setter, but no getter.
What's the point of that?
As far as I can tell, these are fie
On 30 January 2015 at 17:34, Emmanuel Bourg wrote:
> Le 30/01/2015 17:48, Gary Gregory a écrit :
>
>> Well, we cannot break BC in a minor release for a public class. Are we
>> sure BC breaks?
>>
>> If we want to make this internal package public, it needs to be copied to
>> the new location, not
On 30 January 2015 at 15:41, sebb wrote:
> I've just had a look at the new class ZCompressorInputStream.
Sorry, I meant LZWInputStream
> This has lots of mutable protected fields.
>
> For example,
>
> protected int clearCode = -1;
> protected int codeSiz
On 31 January 2015 at 00:10, sebb wrote:
> On 30 January 2015 at 15:41, sebb wrote:
>> I've just had a look at the new class ZCompressorInputStream.
>
> Sorry, I meant LZWInputStream
Which I just realised is mainly a copy of the internal version. Pity
the SVN history does n
On 31 January 2015 at 09:03, Stefan Bodewig wrote:
> On 2015-01-31, sebb wrote:
>
>> Given that the protected fields were in a class marked as internal, it
>> seems arguable that users should not have referred to any of the items
>> in it.
>> Therefore we could po
On 31 January 2015 at 11:41, Stefan Bodewig wrote:
> On 2015-01-31, sebb wrote:
>
>> On 31 January 2015 at 09:03, Stefan Bodewig wrote:
>>> On 2015-01-31, sebb wrote:
>
>>>> Given that the protected fields were in a class marked as internal, it
>>&g
On 31 January 2015 at 18:40, Gonçalo Marques
wrote:
> Hi,
>
> I've sent a pull request containing CollectionUtils refactor for review
> (COLLECTIONS-551).
>
> Since the next release version is 4.1, I'm wondering if methods that were
> deprecated which are tagged with "@since 4.1" shouldn't be prom
On 1 February 2015 at 18:33, Jochen Wiedmann wrote:
> On Sun, Feb 1, 2015 at 7:04 AM, Stefan Bodewig wrote:
>
>> * (Internal)LZWInputStream has a bunch of protected fields that slipped
>> through a few releases ago. We should add getter/setter pairs and
>> deprecate
I would not wish to move away from Java RE *unless* the RE syntax was
the same *and* the implementation was better performing *and* the
existing code suffered from poor performance.
It might be OK if the alternate implementation was missing some
esoteric features, but I would be very wary of using
On 4 February 2015 at 13:51, Phil Steitz wrote:
> I had to go around getNumIdle to avoid waiting on a this lock in the
> unit test I just committed. With pool 2 and volatile connectionPool
> instance, I don't think this sync is needed any more. Same with the
> sync on getNumActive. Am I missing
There seem to be a few use-cases for pools that always treat different
instances as different entries, rather than using the current equals()
check.
Would it make sense to implement alternative versions that accept an
object and wrap it in a class that implements equals() using == and
System.ident
PM, James Carman
> wrote:
>> Or, you just don't implement equals()/hashCode() and you get that
>> functionality for free, right?
>>
>> On Fri, Feb 6, 2015 at 1:56 PM, sebb wrote:
>>> There seem to be a few use-cases for pools that always treat different
>>
On 6 February 2015 at 19:58, Phil Steitz wrote:
> On 2/6/15 11:56 AM, sebb wrote:
>> There seem to be a few use-cases for pools that always treat different
>> instances as different entries, rather than using the current equals()
>> check.
>
> Yes
>>
&g
On 6 February 2015 at 22:36, Phil Steitz wrote:
> On 2/6/15 1:28 PM, sebb wrote:
>> On 6 February 2015 at 19:58, Phil Steitz wrote:
>>> On 2/6/15 11:56 AM, sebb wrote:
>>>> There seem to be a few use-cases for pools that always treat different
>>>> i
On 8 February 2015 at 16:57, Phil Steitz wrote:
> On 2/8/15 8:51 AM, sebb wrote:
>> On 6 February 2015 at 22:36, Phil Steitz wrote:
>>> On 2/6/15 1:28 PM, sebb wrote:
>>>> On 6 February 2015 at 19:58, Phil Steitz wrote:
>>>>> On 2/6/15 11:56 AM,
On 8 February 2015 at 23:47, wrote:
> Author: ebourg
> Date: Sun Feb 8 23:47:27 2015
> New Revision: 1658276
>
> URL: http://svn.apache.org/r1658276
> Log:
> Added a JMH benchmark to compare the most commons CSV parsers
-1
This has broken the Continuum build.
Also the JMH website says:
"The
On 9 February 2015 at 08:14, Emmanuel Bourg wrote:
> Le 09/02/2015 02:40, sebb a écrit :
>
>> -1
>>
>> This has broken the Continuum build.
>
> I'm going to fix this.
>
>
>> Also the JMH website says:
>>
>> "The recommended way
On 13 February 2015 at 19:12, wrote:
> Author: bodewig
> Date: Fri Feb 13 19:12:09 2015
> New Revision: 1659649
>
> URL: http://svn.apache.org/r1659649
> Log:
> python tarfile library seems to create embedded NULs, COMPRESS-301, unit test
> to follow
-1 (for the moment)
I don't think we have p
On 15 February 2015 at 18:45, Stefan Bodewig wrote:
> On 2015-02-15, sebb wrote:
>
>> On 13 February 2015 at 19:12, wrote:
>>> Author: bodewig
>>> Date: Fri Feb 13 19:12:09 2015
>>> New Revision: 1659649
>
>>> URL: http://svn.apache.org/r1
On 17 February 2015 at 06:13, Benedikt Ritter wrote:
> Hello Peter
>
> 2015-02-15 22:49 GMT+01:00 Peter Ansell :
>
>> On 15 February 2015 at 21:29, Benedikt Ritter wrote:
>>
>>
>> > We like to underline, that we have no experience with the RDF
>> > specification. From a technical point of view w
For completeness, here are the main Nexus hashes:
/org/apache/commons/commons-dbcp2/2.1/commons-dbcp2-2.1-tests.jar
(SHA1: f4463d624c494746aa01f009f0886012f9601710)
/org/apache/commons/commons-dbcp2/2.1/commons-dbcp2-2.1-sources.jar
(SHA1: 305da0aa5f560ab4c8e3bee855582829c51fb744)
/org/apache/comm
On 17 February 2015 at 22:56, Peter Ansell wrote:
> On 17 February 2015 at 21:48, sebb wrote:
>> On 17 February 2015 at 06:13, Benedikt Ritter wrote:
>
>
>
>>> and the maven coordinates when we break binary compatibility (= bump up the
>>> major version n
On 19 February 2015 at 15:19, Benedikt Ritter wrote:
> 2015-02-19 16:14 GMT+01:00 Ben McCann :
>
>> Why do you say users would have to rename all their import statements? Is
>> there a patch pending that we're consider which would change the package
>> name? I don't think there'd be any changes th
ch attention to
binary compatibility either.
>
> (This is a very relevant discussion as another thread was just talking
> about updating https://commons.apache.org/releases/versioning.html to
> relate to SemVer)
>
>
> On 19 February 2015 at 15:38, Emmanuel Bourg wrote:
>
On 20 February 2015 at 01:23, Stian Soiland-Reyes wrote:
> On 19 February 2015 at 18:47, sebb wrote:
>> Not necessarily, my example was about requiring a major bump in JVM version.
>> Still binary compatible, but might require users to upgrade their host JVM.
>> Ther
On 23 February 2015 at 10:35, Benedikt Ritter wrote:
> Hello Phil,
>
> 2015-02-22 21:43 GMT+01:00 :
>
>> Author: psteitz
>> Date: Sun Feb 22 20:43:30 2015
>> New Revision: 1661559
>>
>> URL: http://svn.apache.org/r1661559
>> Log:
>> Added (disabled) tests for JIRA: DBCP-283 and DBCP-284.
>>
>> Mod
On 20 February 2015 at 09:26, wrote:
> Author: rmannibucau
> Date: Fri Feb 20 09:26:12 2015
> New Revision: 8065
>
> Log:
> updating my key
If you have ever signed a Commons release using the previous key then
it must be kept in the file.
i.e. rather than replacing an old key, add the new one.
On 23 February 2015 at 18:39, Benedikt Ritter wrote:
> Hi Romain,
>
> 2015-02-23 19:34 GMT+01:00 Romain Manni-Bucau :
>
>> Hi guys
>>
>> Is there any doc on how to publish a commons site without cms? Basically a
>> scp like would save me this time.
>>
>
> Have a look at [1]. You have build the sit
t;> Thanks guys, will try to do it in the coming 2 days
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau
>> http://www.tomitribe.com
>> http://rmannibucau.wordpress.com
>> https://github.com/rmannibucau
>>
>>
>> 2015-02-23 19:45 GMT+01:00 sebb :
On 24 February 2015 at 08:58, Thomas Neidhart wrote:
> Hi,
>
> I need to update the jenkins configuration for Commons-Math too, but do not
> have the proper rights yet.
> Can I give it to myself as PMC member, as explained here:
> http://wiki.apache.org/general/Jenkins ?
The page says it needs PM
On 24 February 2015 at 17:05, Phil Steitz wrote:
> On 2/23/15 1:21 AM, Mark Thomas wrote:
>> On 22/02/2015 22:27, Thomas Neidhart wrote:
>>> On 02/22/2015 08:18 PM, Mark Thomas wrote:
On 22/02/2015 16:07, Karl Heinz Marbaise wrote:
> Hi,
>
> unfortunately you have to ...I'm doing
Might be worth running a version of the test with JIT disabled.
This will make the test much longer so I suggest first seeing if the
tests fail on their own, and then disable JIT.
You could experiment with the additional Jenkins Math job I set up for
the H10 tests:
https://builds.apache.org/job/Co
On 25 February 2015 at 19:24, Thomas Neidhart wrote:
> On 02/25/2015 04:37 PM, Phil Steitz wrote:
>> Seems a little silly to be spending time debugging openjdk bugs.
>> Can we just set Jenkins up to use an Oracle released JDK?
>
> Yeah sure, it might be a waste of time, it is still annoying to see
On 2 March 2015 at 20:00, Leandro Reis wrote:
> Hi all,
>
> I¹m working on a product that uses Commons IO via Jackrabbit Oak. In the
> process of testing the launch of such product on Japanese Windows 2012
> Server R2, I came across the following exception:
> "(java.io.UnsupportedEncodingException
On 2 March 2015 at 21:33, Gary Gregory wrote:
> I'm all for RERO if the release manager is willing.
RM willingness is only part of it.
RERO is all very well if:
- the API is stable; or
- frequent changes of package name/Maven coords are acceptable to consumers; or
- one does not care about binar
On 5 March 2015 at 05:33, Stefan Bodewig wrote:
> On 2015-03-05, sebb AT ASF wrote:
>
>> <<<
>> git checkout -b release
>> <<<
>
>> I don't understand what "you're on the release branch" means.
>> Is that
On 10 March 2015 at 16:51, henrib wrote:
> Hi;
> I was wondering if any community member would be ready to serve as Release
> Manager for JEXL 3.0?
>
> That 3.0 trunk/fork has been used in production for the past 3 years so it
> can be considered fairly mature & stable. Besides, no-one seems inter
On 12 March 2015 at 01:25, Niall Pemberton wrote:
> On Fri, Mar 6, 2015 at 7:42 PM, sarahkm1972 wrote:
>
>> +100 to RERO. +1000 to release before we're all dead. It's been a decade
>> people. Just cut a release already. You can always cut another one later.
>> Stop with the excuses
>>
>> Whatever
.
> On Wed, Mar 11, 2015 at 7:04 PM, sebb wrote:
>
>> On 12 March 2015 at 01:25, Niall Pemberton
>> wrote:
>> > On Fri, Mar 6, 2015 at 7:42 PM, sarahkm1972
>> wrote:
>> >
>> >> +100 to RERO. +1000 to release before we're all dead. It's
On 13 March 2015 at 20:34, Benedikt Ritter wrote:
> Hooray, the UrlValidator again...
>
> seriously, what are we going to do about this? We can push a new release,
> every time the TLD list gets updated.
It's pretty easy to update the TLD list, but this happens quite frequently.
So we really nee
+1
Makes sense, as they generally relate to JIRAs.
On 18 March 2015 at 07:47, Benedikt Ritter wrote:
> Hi,
>
> as the subjects say: would it be better if the github notifications would
> go to issues@c.a.o ? We had a lot of traffic lately, because I went through
> all the PRs for [lang].
>
> Be
I suggest you create a JIRA enhancement request so this can be tracked properly.
On 5 April 2015 at 11:41, David Goodenough
wrote:
> Currently the code in org.apache.commons.cli.OptionValidator generates an
> IllegalArgumentException which contains the message:-
>
> "illegal option value '" + ch
Also note that Whimsy can update the agenda for you
https://whimsy.apache.org/board/agenda/
No need to send the e-mail as well (the board will see the commit message).
On 8 April 2015 at 09:18, Gary Gregory wrote:
> I've already emailed the report. Good for next time though!
>
> Thank you,
> Ga
I think the problem here is that the Nexus mail is lacking in context.
Other Nexus mails have similar problems, but it is a particular
problem here as a dropped staging repo cannot be inspected for the
missing details!
I raised:
https://issues.apache.org/jira/browse/INFRA-9461
On 14 April 2015 a
udes software from the HumanNameParser.php
>> -(https://github.com/jasonpriem/HumanNameParser.php) library,
>> -under the Apache License 2.0 (see: the o.a.c.t.names package).
>> +This product includes software ported from the HumanNameParser PHP library
>> +(https://github.com/jasonpri
Also, note that commit log messages are not published with the source code.
So please consider adding suitable comments in the source code itself.
The commit log should contain sufficient detail to understand why the
commit was done; the source code needs to contain the detail to
understand the s
On 4 May 2015 at 16:43, luc wrote:
> Le 2015-05-04 14:48, Thomas Neidhart a écrit :
>>
>> Problem still remains, see here:
>> https://builds.apache.org/job/Commons%20Math%20H10/49/console
>>
>> The test failures only occur on the following slaves it seems:
>>
>> * H10
>> * ubuntu-2
>
>
> This lo
Is there any point in keeping the SVN repos for components that have
moved to Git?
They are read-only (or should be) and are not synchronised with the
Git repo, so they can be confusing.
If there is a need to keep them, they should be renamed so people
cannot accidentally use them.
It might be a
The git owner is shown as
owner ARRAY(0x2b87708)
https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=summary
This looks odd.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
Following on from the discussion, here is what I propose.
***The intention is to ensure that the SVN repo is not used by
accident, but still allow users to find the Git repo if they only have
the SVN URL.***
[Note: as part of the move to Git, the SVN repo is made read-only by Infra]
Once the Git
On 9 May 2015 at 13:17, Jochen Wiedmann wrote:
> On Sat, May 9, 2015 at 12:14 PM, Benedikt Ritter wrote:
>> hm, the problem may be, that the scm section of the poms in the pre-git
>> releases point to the svn location.
>
>
> If so, then the project hasn't really migrated to git, has it?
Poms can
I think the first job is to ensure that the build works with Maven2/3,
having tidied up the layout to conform with Maven2/3 conventions
(src/test/java and src/main/java etc).
I see that a start has been made, but it looks like there is some way to go yet.
On 10 May 2015 at 10:48, Bruno P. Kinoshi
As the subject says
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
As the subject says
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On 18 May 2015 at 08:17, wrote:
> Repository: commons-math
> Updated Branches:
> refs/heads/master 241dccdca -> cf571ba2a
>
>
> Fix repository location in doap file
>
>
> Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
> Commit: http://git-wip-us.apache.org/repos/asf/commons-m
On 18 May 2015 at 20:09, Benedikt Ritter wrote:
> 2015-05-18 16:12 GMT+02:00 sebb :
>
>> On 18 May 2015 at 08:17, wrote:
>> > Repository: commons-math
>> > Updated Branches:
>> > refs/heads/master 241dccdca -> cf571ba2a
>>
On 19 May 2015 at 00:45, Phil Steitz wrote:
> On 5/18/15 4:40 PM, ggreg...@apache.org wrote:
>> Author: ggregory
>> Date: Mon May 18 23:40:21 2015
>> New Revision: 1680133
>>
>> URL: http://svn.apache.org/r1680133
>> Log:
>> [POOL-295] Update tests from JUnit 4.11 to 4.12.
>>
>> Modified:
>> c
On 19 May 2015 at 20:28, Benedikt Ritter wrote:
> 2015-05-19 8:24 GMT+02:00 Benedikt Ritter :
>
>>
>>
>> 2015-05-19 2:49 GMT+02:00 sebb :
>>
>>> On 18 May 2015 at 20:09, Benedikt Ritter wrote:
>>> > 2015-05-18 16:12 GMT+02:00 s
On 22 May 2015 at 08:14, Gary Gregory wrote:
> My first inclination is to leave it all as is in this dept. Otherwise, all
> public APIs would be candidate for parameter validation. That would be a
> lot of extra code. The difference being when and what exception is thrown.
>
> It's not clear to me
On 27 May 2015 at 21:05, Stefan Bodewig wrote:
> Hi all
>
> just as a heads up: while test-driving Ant on the latest JDK9 build I
> ran into errors for the tests that uncompressed bzip2 files, so I gave
> Commons Compress a try as well (Ant's bzip2 code base is pretty close to
> the CC one).
>
> I
On 28 May 2015 at 11:46, James Carman wrote:
> I suppose we can't overwrite what's there?
AFAIK, one can just re-release 2.4.
Still needs a vote IMO.
> On Thu, May 28, 2015 at 3:14 AM Mark Thomas wrote:
>
>> Technically we do need a new release vote since:
>>
>> a) The released source will not
On 30 May 2015 at 10:21, Luc Maisonobe wrote:
> Le 30/05/2015 01:35, Phil Steitz a écrit :
>> This is a vote to release version 2.4.1 of Apache Commons Pool based on RC1.
>> Version 2.4.1 is source-identical to 2.4 other than build configuration
>> (pom and findbugs filter). This release is to
On 30 May 2015 at 22:10, Phil Steitz wrote:
> On 5/30/15 2:00 PM, Gary Gregory wrote:
>> On Sat, May 30, 2015 at 1:51 PM, Phil Steitz wrote:
>>
>>> On 5/30/15 1:16 PM, Gary Gregory wrote:
I am wondering if we need an updated build process here.
At work, in a large Ant based project
Similarly for Commons Lang.
The _moved_to_git directory tree is read-only (except as needed when
moving components).
On 9 May 2015 at 13:33, sebb wrote:
> Following on from the discussion, here is what I propose.
>
> ***The intention is to ensure that the SVN repo is not used by
> acciden
I added MovingToGit. The page is not yet complete.
On 11 June 2015 at 19:33, Gary Gregory wrote:
> Thank you Sebb. Do we need to add this process to a wiki page or do we
> already have such a page for future migrations.
>
> Gary
>
> On Thu, Jun 11, 2015 at 11:00 AM, sebb w
Could you create a JIRA issue with a link to the request please?
See https://github.com/apache/commons-lang/blob/master/CONTRIBUTING.md
It's much easier to keep track of the progress of a patch this way.
Thanks!
On 12 June 2015 at 04:52, Chas Honton wrote:
> I just created a pull request for
This is off-topic for the developer list.
Please subscribe to the Commons User list [1] and post there.
Also, please prefix the subject line with:
[MATH]
i.e. in this case the subject should be
[MATH] plot distribution
or similar
[1] http://commons.apache.org/mail-lists.html
and
http://commo
Thanks, have just copied it to the appropriate mailing list
(dev@commons.apache.org)
On 18 June 2015 at 11:29, Laurent Barbareau wrote:
> Hello,
>
> On this page http://commons.apache.org/proper/commons-validator/ there's a
> dead link into the left menu, for the item General Information > Securi
The security link is broken on all the component sites; looks like it
should link to the parent (as per the other links in the same section)
but for some reason it is not.
Investigating.
On 18 June 2015 at 14:45, sebb wrote:
> Thanks, have just copied it to the appropriate mailing list
>
ed
to be fixed.
The simplest way is probably to use a redirect for those sites that need it.
For example, validator and lang.
But not Compress, which has its own security.html page (and uses an
older site.xml without the link)
On 18 June 2015 at 14:47, sebb wrote:
> The security link is broke
Commons Compress has a Security Reports page:
http://commons.apache.org/proper/commons-compress/security.html
which contains details of known security issues.
The page links to the general commons security page
http://commons.apache.org/security.html
for details of how to report security issues.
On 19 June 2015 at 19:00, wrote:
> Author: krosenvold
> Date: Fri Jun 19 18:00:44 2015
> New Revision: 1686472
>
> URL: http://svn.apache.org/r1686472
> Log:
> IO-452 broken symlink support
>
> Patch by David Standish.
>
> Also added reflection-based java7 symlink support from maven code (origina
On 20 June 2015 at 06:39, Kristian Rosenvold
wrote:
> 2015-06-19 21:01 GMT+02:00 sebb :
>
>> On 19 June 2015 at 19:00, wrote:
>> > +class Java7Support
>> > +{
>> > +
>> > +private static final boolean IS_JAVA7;
>> > +
>> > +
Oops, sorry about that.
Not sure why I overlooked that the test code needs package access.
On 20 June 2015 at 09:36, Kristian Rosenvold wrote:
> I reverted some of the package protected -> private changes, since the
> tests did not even compile with this change.
>
> Kristian
---
The Javadoc for the two constructors says:
>>
org.apache.commons.io.input.BrokenInputStream.BrokenInputStream(IOException
exception)
Creates a new stream that always throws the given exception.
Parameters:
exception the exception to be thrown
<<
and
>>
org.apache.commons.io.input.BrokenInputSt
On 21 June 2015 at 13:24, Kristian Rosenvold
wrote:
> 2015-06-21 13:43 GMT+02:00 sebb :
>
>>
>> > I'm not sure I understand; the equivalent of
>> >
>> > Boolean result = (Boolean) isSymbolicLink.invoke(null, path);
>> > return result.boolea
On 21 June 2015 at 14:16, Kristian Rosenvold
wrote:
> 2015-06-21 14:53 GMT+02:00 sebb :
>
>> On 21 June 2015 at 13:24, Kristian Rosenvold
>> wrote:
>> > 2015-06-21 13:43 GMT+02:00 sebb :
>> >
>> >>
>> >> > I'm not sure I und
Hello All,
The Apache Commons Parent POM provides common settings for all Apache
Commons components.
This is a VOTE to release Commons Parent 38 from RC2.
The main reason for this release is to fix the bug in site.xml
discovered recently.
This VOTE by LAZY-CONSENSUS is open for at least 72 hou
I wonder whether the current directory layout is the most convenient.
At present, binaries and source are held in separate areas, and all
versions of each type are combined.
I think it might simplify matters to use a single directory per
version, with both source and binary together.
The current
On 21 June 2015 at 19:44, wrote:
> Author: krosenvold
> Date: Sun Jun 21 18:44:49 2015
> New Revision: 1686747
>
> URL: http://svn.apache.org/r1686747
> Log:
> Fixed all checkstyle errors and a findbugs error
>
What was the Findbugs error?
Best not to mix these in a single commit.
Also looks l
The Math download page still lists 2.2 (Java 1.5+)
However it also lists 3.5 (Java 1.5+)
Do we really still intend to develop the 2.x line?
If not, it ought to be removed from the download page and the mirrors.
There are also a lot of other old Math3 versions on the mirrors.
The Math RMs have n
The default karma needed for committing to the SVN dist/release/TLP
areas is membership of the LDAP PMC group. This can be changed to be
membership of the LDAP committer group if required.
I'm not sure about the current karma needed for Nexus upload, it may
be either PMC or committer membership.
On 23 June 2015 at 14:42, Jochen Wiedmann wrote:
> -1 for existing stuff.
There would be no need to change existing releases.
It could be introduced for new releases only.
> I don't see any need to spend work on breaking things.
>
> +0 for new stuff
>
> I don't see any real advantages.
The curr
1101 - 1200 of 6436 matches
Mail list logo
