On 29/11/2012 2:14 PM, Mark Derricutt wrote:
Not "would" but I hazard an argument to say "could", there are subtle
API -signature- changes that make targetting older bytecode
problematic, aka from JDK5-6 I believe there were some methods ( class
escapes me now ) that used to take a String but now take a
CharSequence, source compatible but runtime-linker incompatible when
resolving the method.
I have never seen any java application fail just because I run the
version 7 VM. Even really old code still runs.
If building an older -target IMHO one should always use the toolchains
plugin or switch the whole VM to ensure the bootclasspath "of the
compile" uses the appropriate one.
I only use Eclipse to compile but I am able to specify any run-time that
I have installed to compile code even if my Eclipse and Maven run in
Java 7 VM.
If we did do this change - could we not have m-c-p make a big visible
"WARNING" about not locking down the source/target like we have with
no-versions for plugins?
Ron Wheeler wrote:
On 29/11/2012 12:48 PM, Stephen Connolly wrote:
You only get the new language features from after 1.5 if target >
1.5, so switching core to use the newer features would make core
incompatible with running on 1.5
Not sure that I understand how this follows.
The target compiler should not determine the Java VM that Maven runs in.
I believe that I can compile 1.5 while running maven in a Java 7 VM.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
