[VOTE] Bump Jenkins to Java 6

[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 bump Jenkins' runtime dependency from Java5 to Java6.
The core is already build on Java6, but until now still backward compatible with Java5.
Therefore we would like to know from you (Users) whether you have an issue with this upgrade.
This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave).

Here are the current usage numbers (installations we know of):
Java 1.5: 655
Java 1.6: 29164
Java 1.7: 2919

So please give us some feedback/votes on this.
Domi

[Brian Smith]

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 benefit of upgrading the language version.

What's the upside for jenkins dev?  Is there something in java 6 people are hankering to use?

Personally the only things in java 6 I've found useful were the new concurrent collections and the ResourceBundle hooks.

Cheers

Brian

On 5 September 2012 20:18, domi <[hidden email]> wrote:

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 on Java6, but until now still backward compatible with Java5.
Therefore we would like to know from you (Users) whether you have an issue with this upgrade.
This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave).

Here are the current usage numbers (installations we know of):
Java 1.5: 655
Java 1.6: 29164
Java 1.7: 2919

So please give us some feedback/votes on this.
Domi

[kohsuke Kawaguchi (CB)]

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 benefit of upgrading the
> language version.

The benefits to developers are:

  - We get to use a few APIs that we currently can't rely on.
    (Note that we already do use a number of Java6 APIs in ways that
    gracefully degrades when running on Java5, but this is separate.)

  - Some IDE integrations (apparently) work better when what we tell
    as the compiler language level (1.5) matches with the runtime
    requirement (1.6)

  - Some language level stuff (like @Override on interface methods)
    causes IDE and javac to disagree, which gets fixed with 1.6.

The benefits are admittedly marginal, but the argument is that the cost
is marginal, too --- just 2% of users on Java5, and I suspect those
people aren't updating frequently.

And at some point we need to move on, so I suppose it could well be now.


I guess what I'm particularly keen on is if there are any minority
platforms where Java6 isn't available easily, and/or desperate cries
from users begging us not to require Java6, if any.

(Personally, I'm neutral on this.)

> What's the upside for jenkins dev?  Is there something in java 6 people
> are hankering to use?
>
> Personally the only things in java 6 I've found useful were the new
> concurrent collections and the ResourceBundle hooks.
>
> Cheers
>
> Brian
>
> On 5 September 2012 20:18, domi <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     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 on Java6, but until now still backward
>     compatible with Java5.
>     Therefore we would like to know from you (Users) whether you have an
>     issue with this upgrade.
>     This would mean, that in the future you will have to have Java6
>     installed to run Jenkins (for Master and Slave).
>
>     Here are the current usage numbers (installations we know of):
>     Java 1.5: 655
>     Java 1.6: 29164
>     Java 1.7: 2919
>
>     So please give us some feedback/votes on this.
>     Domi
>
>

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

[stephenconnolly]

On 5 September 2012 23:16, Kohsuke Kawaguchi <[hidden email]> 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 benefit of upgrading the
language version.

The benefits to developers are:

 - We get to use a few APIs that we currently can't rely on.
   (Note that we already do use a number of Java6 APIs in ways that
   gracefully degrades when running on Java5, but this is separate.)

 - Some IDE integrations (apparently) work better when what we tell
   as the compiler language level (1.5) matches with the runtime
   requirement (1.6)

 - Some language level stuff (like @Override on interface methods)
   causes IDE and javac to disagree, which gets fixed with 1.6.

The benefits are admittedly marginal, but the argument is that the cost is marginal, too --- just 2% of users on Java5, and I suspect those people aren't updating frequently.

And at some point we need to move on, so I suppose it could well be now.


I guess what I'm particularly keen on is if there are any minority platforms where Java6 isn't available easily, and/or desperate cries from users begging us not to require Java6, if any.

This is really where the issue is.

If you have Jenkins slaves that are on older OSes which are stuck with Java 1.5 as the "best" JVM they can run, please shout out now.

-Stephen

(Personally, I'm neutral on this.)

What's the upside for jenkins dev?  Is there something in java 6 people
are hankering to use?

Personally the only things in java 6 I've found useful were the new
concurrent collections and the ResourceBundle hooks.

Cheers

Brian

On 5 September 2012 20:18, domi <[hidden email]

<mailto:[hidden email]>> wrote:

    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 on Java6, but until now still backward
    compatible with Java5.
    Therefore we would like to know from you (Users) whether you have an
    issue with this upgrade.
    This would mean, that in the future you will have to have Java6
    installed to run Jenkins (for Master and Slave).

    Here are the current usage numbers (installations we know of):
    Java 1.5: 655
    Java 1.6: 29164
    Java 1.7: 2919

    So please give us some feedback/votes on this.
    Domi

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

[Conny Kreyßel-2]

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 bump Jenkins' runtime dependency from Java5 to Java6.
The core is already build on Java6, but until now still backward compatible with Java5.
Therefore we would like to know from you (Users) whether you have an issue with this upgrade.
This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave).

Here are the current usage numbers (installations we know of):
Java 1.5: 655
Java 1.6: 29164
Java 1.7: 2919

So please give us some feedback/votes on this.
Domi

[Conny Kreyßel-2]

+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 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 on Java6, but until now still backward compatible with Java5.
Therefore we would like to know from you (Users) whether you have an issue with this upgrade.
This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave).

