Re: Continuum and minimum JDK requirement
Emmanuel Venisse emmanuel at venisse.net writes: Brett talked about the possibility to fork builds with Continuum [3]. Continuum always forks builds. However, controlling the JDK it used was not easy. I do believe profiles support will be in the next release and will make it easy. Yes, it will be in Continuum 1.1-beta-1. With Profiles/Installations, you can choose the jdk, maven and environment var to use for a build. Thanks all very much for the information. It's good to know that it is available. Now we only need to get it installed in our zone. Regards, Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuum and minimum JDK requirement
Hi, Just try last continuum snapshot [1]. Now it's possible to define profile with particular jdk, mvn, maven1, ant and/or env var. -- Olivier [1] http://maven.zones.apache.org/~continuum/builds/trunk/?M=D -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Joerg Heinicke Envoyé : mercredi 11 juillet 2007 02:33 À : dev@maven.apache.org Objet : Continuum and minimum JDK requirement Hello guys, we had an issue recently with Continuum on Cocoon and continuous integration which fails to check JDK 1.4 compliance of Cocoon's code base since Continuum itself is running with a JDK 5 (in that particular case it was usage of ThreadLocal.remove() [1]). I found the thread about raising the minimum JDK for Continuum where exactly such issues where foreseen [2]. Brett talked about the possibility to fork builds with Continuum [3]. Is that how Maven assures 1.4 compatibility running its Continuum? Or how do you assure it? Putting it to the extremes there might even be a JDK 1.4 project using enum keyword which should be build with Continuum. If the latter requires JDK 5 is it possible though to build that project? Thanks for any hint, Joerg [1] http://marc.info/?l=xml-cocoon-devm=118115701130207w=4 [2] http://marc.info/?t=11522363541r=1w=4, in particular Steven's mail http://marc.info/?l=turbine-maven-devm=115227611406486w=4 [3] http://marc.info/?l=turbine-maven-devm=115518652524872w=4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuum and minimum JDK requirement
Brett Porter a écrit : On 11/07/2007, at 10:32 AM, Joerg Heinicke wrote: Hello guys, we had an issue recently with Continuum on Cocoon and continuous integration which fails to check JDK 1.4 compliance of Cocoon's code base since Continuum itself is running with a JDK 5 (in that particular case it was usage of ThreadLocal.remove() [1]). I found the thread about raising the minimum JDK for Continuum where exactly such issues where foreseen [2]. The binding problem is a relatively small number of cases that can probably be avoided in your code. Accidentally using JDK 5 methods is something that comes up frequently and you should certainly regularly build on 1.4 to check. Brett talked about the possibility to fork builds with Continuum [3]. Continuum always forks builds. However, controlling the JDK it used was not easy. I do believe profiles support will be in the next release and will make it easy. Yes, it will be in Continuum 1.1-beta-1. With Profiles/Installations, you can choose the jdk, maven and environment var to use for a build. Putting it to the extremes there might even be a JDK 1.4 project using enum keyword which should be build with Continuum. If the latter requires JDK 5 is it possible though to build that project? Setting the correct -source will take care of that. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Continuum and minimum JDK requirement
Hello guys, we had an issue recently with Continuum on Cocoon and continuous integration which fails to check JDK 1.4 compliance of Cocoon's code base since Continuum itself is running with a JDK 5 (in that particular case it was usage of ThreadLocal.remove() [1]). I found the thread about raising the minimum JDK for Continuum where exactly such issues where foreseen [2]. Brett talked about the possibility to fork builds with Continuum [3]. Is that how Maven assures 1.4 compatibility running its Continuum? Or how do you assure it? Putting it to the extremes there might even be a JDK 1.4 project using enum keyword which should be build with Continuum. If the latter requires JDK 5 is it possible though to build that project? Thanks for any hint, Joerg [1] http://marc.info/?l=xml-cocoon-devm=118115701130207w=4 [2] http://marc.info/?t=11522363541r=1w=4, in particular Steven's mail http://marc.info/?l=turbine-maven-devm=115227611406486w=4 [3] http://marc.info/?l=turbine-maven-devm=115518652524872w=4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuum and minimum JDK requirement
On 11/07/2007, at 10:32 AM, Joerg Heinicke wrote: Hello guys, we had an issue recently with Continuum on Cocoon and continuous integration which fails to check JDK 1.4 compliance of Cocoon's code base since Continuum itself is running with a JDK 5 (in that particular case it was usage of ThreadLocal.remove() [1]). I found the thread about raising the minimum JDK for Continuum where exactly such issues where foreseen [2]. The binding problem is a relatively small number of cases that can probably be avoided in your code. Accidentally using JDK 5 methods is something that comes up frequently and you should certainly regularly build on 1.4 to check. Brett talked about the possibility to fork builds with Continuum [3]. Continuum always forks builds. However, controlling the JDK it used was not easy. I do believe profiles support will be in the next release and will make it easy. Putting it to the extremes there might even be a JDK 1.4 project using enum keyword which should be build with Continuum. If the latter requires JDK 5 is it possible though to build that project? Setting the correct -source will take care of that. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuum and minimum JDK requirement
just fyi, we are working on getting that profile enabled version released in the next couple of weeks jesse On 7/10/07, Brett Porter [EMAIL PROTECTED] wrote: On 11/07/2007, at 10:32 AM, Joerg Heinicke wrote: Hello guys, we had an issue recently with Continuum on Cocoon and continuous integration which fails to check JDK 1.4 compliance of Cocoon's code base since Continuum itself is running with a JDK 5 (in that particular case it was usage of ThreadLocal.remove() [1]). I found the thread about raising the minimum JDK for Continuum where exactly such issues where foreseen [2]. The binding problem is a relatively small number of cases that can probably be avoided in your code. Accidentally using JDK 5 methods is something that comes up frequently and you should certainly regularly build on 1.4 to check. Brett talked about the possibility to fork builds with Continuum [3]. Continuum always forks builds. However, controlling the JDK it used was not easy. I do believe profiles support will be in the next release and will make it easy. Putting it to the extremes there might even be a JDK 1.4 project using enum keyword which should be build with Continuum. If the latter requires JDK 5 is it possible though to build that project? Setting the correct -source will take care of that. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continuum and minimum JDK requirement
Dear God, I am so happy to hear that. I swear, I wish I had more time to track this and contribute, but I'm really really impressed by this whole team and the progression of this product over the last year or so. Christian. On Jul 10, 2007, at 10:42 PM, Jesse McConnell wrote: just fyi, we are working on getting that profile enabled version released in the next couple of weeks jesse christian gruber + [EMAIL PROTECTED] + mob 410.900.0796 + mob2 416.998.6023 process coach and architect + ISRÁFÍL CONSULTING SERVICES - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
