Re: [JCS] release?

java 7 doesn't bring any important enough feature to force the work it implies from what I saw (all it brings is done by IDEs since years) so i wouldn't consider it as something to do. Moreover I think we need java 6 for still 1/1.5 years. Will be another story for java 8 for sure since features ar

Re: [JCS] release?

Java 6 reached EOF. I have recently switched from 6 to 7 in a personal project because I really wanted to try the new features, like try-with-resources. The transition was a walk in the park. I think that you should go for Java 7. It is time to move on and leave behind the legacy versions. On Wed,

Re: [JCS] release?

Random thought: Any consideration on raising the floor to Java 7? We could use DBCP 2.x that way. try-with-resources as well, and so on. Gary On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau wrote: > Hello guys, > > seems we are good regarding dependencies now > > do we try a release this we

Re: [JCS] release?

Frak, why can't I get mvn clirr:clirr to create a report? I've force fed the GAV too: Index: pom.xml === --- pom.xml(revision 1631929) +++ pom.xml(working copy) @@ -26,7 +26,8 @@ 34 - commons-jcs + org.apache.comm

Re: [JCS] release?

Hm... the following should work (as a test at least) but does not: Index: pom.xml === --- pom.xml(revision 1631900) +++ pom.xml(working copy) @@ -26,7 +26,8 @@ 34 - commons-jcs + org.apache.commons + commons-jcs-p

Re: [JCS] release?

If I change to POMs to use org.apache.jcs|jcs for the parent POM and org.apache.jcs|jcs as the parent of the modules, I get no reports from "mvn clirr:check" of course since org.apache.jcs|jcs is now a POM POM (!) in JCS 2.0 as opposed to a Jar POM in 1.3. Gary On Tue, Oct 14, 2014 at 7:29 PM, Ga

Re: [JCS] release?

[Sebb: I added you to this discussion as I am not sure how to get JCS 2.0 to have the same Maven coors as 1.3 since it is now a multi-module project]. So it sounds like we should change the Maven coords to what they were for 1.3. But 1.3 was one jar and one POM ( http://search.maven.org/#artifact

[continuum] BUILD FAILURE: Apache Commons JCS - Apache Commons (Group (shared) Maven 3 Build Definition (Java 1.6))

Online report : https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38333&projectId=286 Build statistics: State: Failed Previous State: Failed Started at: Tue 14 Oct 2014 23:20:28 + Finished at: Tue 14 Oct 2014 23:25:23 + Total time: 4m 55s Build Trigger: Sche

Re: [JCS] release?

about api: public api shouldn't be broken (well the one which is broken shouldn't be used in code but only in config/properties files). about logging: we stated we'll not switch now but that we'll tackle it for 2.0.0. If we want log4j2 as default I'll fight to get a facade since jcs is already int

[continuum] BUILD FAILURE: Apache Commons JCS - Apache Commons (Group (shared) Maven 3 Build Definition (Java 1.6))

Online report : https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38330&projectId=286 Build statistics: State: Failed Previous State: Failed Started at: Tue 14 Oct 2014 22:20:28 + Finished at: Tue 14 Oct 2014 22:25:23 + Total time: 4m 54s Build Trigger: Sche

Re: [JCS] release?

Now that Log4j 2 (2.0.2) is out and can be considered to deprecate Commons Logging since it provides a nice API module, should we switch to it? Gary On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau wrote: > Hello guys, > > seems we are good regarding dependencies now > > do we try a release

Re: [JCS] release?

Wow, that must have been a random problem... all tests pass from Maven now... Gary On Tue, Oct 14, 2014 at 4:47 PM, Romain Manni-Bucau wrote: > even running them one by one? > > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.com > https://github.co

Re: [JCS] release?

On Tue, Oct 14, 2014 at 5:26 PM, Romain Manni-Bucau wrote: > 2014-10-14 23:22 GMT+02:00 Gary Gregory : > > The package name and Maven coords must be kept in sync to avoid jar hell. > > > > You cannot change one without changing the other. > > > > If 2.0 is to be compatible with 1.3, then the same

Re: [JCS] release?

2014-10-14 23:22 GMT+02:00 Gary Gregory : > The package name and Maven coords must be kept in sync to avoid jar hell. > > You cannot change one without changing the other. > > If 2.0 is to be compatible with 1.3, then the same Maven coords must be > kept. Well that's where it is ambiguous. It is w

[continuum] BUILD FAILURE: Apache Commons JCS - Apache Commons (Group (shared) Maven 3 Build Definition (Java 1.6))