Here are the current usage numbers (installations we know of):
Java 1.5: 655
Java 1.6: 29164
Java 1.7: 2919

So please give us some feedback/votes on this.
Domi

[Henri Gomez]

+0 (non binding)

Java 6 is available in all productions, so no reason to stick with Java 5 today

2012/9/7 Conny Kreyßel <[hidden email]>:

> +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
>> 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 on Java6, but until now still backward
>> compatible with Java5.
>> Therefore we would like to know from you (Users) whether you have an issue
>> with this upgrade.
>> This would mean, that in the future you will have to have Java6 installed
>> to run Jenkins (for Master and Slave).
>>
>> Here are the current usage numbers (installations we know of):
>> Java 1.5: 655
>> Java 1.6: 29164
>> Java 1.7: 2919
>>
>> So please give us some feedback/votes on this.
>> Domi

[David Karlsen]

+1.
I'm always running jenkins on latest available release (e.g. 1.7up7
atm) - no probs

2012/9/7 Henri Gomez <[hidden email]>:

> +0 (non binding)
>
> Java 6 is available in all productions, so no reason to stick with Java 5 today
>
> 2012/9/7 Conny Kreyßel <[hidden email]>:
>> +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
>>> 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 on Java6, but until now still backward
>>> compatible with Java5.
>>> Therefore we would like to know from you (Users) whether you have an issue
>>> with this upgrade.
>>> This would mean, that in the future you will have to have Java6 installed
>>> to run Jenkins (for Master and Slave).
>>>
>>> Here are the current usage numbers (installations we know of):
>>> Java 1.5: 655
>>> Java 1.6: 29164
>>> Java 1.7: 2919
>>>
>>> So please give us some feedback/votes on this.
>>> Domi

--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

[Christoph Kutzinski]

+1 for going to Java 6


-------- Original-Nachricht --------
> Datum: Fri, 7 Sep 2012 14:05:01 +0200
> Von: David Karlsen <[hidden email]>
> An: [hidden email]
> Betreff: Re: [VOTE] Bump Jenkins to Java 6

> +1.
> I'm always running jenkins on latest available release (e.g. 1.7up7
> atm) - no probs
>
> 2012/9/7 Henri Gomez <[hidden email]>:
> > +0 (non binding)
> >
> > Java 6 is available in all productions, so no reason to stick with Java
> 5 today
> >
> > 2012/9/7 Conny Kreyßel <[hidden email]>:
> >> +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
> >>> 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 on Java6, but until now still backward
> >>> compatible with Java5.
> >>> Therefore we would like to know from you (Users) whether you have an
> issue
> >>> with this upgrade.
> >>> This would mean, that in the future you will have to have Java6
> installed
> >>> to run Jenkins (for Master and Slave).
> >>>
> >>> Here are the current usage numbers (installations we know of):
> >>> Java 1.5: 655
> >>> Java 1.6: 29164
> >>> Java 1.7: 2919
> >>>
> >>> So please give us some feedback/votes on this.
> >>> Domi
>
>
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

