On Fri, Sep 7, 2012 at 1:42 PM, Kohsuke Kawaguchi
wrote:
>
> Yes, slaves are important.
>
> When the Jenkins core bumps up to require Java6, all the slaves will need to
> run Java6.
>
> You can still launch builds that builds with Java5 (just like you can today
> launch a build that builds with Ja
On 09/06/2012 12:12 AM, Stephen Connolly wrote:
On 5 September 2012 23:16, Kohsuke Kawaguchi mailto:kkawagu...@cloudbees.com>> wrote:
On 09/05/2012 01:18 PM, Brian Smith wrote:
Hi
I don't think EOL alone is a good reason to upgrade the runtime
dependency, anybody co
+1
I know thats not easy to update all kinds of nodes to Java 1.6+. But the
jenkins core should be cleaned up to depend on Java 1.6.
Conny
Am Mittwoch, 5. September 2012 21:18:41 UTC+2 schrieb domi:
>
> Hi all,
>
> just after todays meeting on the IRC chat, we startet a discussion about
> upg
Am Mittwoch, 5. September 2012 21:18:41 UTC+2 schrieb domi:
>
> Hi all,
>
> just after todays meeting on the IRC chat, we startet a discussion about
> upgrading Jenkins to Java 6.
> As Java 5 has reached EOL since quite a while, some core developers have
> asked whether it would be
> OK to b
On 5 September 2012 23:16, Kohsuke Kawaguchi wrote:
> On 09/05/2012 01:18 PM, Brian Smith wrote:
>
>> Hi
>>
>> I don't think EOL alone is a good reason to upgrade the runtime
>> dependency, anybody concerned about it can run on a newer JVM anyway.
>>
>> It might help if someone were to outline the
: Jenkins Developers ,
"jenkinsci-users@googlegroups.com"
Datum: 05.09.2012 21:24
Betreff: [VOTE] Bump Jenkins to Java 6
Gesendet von: jenkinsci-users@googlegroups.com
Hi all,
just after todays meeting on the IRC chat, we startet a discussion about
upgrading Jenkins to Java 6
We aren't talking about requiring Java7.
So let's not confuse this request for feedback with a different issue.
On 09/05/2012 12:38 PM, Jeff wrote:
Bump Jenkins version to 1.500 (or something), put branch 1.4xx into
maintenance and switch to Java 7. Java 7 is already at update 7.
My $.02.
On 09/05/2012 05:12 PM, Thomas Sundberg wrote:
On 5 September 2012 21:38, Jeff wrote:
Bump Jenkins version to 1.500 (or something), put branch 1.4xx into
maintenance and switch to Java 7. Java 7 is already at update 7.
+1
Java 6 is end of life by Feb 2013 [1], If I understand it correctly,
On 5 September 2012 21:38, Jeff wrote:
> Bump Jenkins version to 1.500 (or something), put branch 1.4xx into
> maintenance and switch to Java 7. Java 7 is already at update 7.
>
+1
Java 6 is end of life by Feb 2013 [1], If I understand it correctly,
we are discussing a dependency to a Java 7 ru
i-users@googlegroups.com
>Sent: Wednesday, September 5, 2012 1:38 PM
>Subject: Re: [VOTE] Bump Jenkins to Java 6
>
>
>Bump Jenkins version to 1.500 (or something), put branch 1.4xx into
>maintenance and switch to Java 7. Java 7 is already at update 7.
>
>
>My $.02.
>
&
Bump Jenkins version to 1.500 (or something), put branch 1.4xx into
maintenance and switch to Java 7. Java 7 is already at update 7.
My $.02.
On Wed, Sep 5, 2012 at 1:18 PM, domi wrote:
> Hi all,
>
> just after todays meeting on the IRC chat, we startet a discussion about
> upgrading Jenkins t
Hi all,
just after todays meeting on the IRC chat, we startet a discussion about
upgrading Jenkins to Java 6.
As Java 5 has reached EOL since quite a while, some core developers have asked
whether it would be
OK to bump Jenkins' runtime dependency from Java5 to Java6.
The core is already build
12 matches
Mail list logo
