You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@creadur.apache.org by Dennis Lundberg <de...@apache.org> on 2014/11/04 23:14:57 UTC

Jenkins jobs are fixed for Rat

Hi,

I've changed our Jenkins jobs for Rat, so that they now use Java 6.
That made our builds succeed again.

-- 
Dennis Lundberg

Re: Jenkins jobs are fixed for Rat

Posted by Dennis Lundberg <de...@apache.org>.
I agree that we should not drop support for Java 5.

I have added both Animal Sniffer and Maven Enforcer in place to make
sure that we don't use Java 6 stuff.

For 0.11 I used Java 5 to build the release.

On Wed, Nov 5, 2014 at 10:08 AM, Jochen Wiedmann
<jo...@gmail.com> wrote:
> Two basic considerations:
>
> - In general, if there is no compelling reason, we shouldn't drop
> support for major Java versions.
> - If we do support Java 5 at runtime, we shouldn't use Java 6 to build
> and test it. We might miss
>   incompatibilities otherwise.
> - That said, obtaining a Java 5 JDK is a non-trivial thing today. So I
> wonder whether we should stick
>    to 5.0 for the runtime version?
>
> I'm not in favour of one or the other. I'd just vote that we be consistent.
>
> Jochen
>
>
> On Tue, Nov 4, 2014 at 11:44 PM, P. Ottlinger <po...@apache.org> wrote:
>> Hi,
>>
>> Am 04.11.2014 um 23:14 schrieb Dennis Lundberg:
>>> I've changed our Jenkins jobs for Rat, so that they now use Java 6.
>>> That made our builds succeed again.
>>
>> I thought there were strong arguments for staying with Java5 and
>> ensuring that RAT builds with Java5 ?!
>>
>> Are these objections gone now?
>>
>> Thanks for fixing the builds; I suspected the infrastructure to be
>> instable again since my commits didn't change pom files.
>>
>> Cheers,
>> Phil
>>
>
>
>
> --
> Our time is just a point along a line that runs forever with no end.
> (Al Stewart, Lord Grenville)



-- 
Dennis Lundberg

Re: Jenkins jobs are fixed for Rat

Posted by Jochen Wiedmann <jo...@gmail.com>.
Two basic considerations:

- In general, if there is no compelling reason, we shouldn't drop
support for major Java versions.
- If we do support Java 5 at runtime, we shouldn't use Java 6 to build
and test it. We might miss
  incompatibilities otherwise.
- That said, obtaining a Java 5 JDK is a non-trivial thing today. So I
wonder whether we should stick
   to 5.0 for the runtime version?

I'm not in favour of one or the other. I'd just vote that we be consistent.

Jochen


On Tue, Nov 4, 2014 at 11:44 PM, P. Ottlinger <po...@apache.org> wrote:
> Hi,
>
> Am 04.11.2014 um 23:14 schrieb Dennis Lundberg:
>> I've changed our Jenkins jobs for Rat, so that they now use Java 6.
>> That made our builds succeed again.
>
> I thought there were strong arguments for staying with Java5 and
> ensuring that RAT builds with Java5 ?!
>
> Are these objections gone now?
>
> Thanks for fixing the builds; I suspected the infrastructure to be
> instable again since my commits didn't change pom files.
>
> Cheers,
> Phil
>



-- 
Our time is just a point along a line that runs forever with no end.
(Al Stewart, Lord Grenville)

Re: Jenkins jobs are fixed for Rat

Posted by "P. Ottlinger" <po...@apache.org>.
Hi Dennis,

Am 05.11.2014 um 14:13 schrieb Dennis Lundberg:
> Due to changes in Jenkins it is no longer possible to build stuff
> using Java 5, at least not in an easy way when you don't control the
> entire Jenkins instance. Therefor I had to change the jobs for them to
> build at all.

thanks for making this clear, I've adapted the job descriptions.

The remaining question is whether when we'll drop to support a release
that is hardly officially available. I assume that hardly any projects
build releases with Java5 .....

Cheers,
Philipp

Re: Jenkins jobs are fixed for Rat

Posted by Dennis Lundberg <de...@apache.org>.
No we still want to stay on Java 5. A release of Rat should be made
using Java 5 if possible.

Due to changes in Jenkins it is no longer possible to build stuff
using Java 5, at least not in an easy way when you don't control the
entire Jenkins instance. Therefor I had to change the jobs for them to
build at all.


On Tue, Nov 4, 2014 at 11:44 PM, P. Ottlinger <po...@apache.org> wrote:
> Hi,
>
> Am 04.11.2014 um 23:14 schrieb Dennis Lundberg:
>> I've changed our Jenkins jobs for Rat, so that they now use Java 6.
>> That made our builds succeed again.
>
> I thought there were strong arguments for staying with Java5 and
> ensuring that RAT builds with Java5 ?!
>
> Are these objections gone now?
>
> Thanks for fixing the builds; I suspected the infrastructure to be
> instable again since my commits didn't change pom files.
>
> Cheers,
> Phil
>



-- 
Dennis Lundberg

Re: Jenkins jobs are fixed for Rat

Posted by "P. Ottlinger" <po...@apache.org>.
Hi,

Am 04.11.2014 um 23:14 schrieb Dennis Lundberg:
> I've changed our Jenkins jobs for Rat, so that they now use Java 6.
> That made our builds succeed again.

I thought there were strong arguments for staying with Java5 and
ensuring that RAT builds with Java5 ?!

Are these objections gone now?

Thanks for fixing the builds; I suspected the infrastructure to be
instable again since my commits didn't change pom files.

Cheers,
Phil