[nicolas de loof-2]

+1 for java 6 - at least to get rid of IDE complaining for @Overide on interface ;)

2012/9/7 Christoph Kutzinski <[hidden email]>

+1 for going to Java 6


-------- Original-Nachricht --------
> Datum: Fri, 7 Sep 2012 14:05:01 +0200
> Von: David Karlsen <[hidden email]>
> An: [hidden email]
> Betreff: Re: [VOTE] Bump Jenkins to Java 6

> +1.
> I'm always running jenkins on latest available release (e.g. 1.7up7
> atm) - no probs
>
> 2012/9/7 Henri Gomez <[hidden email]>:
> > +0 (non binding)
> >
> > Java 6 is available in all productions, so no reason to stick with Java
> 5 today
> >
> > 2012/9/7 Conny Kreyßel <[hidden email]>:
> >> +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
> >>> 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 on Java6, but until now still backward
> >>> compatible with Java5.
> >>> Therefore we would like to know from you (Users) whether you have an
> issue
> >>> with this upgrade.
> >>> This would mean, that in the future you will have to have Java6
> installed
> >>> to run Jenkins (for Master and Slave).
> >>>
> >>> Here are the current usage numbers (installations we know of):
> >>> Java 1.5: 655
> >>> Java 1.6: 29164
> >>> Java 1.7: 2919
> >>>
> >>> So please give us some feedback/votes on this.
> >>> Domi
>
>
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

[vlatombe]

+1 from me as well. As already said by others,

- JDK6 base is very large now, JDK5 is well beyond EOL.

- No more APIs problems because we use JDK6 for development but compile to 1.5 level

- No more complaining for IDE because of @Override

Vincent

2012/9/7 nicolas de loof <[hidden email]>

+1 for java 6 - at least to get rid of IDE complaining for @Overide on interface ;)

2012/9/7 Christoph Kutzinski <[hidden email]>

+1 for going to Java 6


-------- Original-Nachricht --------
> Datum: Fri, 7 Sep 2012 14:05:01 +0200
> Von: David Karlsen <[hidden email]>
> An: [hidden email]
> Betreff: Re: [VOTE] Bump Jenkins to Java 6

> +1.
> I'm always running jenkins on latest available release (e.g. 1.7up7
> atm) - no probs
>
> 2012/9/7 Henri Gomez <[hidden email]>:
> > +0 (non binding)
> >
> > Java 6 is available in all productions, so no reason to stick with Java
> 5 today
> >
> > 2012/9/7 Conny Kreyßel <[hidden email]>:
> >> +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
> >>> 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 on Java6, but until now still backward
> >>> compatible with Java5.
> >>> Therefore we would like to know from you (Users) whether you have an
> issue
> >>> with this upgrade.
> >>> This would mean, that in the future you will have to have Java6
> installed
> >>> to run Jenkins (for Master and Slave).
> >>>
> >>> Here are the current usage numbers (installations we know of):
> >>> Java 1.5: 655
> >>> Java 1.6: 29164
> >>> Java 1.7: 2919
> >>>
> >>> So please give us some feedback/votes on this.
> >>> Domi
>
>
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

[kohsuke Kawaguchi (CB)]

On 09/06/2012 12:12 AM, Stephen Connolly wrote:

> On 5 September 2012 23:16, Kohsuke Kawaguchi <[hidden email]
> <mailto:[hidden email]>> 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 benefit of
>         upgrading the
>         language version.
>
>
>     The benefits to developers are:
>
>       - We get to use a few APIs that we currently can't rely on.
>         (Note that we already do use a number of Java6 APIs in ways that
>         gracefully degrades when running on Java5, but this is separate.)
>
>       - Some IDE integrations (apparently) work better when what we tell
>         as the compiler language level (1.5) matches with the runtime
>         requirement (1.6)
>
>       - Some language level stuff (like @Override on interface methods)
>         causes IDE and javac to disagree, which gets fixed with 1.6.
>
>     The benefits are admittedly marginal, but the argument is that the
>     cost is marginal, too --- just 2% of users on Java5, and I suspect
>     those people aren't updating frequently.
>
>     And at some point we need to move on, so I suppose it could well be now.
>
>
>     I guess what I'm particularly keen on is if there are any minority
>     platforms where Java6 isn't available easily, and/or desperate cries
>     from users begging us not to require Java6, if any.
>
>
> This is really where the issue is.
>
> If you have Jenkins slaves that are on older OSes which are stuck with
> Java 1.5 as the "best" JVM they can run, please shout out now.

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 Java 1.4), but the slave JVM will
have to be Java6.

So folks, think about all the exotic slaves you may have (BSD, SunOS,
IRIX, HP-UX, AIX, ...) and think if Java6 is available readily on them.
Do you  keep any ancient versions of those platforms for testing
purpose? Do your ancient versions have Java6?

So far we are seeing wide support from developers to bump up to 1.6. So
you better raise your voice if you have a problem...