Online report : https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38327&projectId=286 Build statistics: State: Failed Previous State: Failed Started at: Tue 14 Oct 2014 21:20:26 + Finished at: Tue 14 Oct 2014 21:26:12 + Total time: 5m 46s Build Trigger: Sche

Re: [JCS] release?

Not a blocker, but unsurprisingly Java 8 cannot be used to build due to the well-known new Javadoc doclint feature causing many Javadoc errors. Gary On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau wrote: > Hello guys, > > seems we are good regarding dependencies now > > do we try a release

Re: [JCS] release?

The package name and Maven coords must be kept in sync to avoid jar hell. You cannot change one without changing the other. If 2.0 is to be compatible with 1.3, then the same Maven coords must be kept. If 2.0 is not binary compatible, then you must change the package and and Maven coords. That'

Re: [JCS] release?

surefire is configured to fork for each test. If you change it then it fails with maven as well. That's surely the cause Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-10-14 23:13 GMT+02:00 Gary Gregory : > All sort

Re: [JCS] release?

Well coord changed for multiple reasons IIRC: 1) be aligned with commons projects 2) we upgraded to 2 (for binary + jcache reasons) so it seemd the moment to accept such a change 3) we upgraded to java 6 IIRC 4) project structure changed That said if you replace old jcs coord by commons-jcs-core

Re: [JCS] release?

All sorts of tests fail from Eclipse: commons-jcs-core TestSuite with 5 tests [example: testIndexedDiskCache1(org.apache.commons.jcs.auxiliary.disk.indexed.IndexedDiskCacheSameRegionConcurrentUnitTest$1)] testIndexedDiskCache1(org.apache.commons.jcs.auxiliary.disk.indexed.IndexedDiskCacheSameRegio

Re: [JCS] release?

It looks like the Maven coords have changed which means the package name must change, probably to ...jcs2, which means the artifact ID could probably stand to be post-fixed with a 2 as well. Did the Maven coords change because version 2 breaks binary compatibility with 1.3? Gary On Tue, Oct 14,

Re: [JCS] release?

I can, but only after you get the build to run successfully ;-) Gary On Tue, Oct 14, 2014 at 4:41 PM, Romain Manni-Bucau wrote: > while the build is not broken +1, who takes the lead on it? @Gary? > > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.

Re: [JCS] release?

I can handle rat Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-10-14 22:52 GMT+02:00 Gary Gregory : > RAT reports problems which must be addressed one way or another... > > Gary > > On Tue, Oct 14, 2014 at 4:23 PM,

Jenkins build is back to stable : commons-jcs #40

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Jenkins build is back to stable : commons-jcs » Apache Commons JCS :: Core #40

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [JCS] release?

RAT reports problems which must be addressed one way or another... Gary On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau wrote: > Hello guys, > > seems we are good regarding dependencies now > > do we try a release this week? 2.0-alpha-1? Anything blocking? > > > Romain Manni-Bucau > @rmanni

Re: [JCS] release?

even running them one by one? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-10-14 22:44 GMT+02:00 Gary Gregory : > When I run "mvn clean test" I get: > > Tests in error: > BasicRemoteCacheClientServerUnitTest.test

Re: [JCS] release?

When I run "mvn clean test" I get: Tests in error: BasicRemoteCacheClientServerUnitTest.test1SinglePut:133 NoClassDefFound org/ap... BasicRemoteCacheClientServerUnitTest.test2PutRemove:181 NoClassDefFound org/ap... BasicRemoteCacheClientServerUnitTest.test3PutAndListen:238 NoClassDefFound or

Re: [JCS] release?

while the build is not broken +1, who takes the lead on it? @Gary? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-10-14 22:38 GMT+02:00 Gary Gregory : > A quick glance shows a lot of old versions of dependencies. Sin

Re: [JCS] release?

A quick glance shows a lot of old versions of dependencies. Since we are now on Java 6, it seems like there would be no issue updating all of these. Gary On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau wrote: > Hello guys, > > seems we are good regarding dependencies now > > do we try a rel

[JCS] release?

Hello guys, seems we are good regarding dependencies now do we try a release this week? 2.0-alpha-1? Anything blocking? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau -

Re: [math] pull request

On 10/14/2014 02:13 PM, Emmanuel Bourg wrote: Le 14/10/2014 20:14, Ole Ersoy a écrit : It just occurred to me to go to https://github.com/apache/commons-math to see whether the pull requests are visible. It also looks like github combines all my commits into one pull request. I assumed that

Re: [math] pull request

Le 14/10/2014 20:14, Ole Ersoy a écrit : > It just occurred to me to go to https://github.com/apache/commons-math > to see whether the pull requests are visible. It also looks like github > combines all my commits into one pull request. I assumed that I had to > do them individually. So if this

Re: [math] pull request

On 10/14/2014 12:32 PM, Luc Maisonobe wrote: Le 14/10/2014 17:46, Ole Ersoy a écrit : Hi, I have 1 open pull request for MathIllegalStateException (Simple update to description - Gilles approved) that has been sitting for a while, so I just wanted to make sure it's visible. I tried creating

Re: [math] pull request

Le 14/10/2014 17:46, Ole Ersoy a écrit : > Hi, > > I have 1 open pull request for MathIllegalStateException (Simple update > to description - Gilles approved) that has been sitting for a while, so > I just wanted to make sure it's visible. I tried creating another for I forgot about it, sorry. C

Re: [math] Include quartiles estimated using PSquarePercentile in SummaryStatistics

Many Thanks Phil, for answering all my questions. On Tue, Oct 14, 2014 at 10:19 PM, Phil Steitz wrote: > On 10/14/14 6:59 AM, venkatesha murthy wrote: > > ok. > > > > Wanted to understand advantage of having a container class for all > > storeless stats (just as DescriptiveStats is for Univariat

Re: [math] Include quartiles estimated using PSquarePercentile in SummaryStatistics

On 10/14/14 6:59 AM, venkatesha murthy wrote: > ok. > > Wanted to understand advantage of having a container class for all > storeless stats (just as DescriptiveStats is for Univariate). I could open > another email thread. SummaryStatistics is a container for storeless stats, DescriptiveStatistic

[math] pull request

Hi, I have 1 open pull request for MathIllegalStateException (Simple update to description - Gilles approved) that has been sitting for a while, so I just wanted to make sure it's visible. I tried creating another for the AbstractIntegerDistributionTest, but github does not enable any buttons

Re: [math] Include quartiles estimated using PSquarePercentile in SummaryStatistics

ok. Wanted to understand advantage of having a container class for all storeless stats (just as DescriptiveStats is for Univariate). I could open another email thread. Also wanted to understand whats a abstract interface problem that you were refering thanks murthy On Tue, Oct 14, 2014 at 9:47 A

Re: [math] GitHub vs ASF Repo

Le 2014-10-14 15:16, Hank Grabowski a écrit : Should I try an experiment with that with those interpolator changes I put the diff into JIRA for and remove that flle from the JIRA issue or is the process of using that diff already underway so it would create more brain daamge than it was worth?

Re: [lang] LANG-975

On 14 October 2014 14:07, Duncan Jones wrote: > On 9 October 2014 19:17, Benedikt Ritter wrote: >> I'm not fond that we need this method. However you're raising a good point. >> BooleanUtils only "talks" english. It understands "yes" and "no" but not >> "ja" and "nein" or "oui" and "non". It woul

Re: [math] GitHub vs ASF Repo

Should I try an experiment with that with those interpolator changes I put the diff into JIRA for and remove that flle from the JIRA issue or is the process of using that diff already underway so it would create more brain daamge than it was worth? On Tue, Oct 14, 2014 at 9:12 AM, luc wrote: > H

Re: [math] GitHub vs ASF Repo

Hi Hank, Le 2014-10-14 15:01, Gilles a écrit : On Tue, 14 Oct 2014 08:36:07 -0400, Hank Grabowski wrote: It seems that the GitHub repository is now staying in sync with the ASF repository. Is the preferred workflow going to be (or already is) forking inside of GitHub and then doing pull reque

Re: [lang] LANG-975

On 9 October 2014 19:17, Benedikt Ritter wrote: > I'm not fond that we need this method. However you're raising a good point. > BooleanUtils only "talks" english. It understands "yes" and "no" but not > "ja" and "nein" or "oui" and "non". It would be nice to have a possibilty > to make the toBoole

Re: [math] GitHub vs ASF Repo

On Tue, 14 Oct 2014 08:36:07 -0400, Hank Grabowski wrote: It seems that the GitHub repository is now staying in sync with the ASF repository. Is the preferred workflow going to be (or already is) forking inside of GitHub and then doing pull requests or will the workflow be to work directly wit

[math] GitHub vs ASF Repo

It seems that the GitHub repository is now staying in sync with the ASF repository. Is the preferred workflow going to be (or already is) forking inside of GitHub and then doing pull requests or will the workflow be to work directly with ASF? For someone like me with only read only access to the