Re: [collections] Preparing a 4.1 release
On 05/24/2015 05:52 PM, Gary Gregory wrote: Why not just move to Java 7? The reason to move to Java 6 is to add support for NavigableMap, which unfortunately is missing right now. Moving to Java 7 is not really necessary, the next logical move would be to Java 8 imho. In fact it would be worthwhile to have a separate collections component that targets Java 8 but for this we are clearly lacking the manpower / interest from the community. Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
RE: [collections] Preparing a 4.1 release
Why not just move to Java 7? Gary Original message From: Thomas Neidhart thomas.neidh...@gmail.com Date: 05/23/2015 02:17 (GMT-08:00) To: Commons Developers List dev@commons.apache.org Subject: [collections] Preparing a 4.1 release Hi, in the next few weeks I will hopefully finish all open issues for an upcoming 4.1 release. Note: the release will also update the minimum required java version to 1.6. Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [jelly] Working on some old issues
On Sun, May 24, 2015 at 7:52 AM, Bruno P. Kinoshita brunodepau...@yahoo.com.br wrote: Hi Nial Do you know why your branch wasn't merged? I dont really remember. I'm not sure whether all issues were resolved (perhaps around tags doc generation). I sent the following email at the start of 2010 - but I did some more work after that email: * http://markmail.org/message/yveew57uparj3aab I think the main reason though was that jelly was petty dormant and there was no real interest. Niall I've checked it out and a few tests are failing with Maven 3.2.5 and Java 7 8. But I'd like to use your branch, try to fix any failing tests and merge back onto trunk. Created https://issues.apache.org/jira/browse/JELLY-291 to track this issue. Thanks!Bruno From: Niall Pemberton niall.pember...@gmail.com To: Commons Developers List dev@commons.apache.org Cc: Bruno P. Kinoshita brunodepau...@yahoo.com.br Sent: Monday, May 11, 2015 3:36 AM Subject: Re: [jelly] Working on some old issues On Sun, May 10, 2015 at 3:19 PM, sebb seb...@gmail.com wrote: 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 worked on a maven branch back in 2010 here: https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH Niall 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. Kinoshita brunodepau...@yahoo.com.br wrote: Hi Paul if I remember well how the patches of Kohsuke landed, I remember I was unable to apply them because they seemed to be breaking some of the standard command-line jelly. I think I remember that a pluggeable context was discussed but, maybe, was not developed. Any kind of background on old issues is welcome! Before I start to work on any issue, I'll triage old issues, try to find some low hanging fruits, and then will start a one or two dayresearch on the mailing list to see if I can learn as much as possible before coding. I have not been able to save cycles to address more issues of Jelly and I know of some other folks, fellows in research in learning technology, that were, looking forward to getting more releases of jelly at the time I met them. I will work a little bit every weekend on triage issues, but will have a one or two week cyclein the middle of June and in July (lovely weather for coding; cold, cloudy, and raining a lot :) Hope it helps. I am happy to help you if I can towards making it better. It definitely helps. Very happy for having someone I can ask questions about some old issuesin [jelly] :) ThanksBruno From: Paul Libbrecht p...@hoplahup.net To: Commons Developers List dev@commons.apache.org Sent: Sunday, May 3, 2015 8:33 AM Subject: Re: [jelly] Working on some old issues On 1/05/15 10:22, Bruno P. Kinoshita wrote: Since I joined Commons I've had a special interest in [jelly] due to its importance in the Jenkins project. Jenkins uses a patched version of [jelly]. Kohsuke, creator of Jenkins, is/was a Commons committer too, and submitted some issues. I intend to investigate if that'd be doable fix the issues to a point that Jenkins can drop the patched version, and [jelly] can be updated and released again. Hello Bruno, if I remember well how the patches of Kohsuke landed, I remember I was unable to apply them because they seemed to be breaking some of the standard command-line jelly. I think I remember that a pluggeable context was discussed but, maybe, was not developed. Thus, I can only encourage you to go ahead. I think it would be nice to have both worlds working well with a single code base. I have not been able to save cycles to address more issues of Jelly and I know of some other folks, fellows in research in learning technology, that were, looking forward to getting more releases of jelly at the time I met them. Hope it helps. I am happy to help you if I can towards making it better. paul
Re: [collections] Preparing a 4.1 release
That all makes sense. Thanks for the clarification. Gary On Sun, May 24, 2015 at 10:37 AM, Thomas Neidhart thomas.neidh...@gmail.com wrote: On 05/24/2015 05:52 PM, Gary Gregory wrote: Why not just move to Java 7? The reason to move to Java 6 is to add support for NavigableMap, which unfortunately is missing right now. Moving to Java 7 is not really necessary, the next logical move would be to Java 8 imho. In fact it would be worthwhile to have a separate collections component that targets Java 8 but for this we are clearly lacking the manpower / interest from the community. Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: [jelly] Working on some old issues
Hi Nial Do you know why your branch wasn't merged? I've checked it out and a few tests are failing with Maven 3.2.5 and Java 7 8. But I'd like to use your branch, try to fix any failing tests and merge back onto trunk. Created https://issues.apache.org/jira/browse/JELLY-291 to track this issue. Thanks!Bruno From: Niall Pemberton niall.pember...@gmail.com To: Commons Developers List dev@commons.apache.org Cc: Bruno P. Kinoshita brunodepau...@yahoo.com.br Sent: Monday, May 11, 2015 3:36 AM Subject: Re: [jelly] Working on some old issues On Sun, May 10, 2015 at 3:19 PM, sebb seb...@gmail.com wrote: 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 worked on a maven branch back in 2010 here: https://svn.apache.org/repos/asf/commons/proper/jelly/branches/MAVEN-2-BRANCH Niall 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. Kinoshita brunodepau...@yahoo.com.br wrote: Hi Paul if I remember well how the patches of Kohsuke landed, I remember I was unable to apply them because they seemed to be breaking some of the standard command-line jelly. I think I remember that a pluggeable context was discussed but, maybe, was not developed. Any kind of background on old issues is welcome! Before I start to work on any issue, I'll triage old issues, try to find some low hanging fruits, and then will start a one or two dayresearch on the mailing list to see if I can learn as much as possible before coding. I have not been able to save cycles to address more issues of Jelly and I know of some other folks, fellows in research in learning technology, that were, looking forward to getting more releases of jelly at the time I met them. I will work a little bit every weekend on triage issues, but will have a one or two week cyclein the middle of June and in July (lovely weather for coding; cold, cloudy, and raining a lot :) Hope it helps. I am happy to help you if I can towards making it better. It definitely helps. Very happy for having someone I can ask questions about some old issuesin [jelly] :) ThanksBruno From: Paul Libbrecht p...@hoplahup.net To: Commons Developers List dev@commons.apache.org Sent: Sunday, May 3, 2015 8:33 AM Subject: Re: [jelly] Working on some old issues On 1/05/15 10:22, Bruno P. Kinoshita wrote: Since I joined Commons I've had a special interest in [jelly] due to its importance in the Jenkins project. Jenkins uses a patched version of [jelly]. Kohsuke, creator of Jenkins, is/was a Commons committer too, and submitted some issues. I intend to investigate if that'd be doable fix the issues to a point that Jenkins can drop the patched version, and [jelly] can be updated and released again. Hello Bruno, if I remember well how the patches of Kohsuke landed, I remember I was unable to apply them because they seemed to be breaking some of the standard command-line jelly. I think I remember that a pluggeable context was discussed but, maybe, was not developed. Thus, I can only encourage you to go ahead. I think it would be nice to have both worlds working well with a single code base. I have not been able to save cycles to address more issues of Jelly and I know of some other folks, fellows in research in learning technology, that were, looking forward to getting more releases of jelly at the time I met them. Hope it helps. I am happy to help you if I can towards making it better. paul