> -Stephen
>
>
>     (Personally, I'm neutral on this.)
>
>         What's the upside for jenkins dev?  Is there something in java 6
>         people
>         are hankering to use?
>
>         Personally the only things in java 6 I've found useful were the new
>         concurrent collections and the ResourceBundle hooks.
>
>         Cheers
>
>         Brian
>
>         On 5 September 2012 20:18, domi <[hidden email]
>         <mailto:[hidden email]>
>         <mailto:[hidden email] <mailto:[hidden email]>>> wrote:
>
>              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 on Java6, but until now still
>         backward
>              compatible with Java5.
>              Therefore we would like to know from you (Users) whether
>         you have an
>              issue with this upgrade.
>              This would mean, that in the future you will have to have Java6
>              installed to run Jenkins (for Master and Slave).
>
>              Here are the current usage numbers (installations we know of):
>              Java 1.5: 655
>              Java 1.6: 29164
>              Java 1.7: 2919
>
>              So please give us some feedback/votes on this.
>              Domi
>
>
>
>
>     --
>     Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>     Try Nectar, our professional version of Jenkins
>
>

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

[kohsuke Kawaguchi (CB)]

On 09/07/2012 06:02 AM, Vincent Latombe wrote:
> +1 from me as well. As already said by others,
>
> - No more APIs problems because we use JDK6 for development but compile
> to 1.5 level

This will never really go away as many of us nowadays use JDK7 for
development.

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

[Kane Bonnette]

> So folks, think about all the exotic slaves you may have (BSD, SunOS, IRIX, HP-UX, AIX, ...) and think if Java6 is available readily on them.
> Do you  keep any ancient versions of those platforms for testing purpose? Do your ancient versions have Java6?


At some point we have to draw a line and say "this is causing too many problems and not giving enough benefits" and upgrade. When the base platform is at end of life, that seems like a good line to me.

There will always be some exotic machine out there that doesn't have the latest and greatest. I am sure there were issues when there were upgrades from Java 1.4. But if not enough Oracle cares to support those ancient systems I don't think there's any need for Jenkins to do so.

There's also a wider ecosystem argument. If nobody refuses to stop supporting old versions of technology, then we will drag those old versions around like an albatross across the wider community's neck. I am sure Microsoft has endless gnashing of teeth over the number of people that still use IE6, with is slow, bug-ridden, security-hole filled codebase, instead of the much newer and modern versions they have put out. And those old versions hurt the wider web development community, but because they are supported (or mandatory!) by a number of applications, IE6 and earlier hang around and act as a drag to wider web development.

Chrome has largely avoided this issue with the auto-update architecture and it's a much better platform because of it.

Java is the same way.

+1 for Java 6.

[Olivier Lamy-2]

Hi,
+1
I just wonder if maven job running with a jdk 1.5 will still work (/me
just remember an issue using jenkins on tomcat7 with maven job with
1.5 but not sure that's the same trouble)

--
Olivier
2012/9/5 domi <[hidden email]>:

> 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 on Java6, but until now still backward compatible with Java5.
> Therefore we would like to know from you (Users) whether you have an issue with this upgrade.
> This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave).
>
> Here are the current usage numbers (installations we know of):
> Java 1.5: 655
> Java 1.6: 29164
> Java 1.7: 2919
>
> So please give us some feedback/votes on this.
> Domi

--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

[David Karlsen]

Even HP-PA runs java6 - probably the most exotic I run.

2012/9/7 Kohsuke Kawaguchi <[hidden email]>:

> On 09/06/2012 12:12 AM, Stephen Connolly wrote:
>>
>> On 5 September 2012 23:16, Kohsuke Kawaguchi <[hidden email]
>> <mailto:[hidden email]>> 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 benefit of
>>         upgrading the
>>         language version.
>>
>>
>>     The benefits to developers are:
>>
>>       - We get to use a few APIs that we currently can't rely on.
>>         (Note that we already do use a number of Java6 APIs in ways that
>>         gracefully degrades when running on Java5, but this is separate.)
>>
>>       - Some IDE integrations (apparently) work better when what we tell
>>         as the compiler language level (1.5) matches with the runtime
>>         requirement (1.6)
>>
>>       - Some language level stuff (like @Override on interface methods)
>>         causes IDE and javac to disagree, which gets fixed with 1.6.
>>
>>     The benefits are admittedly marginal, but the argument is that the
>>     cost is marginal, too --- just 2% of users on Java5, and I suspect
>>     those people aren't updating frequently.
>>
>>     And at some point we need to move on, so I suppose it could well be
>> now.
>>
>>
>>     I guess what I'm particularly keen on is if there are any minority
>>     platforms where Java6 isn't available easily, and/or desperate cries
>>     from users begging us not to require Java6, if any.
>>
>>
>> This is really where the issue is.
>>
>> If you have Jenkins slaves that are on older OSes which are stuck with
>> Java 1.5 as the "best" JVM they can run, please shout out now.
>
>
> 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 Java 1.4), but the slave JVM will have to be
> Java6.
>
> So folks, think about all the exotic slaves you may have (BSD, SunOS, IRIX,
> HP-UX, AIX, ...) and think if Java6 is available readily on them. Do you
> keep any ancient versions of those platforms for testing purpose? Do your
> ancient versions have Java6?
>
> So far we are seeing wide support from developers to bump up to 1.6. So you
> better raise your voice if you have a problem...
>
>> -Stephen
>>
>>
>>     (Personally, I'm neutral on this.)
>>
>>         What's the upside for jenkins dev?  Is there something in java 6
>>         people
>>         are hankering to use?
>>
>>         Personally the only things in java 6 I've found useful were the
>> new
>>         concurrent collections and the ResourceBundle hooks.
>>
>>         Cheers
>>
>>         Brian
>>
>>         On 5 September 2012 20:18, domi <[hidden email]
>>         <mailto:[hidden email]>
>>         <mailto:[hidden email] <mailto:[hidden email]>>> wrote:
>>
>>              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 on Java6, but until now still
>>         backward
>>              compatible with Java5.
>>              Therefore we would like to know from you (Users) whether
>>         you have an
>>              issue with this upgrade.
>>              This would mean, that in the future you will have to have
>> Java6
>>              installed to run Jenkins (for Master and Slave).
>>
>>              Here are the current usage numbers (installations we know
>> of):
>>              Java 1.5: 655
>>              Java 1.6: 29164
>>              Java 1.7: 2919
>>
>>              So please give us some feedback/votes on this.
>>              Domi
>>
>>
>>
>>
>>     --
>>     Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>>     Try Nectar, our professional version of Jenkins
>>
>>
>
>
> --
> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
> Try Nectar, our professional version of Jenkins

--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

[Kohsuke Kawaguchi]

Hmm, good point, no it won't.

Even if we are to compile maven-plugin with 1.5, I'm pretty sure it
uses a number of classes from core.

2012/9/7 Olivier Lamy <[hidden email]>:

> Hi,
> +1
> I just wonder if maven job running with a jdk 1.5 will still work (/me
> just remember an issue using jenkins on tomcat7 with maven job with
> 1.5 but not sure that's the same trouble)
>
> --
> Olivier
> 2012/9/5 domi <[hidden email]>:
>> 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 on Java6, but until now still backward compatible with Java5.
>> Therefore we would like to know from you (Users) whether you have an issue with this upgrade.
>> This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave).
>>
>> Here are the current usage numbers (installations we know of):
>> Java 1.5: 655
>> Java 1.6: 29164
>> Java 1.7: 2919
>>
>> So please give us some feedback/votes on this.
>> Domi
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy

--
Kohsuke Kawaguchi

[Olivier Lamy-2]

/me gloups...



2012/9/8 Kohsuke Kawaguchi <[hidden email]>:

> Hmm, good point, no it won't.
>
> Even if we are to compile maven-plugin with 1.5, I'm pretty sure it
> uses a number of classes from core.
>
> 2012/9/7 Olivier Lamy <[hidden email]>:
>> Hi,
>> +1
>> I just wonder if maven job running with a jdk 1.5 will still work (/me
>> just remember an issue using jenkins on tomcat7 with maven job with
>> 1.5 but not sure that's the same trouble)
>>
>> --
>> Olivier
>> 2012/9/5 domi <[hidden email]>:
>>> 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 on Java6, but until now still backward compatible with Java5.
>>> Therefore we would like to know from you (Users) whether you have an issue with this upgrade.
>>> This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave).
>>>
>>> Here are the current usage numbers (installations we know of):
>>> Java 1.5: 655
>>> Java 1.6: 29164
>>> Java 1.7: 2919
>>>
>>> So please give us some feedback/votes on this.
>>> Domi
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Kohsuke Kawaguchi

--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

[Jesse Glick-4]

On 09/08/2012 02:55 AM, Olivier Lamy wrote:
> I just wonder if maven job running with a jdk 1.5 will still work

Does it not suffice to configure maven-compiler-plugin to use source/target 1.5, and add an execution for animal-sniffer-maven-plugin to make sure you are not “cheating”?
Or use toolchains?

If you need to run integration tests and the like using Java 5, can you use a freestyle job and run Maven forked with an explicitly selected JDK?

[Olivier Lamy-2]

2012/9/10 Jesse Glick <[hidden email]>:
> On 09/08/2012 02:55 AM, Olivier Lamy wrote:
>>
>> I just wonder if maven job running with a jdk 1.5 will still work
>
>
> Does it not suffice to configure maven-compiler-plugin to use source/target
> 1.5, and add an execution for animal-sniffer-maven-plugin to make sure you
> are not “cheating”? Or use toolchains?
Yes I know a bit those tools. I prefer animal-sniffer to toolchains
which need some manual stuff when you install nodes.
Hey cool normally jenkins do that for you but having to
create/maintain a file ~/.m2/toolchains.xml is a pain. At least
jenkins could create it (a new plugin idea maybe :-) )

My concern is not me but the majority of the users who have 1.5 build
with maven-plugin.
IMHO they are probably a lot (I'm doing some maintenance on ASF
Jenkins instance and that's the case).
If we do such changes we must really take care about a really visible
warning mechanism to correctly inform of what to do/change to fix
issues.

>
> If you need to run integration tests and the like using Java 5, can you use
> a freestyle job and run Maven forked with an explicitly selected JDK?
If you have all the features from maven-plugin available in freestyle
and a tool to convert a maven job to a freestyle: sure I will be happy
:-)


--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy