Re: Tapestry 5.3.x and Java 8
Yes, JDK 8 will largely eliminate the need for tapestry-func, which is OK ... likewise, a lot of the existing code could be tightened up (and performance possibly improved) using the functional programming capabilities in JDK 8. On Sun, Feb 2, 2014 at 1:53 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: Voted. Also added a comment to do the same for 5.3.x On Feb 2, 2014, at 11:29 AM, Bob Harner wrote: Lenny, you add your name to the demand list by voting on the issue at https://issues.apache.org/jira/browse/TAP5-2214 I've been playing with JDK 8 some myself and see a lot in there that Tapestry could benefit from. At some point (but not soon) we may need a JDK 8-specific branch to introduce API changes for lambda expressions, default methods, and other cool new toys. On Feb 1, 2014 12:35 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: Thanks Bob for the explanation. You can put my name of the list of 'demand' for this. I am pretty sure that when JDK8 starts breaking T5.3, there will be a lot more 'demanders' On Feb 1, 2014, at 11:16 AM, Bob Harner wrote: Lenny, As for whether ASM will be upgraded in the next version of 5.3, I don't see why not, if there is any demand for it. All the developer focus has been on 5.4, of course, so currently there doesn't seem to be a need for any 5.3.8 release. As always, that can change. As I understand it, ASM is baked in with a modified package name so that there isn't a risk of class conflicts with any other occurrences of ASM in users' applications and libraries such as Hibernate. Read the last sentence at http://asm.ow2.org/doc/faq.html On Fri, Jan 31, 2014 at 5:42 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: I am trying to find out about 5.3 specifically, not 5.4. I am sure that 5.4 is going to be upgraded to ASM that's compatible with Java 8 at some point, but our projects are using 5.3, and we don't plan to upgrade to 5.4 for various reasons. So, if there are no plans for upgrading 5.3 to the new ASM, we need to think about alternate plans ahead of time. Also, is there a particular reason why ASM is 'baked in' to plastic, as opposed to just having a separate maven / gradle dependency on it? Seems to be much easier to upgrade if it's a regular dependency rather than jarjar'd. On Jan 31, 2014, at 2:04 PM, Joachim Van der Auwera wrote: I am currently using Tapestry 5.4 on Java8 by applying the patch given in https://issues.apache.org/jira/browse/TAP5-2214. I have not (yet) found other issues when using Java8. Personally, I would like to see this patch applied, but I understand that including a non-release version of ASM is not ideal. Kind regards, Joachim On 01/31/2014 07:44 PM, Lenny Primak wrote: Is there a plan to update 5.3.x when Java 8 comes out? Is it just the matter of the version of ASM that is used or is there something else that precludes 5.3.x to run on Java 8? Thanks - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
Re: Tapestry 5.3.x and Java 8
Lenny, you add your name to the demand list by voting on the issue at https://issues.apache.org/jira/browse/TAP5-2214 I've been playing with JDK 8 some myself and see a lot in there that Tapestry could benefit from. At some point (but not soon) we may need a JDK 8-specific branch to introduce API changes for lambda expressions, default methods, and other cool new toys. On Feb 1, 2014 12:35 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: Thanks Bob for the explanation. You can put my name of the list of 'demand' for this. I am pretty sure that when JDK8 starts breaking T5.3, there will be a lot more 'demanders' On Feb 1, 2014, at 11:16 AM, Bob Harner wrote: Lenny, As for whether ASM will be upgraded in the next version of 5.3, I don't see why not, if there is any demand for it. All the developer focus has been on 5.4, of course, so currently there doesn't seem to be a need for any 5.3.8 release. As always, that can change. As I understand it, ASM is baked in with a modified package name so that there isn't a risk of class conflicts with any other occurrences of ASM in users' applications and libraries such as Hibernate. Read the last sentence at http://asm.ow2.org/doc/faq.html On Fri, Jan 31, 2014 at 5:42 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: I am trying to find out about 5.3 specifically, not 5.4. I am sure that 5.4 is going to be upgraded to ASM that's compatible with Java 8 at some point, but our projects are using 5.3, and we don't plan to upgrade to 5.4 for various reasons. So, if there are no plans for upgrading 5.3 to the new ASM, we need to think about alternate plans ahead of time. Also, is there a particular reason why ASM is 'baked in' to plastic, as opposed to just having a separate maven / gradle dependency on it? Seems to be much easier to upgrade if it's a regular dependency rather than jarjar'd. On Jan 31, 2014, at 2:04 PM, Joachim Van der Auwera wrote: I am currently using Tapestry 5.4 on Java8 by applying the patch given in https://issues.apache.org/jira/browse/TAP5-2214. I have not (yet) found other issues when using Java8. Personally, I would like to see this patch applied, but I understand that including a non-release version of ASM is not ideal. Kind regards, Joachim On 01/31/2014 07:44 PM, Lenny Primak wrote: Is there a plan to update 5.3.x when Java 8 comes out? Is it just the matter of the version of ASM that is used or is there something else that precludes 5.3.x to run on Java 8? Thanks - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry 5.3.x and Java 8
Voted. Also added a comment to do the same for 5.3.x On Feb 2, 2014, at 11:29 AM, Bob Harner wrote: Lenny, you add your name to the demand list by voting on the issue at https://issues.apache.org/jira/browse/TAP5-2214 I've been playing with JDK 8 some myself and see a lot in there that Tapestry could benefit from. At some point (but not soon) we may need a JDK 8-specific branch to introduce API changes for lambda expressions, default methods, and other cool new toys. On Feb 1, 2014 12:35 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: Thanks Bob for the explanation. You can put my name of the list of 'demand' for this. I am pretty sure that when JDK8 starts breaking T5.3, there will be a lot more 'demanders' On Feb 1, 2014, at 11:16 AM, Bob Harner wrote: Lenny, As for whether ASM will be upgraded in the next version of 5.3, I don't see why not, if there is any demand for it. All the developer focus has been on 5.4, of course, so currently there doesn't seem to be a need for any 5.3.8 release. As always, that can change. As I understand it, ASM is baked in with a modified package name so that there isn't a risk of class conflicts with any other occurrences of ASM in users' applications and libraries such as Hibernate. Read the last sentence at http://asm.ow2.org/doc/faq.html On Fri, Jan 31, 2014 at 5:42 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: I am trying to find out about 5.3 specifically, not 5.4. I am sure that 5.4 is going to be upgraded to ASM that's compatible with Java 8 at some point, but our projects are using 5.3, and we don't plan to upgrade to 5.4 for various reasons. So, if there are no plans for upgrading 5.3 to the new ASM, we need to think about alternate plans ahead of time. Also, is there a particular reason why ASM is 'baked in' to plastic, as opposed to just having a separate maven / gradle dependency on it? Seems to be much easier to upgrade if it's a regular dependency rather than jarjar'd. On Jan 31, 2014, at 2:04 PM, Joachim Van der Auwera wrote: I am currently using Tapestry 5.4 on Java8 by applying the patch given in https://issues.apache.org/jira/browse/TAP5-2214. I have not (yet) found other issues when using Java8. Personally, I would like to see this patch applied, but I understand that including a non-release version of ASM is not ideal. Kind regards, Joachim On 01/31/2014 07:44 PM, Lenny Primak wrote: Is there a plan to update 5.3.x when Java 8 comes out? Is it just the matter of the version of ASM that is used or is there something else that precludes 5.3.x to run on Java 8? Thanks - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry 5.3.x and Java 8
Lenny, As for whether ASM will be upgraded in the next version of 5.3, I don't see why not, if there is any demand for it. All the developer focus has been on 5.4, of course, so currently there doesn't seem to be a need for any 5.3.8 release. As always, that can change. As I understand it, ASM is baked in with a modified package name so that there isn't a risk of class conflicts with any other occurrences of ASM in users' applications and libraries such as Hibernate. Read the last sentence at http://asm.ow2.org/doc/faq.html On Fri, Jan 31, 2014 at 5:42 PM, Lenny Primak lpri...@hope.nyc.ny.us wrote: I am trying to find out about 5.3 specifically, not 5.4. I am sure that 5.4 is going to be upgraded to ASM that's compatible with Java 8 at some point, but our projects are using 5.3, and we don't plan to upgrade to 5.4 for various reasons. So, if there are no plans for upgrading 5.3 to the new ASM, we need to think about alternate plans ahead of time. Also, is there a particular reason why ASM is 'baked in' to plastic, as opposed to just having a separate maven / gradle dependency on it? Seems to be much easier to upgrade if it's a regular dependency rather than jarjar'd. On Jan 31, 2014, at 2:04 PM, Joachim Van der Auwera wrote: I am currently using Tapestry 5.4 on Java8 by applying the patch given in https://issues.apache.org/jira/browse/TAP5-2214. I have not (yet) found other issues when using Java8. Personally, I would like to see this patch applied, but I understand that including a non-release version of ASM is not ideal. Kind regards, Joachim On 01/31/2014 07:44 PM, Lenny Primak wrote: Is there a plan to update 5.3.x when Java 8 comes out? Is it just the matter of the version of ASM that is used or is there something else that precludes 5.3.x to run on Java 8? Thanks - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry 5.3.x and Java 8
On Sat, 01 Feb 2014 15:34:36 -0200, Lenny Primak lpri...@hope.nyc.ny.us wrote: Thanks Bob for the explanation. You can put my name of the list of 'demand' for this. I am pretty sure that when JDK8 starts breaking T5.3, there will be a lot more 'demanders' Then we do a new 5.3.x release to fix this issue. :) -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Tapestry 5.3.x and Java 8
Is there a plan to update 5.3.x when Java 8 comes out? Is it just the matter of the version of ASM that is used or is there something else that precludes 5.3.x to run on Java 8? Thanks - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry 5.3.x and Java 8
I am currently using Tapestry 5.4 on Java8 by applying the patch given in https://issues.apache.org/jira/browse/TAP5-2214. I have not (yet) found other issues when using Java8. Personally, I would like to see this patch applied, but I understand that including a non-release version of ASM is not ideal. Kind regards, Joachim On 01/31/2014 07:44 PM, Lenny Primak wrote: Is there a plan to update 5.3.x when Java 8 comes out? Is it just the matter of the version of ASM that is used or is there something else that precludes 5.3.x to run on Java 8? Thanks - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry 5.3.x and Java 8
On Fri, 31 Jan 2014 17:04:57 -0200, Joachim Van der Auwera li...@progs.be wrote: I am currently using Tapestry 5.4 on Java8 by applying the patch given in https://issues.apache.org/jira/browse/TAP5-2214. I have not (yet) found other issues when using Java8. Personally, I would like to see this patch applied, but I understand that including a non-release version of ASM is not ideal. The ASM team announced some time ago they will only release a non-alpha, non-beta version supporting Java 8 after Java 8 is officially released. I'm also eager to use Java 8, but, as Joachim mentioned, it's at least a little bit dangerous for Tapestry to rely on an alpha version of any of its dependencies. -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Tapestry 5.3.x and Java 8
I am trying to find out about 5.3 specifically, not 5.4. I am sure that 5.4 is going to be upgraded to ASM that's compatible with Java 8 at some point, but our projects are using 5.3, and we don't plan to upgrade to 5.4 for various reasons. So, if there are no plans for upgrading 5.3 to the new ASM, we need to think about alternate plans ahead of time. Also, is there a particular reason why ASM is 'baked in' to plastic, as opposed to just having a separate maven / gradle dependency on it? Seems to be much easier to upgrade if it's a regular dependency rather than jarjar'd. On Jan 31, 2014, at 2:04 PM, Joachim Van der Auwera wrote: I am currently using Tapestry 5.4 on Java8 by applying the patch given in https://issues.apache.org/jira/browse/TAP5-2214. I have not (yet) found other issues when using Java8. Personally, I would like to see this patch applied, but I understand that including a non-release version of ASM is not ideal. Kind regards, Joachim On 01/31/2014 07:44 PM, Lenny Primak wrote: Is there a plan to update 5.3.x when Java 8 comes out? Is it just the matter of the version of ASM that is used or is there something else that precludes 5.3.x to run on Java 8? Thanks - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
