On 11/19/2015 04:01 PM, Kay Schenk wrote:
>
>
> On 11/17/2015 11:50 PM, Damjan Jovanovic wrote:
>> Building AOO with Java 8's very strict javadoc tool was fixed in SVN trunk
>> only, by r1697228, r1697237, r1697247, r1697306, and r1697312, so yes it
>> should work well for building AOO now, and it's the only version I've been
>> testing for months on FreeBSD. Base works, wizards work, beanshell scripts
>> works, bvt/fvt/pvt tests generally pass (I haven't compared test results
>> with different Java versions).
>>
>> LibreOffice supposedly builds with Java 6.
>>
>> Java 7 added major new language features, like try-with-resources,
>> diamonds, switch on strings, so requiring Java >= 7 would be good for
>> development purposes. But then users can't use any older JRE version, which
>> might be a problem for unofficial Java implementations that are a little
>> behind (see
>> http://en.wikipedia.org/wiki/Comparison_of_Java_virtual_machines).
>> When last I checked, the only fast JVM on the Raspberry Pi with the hard
>> float (hf) kernel was CACAO, which only supports Java 1.6.
>>
>> A while ago I did find a way to change the bytecode and class file version
>> of the class files produced by Java 1.7's javac, to make most language (as
>> opposed to API) features work on 1.6 and 1.5 JREs. I even have a Maven
>> plugin to do this. I can look into it again if necessary?
>>
>> Oh and should we maybe use Maven for building Java code instead of
>> dmake/gbuild/ant?
>>
>> Damjan
>
> Thanks for the feedback. I hope we can get responses from Windows
> and Mac builders soon.
OK, it's been a few weeks now and I'd like to get back to this.
Are there any objections to using Java 8 instead of the combination
of Java 6 and 7 that we have now?
>
> ...and, why do you like Maven instead of what we have now?
>
>>
>> On Wed, Nov 18, 2015 at 12:17 AM, Kay Schenk <kay.sch...@gmail.com> wrote:
>>
>>> We seem to have a number of numer of Java related discussions of
>>> late. Here's another one -- the Java version we're using for builds.
>>>
>>> Java 6 went out of update status quite some time ago -- Feb. 2013 --
>>> and this is still being used for our Linux builds, and Windows
>>> builds if our current binaries are produced with the same
>>> configuration as the buildbot configurations.
>>>
>>> Java 7 reached end-of-life in April, 2015.
>>>
>>> Yesterday, I installed Java 8 -- openjdk version "1.8.0_65" -- on my
>>> CentOS 6.7 (32 bit) and built. Testing resulted in OK results for
>>> the little I did. I was concerned about the Base portion with the
>>> installed hsqldb but so far everything is OK.
>>>
>>> Is anyone else on other platforms using Java 8 for successful
>>> building and testing? Windows builders? Mac builders? Others? Given
>>> that in our next release, we will be out of the 4.1.x branch (I
>>> think), I would think we could jump up to Java 8. I would expect
>>> that our users would be on Java 8 already.
>>> --
>>> --------------------------------------------
>>> MzK
>>>
>>> “Somebody's gotta win, somebody's gotta lose.
>>> Just don't fight about it.
>>> Just try to get better."
>>> -- Yogi Berra
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
>>
>
--
--------------------------------------------
MzK
"Somebody's gotta win, somebody's gotta lose.
Just don't fight about it.
Just try to get better."
-- Yogi Berra
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
