[ http://jira.codehaus.org/browse/MNGECLIPSE-133?page=all ]
Eugene Kuleshov closed MNGECLIPSE-133:
--------------------------------------
Resolution: Won't Fix
How does "invalid target release: 1.6" error in javac justify for issue in this
plugin? Besides -target 1.6 said allowed in the documentation link you reffered
to, so it is sounds like a bug in javac.
In any case plugin is configuring JDT options and more over takes anythithing
that is declared in pom.xml. There are no plans to ensure correctness of the
options.
> Update Source Folders changes project JDK incorrectly when using Java 6.
> ------------------------------------------------------------------------
>
> Key: MNGECLIPSE-133
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-133
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Dependency Resolver
> Versions: 0.0.9
> Environment: Windows XP SP2; JDK 1.6.0-beta2-b86; Eclipse 3.1.2;
> Reporter: Mark Soderquist
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> I believe this is something that Sun has done to you just recently with JDK
> 1.6 build 85 or 86 (I'm not sure which since I jumped from 84 to 86.)
> According to the javac
> documentation(http://download.java.net/jdk6/docs/technotes/tools/windows/javac.html#source)
> the -source values of 1.6 and 6 are not valid since no language changes
> occurred in Java 6. Changing the JDK in the Eclipse project based on the
> source value in the POM file may not work from now on. According to the
> documentation the target flag still allows the 1.6 value but running javac
> with -source 1.5 and -target 1.6 give an "invalid target release: 1.6" error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
