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" <rogerandb...@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>
