You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2017/05/15 20:09:30 UTC
Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120
See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java%208/1120/display/redirect>
RE: Jenkins build is back to normal : Pivot-maintenance on Java 8
#1120
Posted by Roger Whitcomb <Ro...@actian.com>.
So, what I found out (separately) is that even if you set the build class to 1.7 (say), and use the 1.8 compiler, but DON'T set the 1.7 bootstrap classpath, then the compiler will not flag stuff that is not compliant with the earlier version, so we need to either build with 1.6, or set the bootstrap classpath so that the 1.8 compiler will still check the 1.6 classes, and etc. Remember there was a bug I fixed a week ago or so, because I had used a 1.8 method, but compiling with 1.8 even with the "compiler.source" and "compiler.target" set to 1.7 didn't catch the error, UNTIL I also set the bootstrap classpath to 1.7.... So, that's why I'm a bit concerned. If we still want 2.0.x to run with 1.6, then we really need to really compile with 1.6 (somehow)...
~Roger
-----Original Message-----
From: Sandro Martini [mailto:sandro.martini@gmail.com]
Sent: Wednesday, May 17, 2017 8:16 AM
To: Developers - Apache Pivot <de...@pivot.apache.org>
Subject: Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120
Hi Roger,
I dropped the build on Java 7 only because on 2.0.x the minimum required Java version is 6, and the current one is Java 8, and Java 7 is after End-of-Life so I think is no more relevant (even because if some code compiles with Java 6 and with Java 8 usually if works even with Java 7) ...
Anyway if needed we can restore is (or better, define it from scratch in Jenkins).
Bye,
Sandro
2017-05-17 16:59 GMT+02:00 Roger and Beth Whitcomb
<Ro...@rbwhitcomb.com>:
> So, the "maintenance" branch (2.0.x) still only requires Java 1.6, so
> why are we only building with Java 8? I would think we should be
> building with Java 1.6, so we know that it works at the lowest common
> denominator still..... Is that possible? Does the Jenkins machine
> have access to Java
> 1.6 JDK? If not, then I think we should be building/testing "maintenance"
> with 1.7, since that is the most likely "lowest common denominator"
> actively being used at this point....
>
> Actually, I would think we should be doing "maintenance" builds with
> all
> three: 1.6, 1.7 and 1.8, just to check to make sure it works with any
> Java version that Pivot 2.0.x will accept.... For "trunk" we could
> just have 1.8 builds, since that is what we are targeting at this point.
>
> Thoughts? Is this possible?
>
> Thanks,
> ~Roger
>
>
> On 5/16/17 4:09 PM, Sandro Martini wrote:
>>
>> Hi Roger,
>> I changed the maintenance build from using Java 7 to Java 8 mainly
>> because JRE 7 should not occurs any more now (instead of creating by
>> scratch a new Jenkins job) ... if needed I can take a look.
>>
>> On trunk I agree that a build on Java 7 is no more needed, at least I
>> could disable it.
>>
>> Bye
>>
>> Il 15/Mag/2017 23:35, "Roger and Beth Whitcomb"
>> <Ro...@rbwhitcomb.com>
>> ha scritto:
>>
>> Why do we no longer have a "Pivot-maintenance on Java 7" build? And
>> why are we building "trunk" on Java 7 anymore? Maybe we got the two
>> confused?
>>
>>
>> On 5/15/17 1:09 PM, Apache Jenkins Server wrote:
>>
>>> See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java
>>> %208/1120/display/redirect>
>>>
>>>
>>>
>>>
>
Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120
Posted by Sandro Martini <sa...@gmail.com>.
Hi,
I'm looking to disable Jenkins Build for trunk on Java 7, but looking
at our BUILD file we still set Java 7 as minimum release for the trunk
so I think we have two choices for trunk:
- stay with Java 7 as minimum requirements, and keep enabled related Jenkins job
- update requirements to Java 8, and disable Jenkins job for Java 7,
or better change it to test instead with latest builds of Java 9 to
start looking at it
What do you prefer ?
Bye,
Sandro
2017-05-17 19:06 GMT+02:00 Roger Whitcomb <Ro...@actian.com>:
> The other thing is that building the 2.0.x branch with Java 8 gives 100s of Javadoc warnings, which are also not really helpful. I have fixed all these in "trunk". But, if we're going to do a Jenkins build for 2.0.x (and I think we should, since is the current release branch), then it should build "clean", without 100s of warnings...... And a Java 7 (or Java 6 if we can do it) build would achieve that....
>
> ~Roger
>
> -----Original Message-----
> From: Sandro Martini [mailto:sandro.martini@gmail.com]
> Sent: Wednesday, May 17, 2017 8:16 AM
> To: Developers - Apache Pivot <de...@pivot.apache.org>
> Subject: Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120
>
> Hi Roger,
> I dropped the build on Java 7 only because on 2.0.x the minimum required Java version is 6, and the current one is Java 8, and Java 7 is after End-of-Life so I think is no more relevant (even because if some code compiles with Java 6 and with Java 8 usually if works even with Java 7) ...
>
> Anyway if needed we can restore is (or better, define it from scratch in Jenkins).
>
> Bye,
> Sandro
>
>
> 2017-05-17 16:59 GMT+02:00 Roger and Beth Whitcomb
> <Ro...@rbwhitcomb.com>:
>> So, the "maintenance" branch (2.0.x) still only requires Java 1.6, so
>> why are we only building with Java 8? I would think we should be
>> building with Java 1.6, so we know that it works at the lowest common
>> denominator still..... Is that possible? Does the Jenkins machine
>> have access to Java
>> 1.6 JDK? If not, then I think we should be building/testing "maintenance"
>> with 1.7, since that is the most likely "lowest common denominator"
>> actively being used at this point....
>>
>> Actually, I would think we should be doing "maintenance" builds with
>> all
>> three: 1.6, 1.7 and 1.8, just to check to make sure it works with any
>> Java version that Pivot 2.0.x will accept.... For "trunk" we could
>> just have 1.8 builds, since that is what we are targeting at this point.
>>
>> Thoughts? Is this possible?
>>
>> Thanks,
>> ~Roger
>>
>>
>> On 5/16/17 4:09 PM, Sandro Martini wrote:
>>>
>>> Hi Roger,
>>> I changed the maintenance build from using Java 7 to Java 8 mainly
>>> because JRE 7 should not occurs any more now (instead of creating by
>>> scratch a new Jenkins job) ... if needed I can take a look.
>>>
>>> On trunk I agree that a build on Java 7 is no more needed, at least I
>>> could disable it.
>>>
>>> Bye
>>>
>>> Il 15/Mag/2017 23:35, "Roger and Beth Whitcomb"
>>> <Ro...@rbwhitcomb.com>
>>> ha scritto:
>>>
>>> Why do we no longer have a "Pivot-maintenance on Java 7" build? And
>>> why are we building "trunk" on Java 7 anymore? Maybe we got the two
>>> confused?
>>>
>>>
>>> On 5/15/17 1:09 PM, Apache Jenkins Server wrote:
>>>
>>>> See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java
>>>> %208/1120/display/redirect>
>>>>
>>>>
>>>>
>>>>
>>
>
RE: Jenkins build is back to normal : Pivot-maintenance on Java 8
#1120
Posted by Roger Whitcomb <Ro...@actian.com>.
The other thing is that building the 2.0.x branch with Java 8 gives 100s of Javadoc warnings, which are also not really helpful. I have fixed all these in "trunk". But, if we're going to do a Jenkins build for 2.0.x (and I think we should, since is the current release branch), then it should build "clean", without 100s of warnings...... And a Java 7 (or Java 6 if we can do it) build would achieve that....
~Roger
-----Original Message-----
From: Sandro Martini [mailto:sandro.martini@gmail.com]
Sent: Wednesday, May 17, 2017 8:16 AM
To: Developers - Apache Pivot <de...@pivot.apache.org>
Subject: Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120
Hi Roger,
I dropped the build on Java 7 only because on 2.0.x the minimum required Java version is 6, and the current one is Java 8, and Java 7 is after End-of-Life so I think is no more relevant (even because if some code compiles with Java 6 and with Java 8 usually if works even with Java 7) ...
Anyway if needed we can restore is (or better, define it from scratch in Jenkins).
Bye,
Sandro
2017-05-17 16:59 GMT+02:00 Roger and Beth Whitcomb
<Ro...@rbwhitcomb.com>:
> So, the "maintenance" branch (2.0.x) still only requires Java 1.6, so
> why are we only building with Java 8? I would think we should be
> building with Java 1.6, so we know that it works at the lowest common
> denominator still..... Is that possible? Does the Jenkins machine
> have access to Java
> 1.6 JDK? If not, then I think we should be building/testing "maintenance"
> with 1.7, since that is the most likely "lowest common denominator"
> actively being used at this point....
>
> Actually, I would think we should be doing "maintenance" builds with
> all
> three: 1.6, 1.7 and 1.8, just to check to make sure it works with any
> Java version that Pivot 2.0.x will accept.... For "trunk" we could
> just have 1.8 builds, since that is what we are targeting at this point.
>
> Thoughts? Is this possible?
>
> Thanks,
> ~Roger
>
>
> On 5/16/17 4:09 PM, Sandro Martini wrote:
>>
>> Hi Roger,
>> I changed the maintenance build from using Java 7 to Java 8 mainly
>> because JRE 7 should not occurs any more now (instead of creating by
>> scratch a new Jenkins job) ... if needed I can take a look.
>>
>> On trunk I agree that a build on Java 7 is no more needed, at least I
>> could disable it.
>>
>> Bye
>>
>> Il 15/Mag/2017 23:35, "Roger and Beth Whitcomb"
>> <Ro...@rbwhitcomb.com>
>> ha scritto:
>>
>> Why do we no longer have a "Pivot-maintenance on Java 7" build? And
>> why are we building "trunk" on Java 7 anymore? Maybe we got the two
>> confused?
>>
>>
>> On 5/15/17 1:09 PM, Apache Jenkins Server wrote:
>>
>>> See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java
>>> %208/1120/display/redirect>
>>>
>>>
>>>
>>>
>
Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120
Posted by Sandro Martini <sa...@gmail.com>.
Hi Roger,
I dropped the build on Java 7 only because on 2.0.x the minimum
required Java version is 6, and the current one is Java 8, and Java 7
is after End-of-Life so I think is no more relevant (even because if
some code compiles with Java 6 and with Java 8 usually if works even
with Java 7) ...
Anyway if needed we can restore is (or better, define it from scratch
in Jenkins).
Bye,
Sandro
2017-05-17 16:59 GMT+02:00 Roger and Beth Whitcomb
<Ro...@rbwhitcomb.com>:
> So, the "maintenance" branch (2.0.x) still only requires Java 1.6, so why
> are we only building with Java 8? I would think we should be building with
> Java 1.6, so we know that it works at the lowest common denominator
> still..... Is that possible? Does the Jenkins machine have access to Java
> 1.6 JDK? If not, then I think we should be building/testing "maintenance"
> with 1.7, since that is the most likely "lowest common denominator" actively
> being used at this point....
>
> Actually, I would think we should be doing "maintenance" builds with all
> three: 1.6, 1.7 and 1.8, just to check to make sure it works with any Java
> version that Pivot 2.0.x will accept.... For "trunk" we could just have 1.8
> builds, since that is what we are targeting at this point.
>
> Thoughts? Is this possible?
>
> Thanks,
> ~Roger
>
>
> On 5/16/17 4:09 PM, Sandro Martini wrote:
>>
>> Hi Roger,
>> I changed the maintenance build from using Java 7 to Java 8 mainly because
>> JRE 7 should not occurs any more now (instead of creating by scratch a new
>> Jenkins job) ... if needed I can take a look.
>>
>> On trunk I agree that a build on Java 7 is no more needed, at least I
>> could
>> disable it.
>>
>> Bye
>>
>> Il 15/Mag/2017 23:35, "Roger and Beth Whitcomb"
>> <Ro...@rbwhitcomb.com>
>> ha scritto:
>>
>> Why do we no longer have a "Pivot-maintenance on Java 7" build? And why
>> are
>> we building "trunk" on Java 7 anymore? Maybe we got the two confused?
>>
>>
>> On 5/15/17 1:09 PM, Apache Jenkins Server wrote:
>>
>>> See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java
>>> %208/1120/display/redirect>
>>>
>>>
>>>
>>>
>
Re: Jenkins build is back to normal : Pivot-maintenance on Java 8
#1120
Posted by Roger and Beth Whitcomb <Ro...@rbwhitcomb.com>.
So, the "maintenance" branch (2.0.x) still only requires Java 1.6, so
why are we only building with Java 8? I would think we should be
building with Java 1.6, so we know that it works at the lowest common
denominator still..... Is that possible? Does the Jenkins machine have
access to Java 1.6 JDK? If not, then I think we should be
building/testing "maintenance" with 1.7, since that is the most likely
"lowest common denominator" actively being used at this point....
Actually, I would think we should be doing "maintenance" builds with all
three: 1.6, 1.7 and 1.8, just to check to make sure it works with any
Java version that Pivot 2.0.x will accept.... For "trunk" we could just
have 1.8 builds, since that is what we are targeting at this point.
Thoughts? Is this possible?
Thanks,
~Roger
On 5/16/17 4:09 PM, Sandro Martini wrote:
> Hi Roger,
> I changed the maintenance build from using Java 7 to Java 8 mainly because
> JRE 7 should not occurs any more now (instead of creating by scratch a new
> Jenkins job) ... if needed I can take a look.
>
> On trunk I agree that a build on Java 7 is no more needed, at least I could
> disable it.
>
> Bye
>
> Il 15/Mag/2017 23:35, "Roger and Beth Whitcomb" <Ro...@rbwhitcomb.com>
> ha scritto:
>
> Why do we no longer have a "Pivot-maintenance on Java 7" build? And why are
> we building "trunk" on Java 7 anymore? Maybe we got the two confused?
>
>
> On 5/15/17 1:09 PM, Apache Jenkins Server wrote:
>
>> See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java
>> %208/1120/display/redirect>
>>
>>
>>
>>
Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120
Posted by Sandro Martini <sa...@gmail.com>.
Hi Roger,
I changed the maintenance build from using Java 7 to Java 8 mainly because
JRE 7 should not occurs any more now (instead of creating by scratch a new
Jenkins job) ... if needed I can take a look.
On trunk I agree that a build on Java 7 is no more needed, at least I could
disable it.
Bye
Il 15/Mag/2017 23:35, "Roger and Beth Whitcomb" <Ro...@rbwhitcomb.com>
ha scritto:
Why do we no longer have a "Pivot-maintenance on Java 7" build? And why are
we building "trunk" on Java 7 anymore? Maybe we got the two confused?
On 5/15/17 1:09 PM, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java
> %208/1120/display/redirect>
>
>
>
>
Re: Jenkins build is back to normal : Pivot-maintenance on Java 8
#1120
Posted by Roger and Beth Whitcomb <Ro...@rbwhitcomb.com>.
Why do we no longer have a "Pivot-maintenance on Java 7" build? And why
are we building "trunk" on Java 7 anymore? Maybe we got the two confused?
On 5/15/17 1:09 PM, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/Pivot-maintenance%20on%20Java%208/1120/display/redirect>
>
>
>