Point is, unless you are using java 1.3, until 2.5ish you have had the
<source>1.5</source> and <target>1.5</target> in your pom anyway.

So changing the default from 1.5 to 1.7 will not make life any harder for
you as you'll just be putting back in the <source>1.5</source> and
<target>1.5</target> (assuming you didn't keep it there, because its safer)

On 29 November 2012 10:06, Stadelmann Josef wrote:

I don't love that as a default! because there are OS which do not yet have
up-to-date Open JDK 7 or JDK 8.
And we do not have influence to the company not delivering as they should,
years after promising that Java is
what we need for future OpenVMS developments. Or has someone knowledge
when HP releases a Open JDK 7.0? And yes,
we know, changing a platform with 25 to 30 year old business algorithms
written in PASCAL, today integrated with
Java to form part of a larger web-service server on OpenVMS is not so
easy. Legacy code has value too, not only
legacy data!

-----Ursprüngliche Nachricht-----
Von: Mark Derricutt
Gesendet: Mittwoch, 28. November 2012 19:36
An: Maven Users List
Betreff: Re: Why does mvn compiile using java 1.3?

Now that Oracle are controlling Java on OSX we can no longer "blame Apple"
- I'd love to see the default become Java 7 now.

And if one needs to lock down to the older versions, lock them down.

On 29/11/2012, at 7:07 AM, Curtis Rueden wrote:

Good to know that Maven is now only 8 years behind.
I blame Apple.

To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 15 of 32 | next ›
Discussion Overview
groupusers @
postedNov 16, '12 at 9:43a
activeNov 29, '12 at 8:42p



site design / logo © 2021 Grokbase