blocks|key|2926749|text|您已经将%25JAVA_HOME设置为JDK1.7，但是您正在尝试使用1.8进行编译。安装JDK1.8并确保您的%25JAVA_HOME指向该版本，或者将目标版本降至1.7。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2926750|2926751|无效目标版本:+1.8|blockquote|2926752|2926753|2926754|目标版本指的是jdk版本。|2926755|entityMap^0|4|A|1I|A|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|U|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|V|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|W|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|X|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|Y|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|O|$]]

You have set your <code>%JAVA_HOME</code> to jdk 1.7, but you are trying to compile using 1.8. Install jdk 1.8 and make sure your <code>%JAVA_HOME</code> points to that or drop the target release to 1.7. 

<blockquote>
 invalid target release: 1.8
</blockquote>

The target release refers to the jdk version.

blocks|key|139643|text|将值放入插件中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139644|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-compiler-plugin</artifactId>
++++<version>3.1</version>
++++<configuration>
++++++++<source>1.8</source>
++++++++<target>1.8</target>
++++</configuration>
</plugin>|code-block|syntax|javascript|139645|使用了以下错误：|139646|<source>${java.version}</source>
<target>${java.version}</target>|139647|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Put the value in the plugin:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
 &lt;version&gt;3.1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;source&gt;1.8&lt;/source&gt;
 &lt;target&gt;1.8&lt;/target&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

The error was use:

<pre><code>&lt;source&gt;${java.version}&lt;/source&gt;
&lt;target&gt;${java.version}&lt;/target&gt;
</code></pre>

blocks|key|141902|text|把它放到你的.profile中将会动态的照顾你的$JAVA_HOME|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|141903|export+JAVA_HOME=$(/usr/libexec/java_home)|code-block|syntax|javascript|141904|然后关闭您的shell，打开一个新的shell并使用|141905|echo+$JAVA_HOME|141906|它应该显示类似这样的内容|141907|/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home|141908|如果不是，请在启动脚本中删除JAVA_HOME的任何其他分配。请记住，这些启动脚本以.开头，因此在使用*通配符时，它们是隐藏的，不会被包括在内，例如，如果您想要grep主目录的所有文件，则需要：|BOLD|141909|grep+-s+JAVA_HOME+~/.*+--exclude=.bash_history|141910|entityMap^0|O|A|0|0|0|0|0|0|0|4|16|1|1F|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|15|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|17|8|@$9|18|A|19|B|U]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|V|3|W|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|X|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|Y|$]]

Putting that in your .profile will dynamically take care of your <code>$JAVA_HOME</code>

<pre><code>export JAVA_HOME=$(/usr/libexec/java_home)
</code></pre>

Close your shell afterwards, open a new one and test with

<pre><code>echo $JAVA_HOME
</code></pre>

It should display something like

<pre><code>/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home
</code></pre>

If not, remove any other assignments of JAVA_HOME in your startup scripts. Remember, that these startup scripts start with a <code>.</code> so they are hidden and won't be included when using <code>*</code> wildcard, e.g. if you want to grep all files of your home directory, you need to:

<pre><code>grep -s JAVA_HOME ~/.* --exclude=.bash_history
</code></pre>

blocks|key|143142|text|在我的例子中，maven的“运行配置”使用了错误的JRE+(1.7)。确保选中Run+->+Run+Configurations+->+(Tab)+JRE+to++jdk1.8.x。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|143143|entityMap^0|13|12|29|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

In my case the maven "Run configuration" was using the wrong JRE (1.7). Be sure to check Run -> Run Configurations -> (Tab) JRE to be some jdk1.8.x.

blocks|key|2926802|text|当我的JDK指向1.7，而JRE指向1.8时，这个问题就解决了。通过键入以下命令，签入命令提示符|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926803|java+-version|code-block|syntax|javascript|2926804|和|2926805|javac+-version|2926806|两者应该是相同的。|2926807|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The issue was resolved as I was having a JDK pointing to 1.7 and JRE pointing to 1.8. Check in the command prompt by typing
<pre><code>java -version
</code></pre>
and
<pre><code>javac -version
</code></pre>
Both should be same.

blocks|key|141932|text|我面临的问题是，我能够从命令提示符创建maven构建，但不能从Eclipse.What构建。在eclipse中，我更改了运行配置以指向JDK中的JRE文件夹，而不是只将其留在JDK文件夹中，因为standard.This解决方案可能对您也有效，但如果且仅当所有java路径都正确时，java和javac显示的版本与pom.xml的目标中显示的版本相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141933|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The problem I was facing was that I was able to make a maven build from the command prompt but not from Eclipse.What worked for me in eclipse is that I changed the run configuration to point to JRE folder inside of JDK rather than leaving it in JDK folder only as per the standard.This solution may work for you as well but try this if and only if all the java paths are correct, java and javac are showing the same version as present in the target of pom.xml.

blocks|key|140880|text|在我的案例中起作用的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|140881|我打开pom.xml并替换其中一个插件，如下所示。|offset|length|style|CODE|140882|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-compiler-plugin</artifactId>
++++<version>3.2</version>
++++<configuration>
++++++++<source>1.7</source>
++++++++<target>1.7</target>
++++</configuration>
</plugin>|code-block|syntax|javascript|140883|在我编辑源标记和目标标记之前，我将其更改为1.7，它就起作用了。|140884|entityMap^0|0|3|7|0|0|L|3|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

What worked in my case is this:

I opened the <code>pom.xml</code> and replaced the one of the plug-ins as below.

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
 &lt;version&gt;3.2&lt;/version&gt;
 &lt;configuration&gt;
 &lt;source&gt;1.7&lt;/source&gt;
 &lt;target&gt;1.7&lt;/target&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

Before I edited the source and target tags both had <code>1.8</code>, I changed that to <code>1.7</code> and it worked.

blocks|key|141968|text|这个问题没有明确地问到Docker，但是当我有一个目标是1.9的pom.xml文件时，我收到了同样的错误...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141969|<properties>
++<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
++<maven.compiler.source>1.9</maven.compiler.source>
++<maven.compiler.target>1.9</maven.compiler.target>
</properties>|code-block|syntax|javascript|141970|..。但随后试图通过指定"maven“本身来对Docker容器运行测试。|141971|docker+run+-t+--rm+-v+m2_repository:/root/.m2/repository+-v+$(pwd):/work+-w+/work+maven+mvn+-e+test|141972|对我来说，修复方法是针对我需要的确切版本。|141973|docker+run+-t+--rm+-v+m2_repository:/root/.m2/repository+-v+$(pwd):/work+-w+/work+maven:3.5.2-jdk-9+mvn+test|141974|(您可以使用。)|141975|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

This question wasn't asking explicitly about Docker, but I received the same error when I had a pom.xml file that was targeting 1.9...

<pre><code>&lt;properties&gt;
 &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
 &lt;maven.compiler.source&gt;1.9&lt;/maven.compiler.source&gt;
 &lt;maven.compiler.target&gt;1.9&lt;/maven.compiler.target&gt;
&lt;/properties&gt;
</code></pre>

... but then tried to run tests against a Docker container by specifying "maven" by itself. 

<pre class="lang-none prettyprint-override"><code>docker run -t --rm -v m2_repository:/root/.m2/repository -v $(pwd):/work -w /work maven mvn -e test
</code></pre>

For me, the fix was to target the exact version I needed.

<pre class="lang-none prettyprint-override"><code>docker run -t --rm -v m2_repository:/root/.m2/repository -v $(pwd):/work -w /work maven:3.5.2-jdk-9 mvn test
</code></pre>

(You can <a href="https://hub.docker.com/_/maven/" rel="nofollow noreferrer">learn more here</a>.)

blocks|key|2714397|text|对于eclipse，我是如何解决我的问题的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2714398|2714399|首选项-->编译器-->编译器抱怨级别(更改为1.8)+|ordered-list-item|2714400|2714401|📷|atomic|offset|length|2714402|​|2714403|JAVA+->安装的|2714404|+-->选择+SE+8+1.8+|unordered-list-item|2714405|2714406|2714407|2714408|使用Run+as+maven+build通过maven重建|2714409|。|2714410|2714411|它应该不会再显示无效目标错误。|2714412|注意:我不需要在终端中设置或更改任何其他变量。希望这能有所帮助。|2714413|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/8d66374e413189e935e6df41917ddbf7.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/44e24ff68eef39b27640c25854ebc669.png^0|0|0|0|0|0|1|0|0|0|0|0|0|0|1|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1H|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1J|8|@]|9|@$J|1K|K|1L|1|1M]]|A|$]]|$1|L|3|M|5|6|7|1N|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1O|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1P|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|T|3|H|5|I|7|1R|8|@]|9|@$J|1S|K|1T|1|1U]]|A|$]]|$1|U|3|M|5|6|7|1V|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1W|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|1X|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|20|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|21|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B|1C|-4]]|1D|$5|17|18|19|A|$1A|1E|1C|-4]]]]

For eclipse here is how I solved my problem:

<ol>
<li>Preferences --> Compiler --> Compiler Complainer Level (Change to 1.8)
<a href="https://i.stack.imgur.com/9gtYV.png" rel="noreferrer"><img src="https://i.stack.imgur.com/9gtYV.png" alt="enter image description here"></a></li>
<li>Perferences --> Installed JREs --> select JAVA SE 8 1.8
<a href="https://i.stack.imgur.com/lFh3A.png" rel="noreferrer"><img src="https://i.stack.imgur.com/lFh3A.png" alt="enter image description here"></a></li>
<li>Rebuild via maven using Run as maven build.</li>
</ol>

It shouldn't show you the invalid target error anymore. 
Note: I didn't have to set or change any other variables in my terminal.
Hope this helps.

blocks|key|2714583|text|我在Dokku上部署时遇到了这个问题，出于某种原因，它选择了JDK+1.7|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2714584|创建system.properties文件并设置java.runtime.version=1.8解决了此问题。Dokku现在使用JavaV8。Choosing+a+JDK+on+Heroku|offset|length|style|CODE|2714585|我以前从来没这么做过...|2714586|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/heroku/heroku-buildpack-java^0|0|2|H|O|O|1Z|O|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]|$D|V|E|W|F|G]]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I faced this issue deploying on Dokku, for some reason it was choosing JDK 1.7

Creating a <code>system.properties</code> file and setting <code>java.runtime.version=1.8</code> solved the issue. Dokku now uses Java version 8.
<a href="https://github.com/heroku/heroku-buildpack-java" rel="nofollow noreferrer">Choosing a JDK on Heroku</a> 

I Never had to do it before...

blocks|key|2927289|text|在Windows机器上，您可以临时设置Java版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2927290|例如，要将版本更改为Java8，请在cmd上运行以下命令：|offset|length|style|CODE|2927291|set+JAVA_HOME=C:\\...\jdk1.8.0_65|code-block|syntax|javascript|2927292|entityMap^0|0|I|3|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

On Windows machine you can temporarily set Java version. 
For example, to change the version to Java 8, run this command on <code>cmd</code>: 

<pre><code>set JAVA_HOME=C:\\...\jdk1.8.0_65
</code></pre>

blocks|key|2714627|text|执行强制Maven更新，它将带来兼容的1.8Jar版本，然后在构建时，将Execute环境中的JRE版本从Run+Configurations更新到1.8，然后点击RUN|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2714628|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Do a force Maven Update which will bring the compatible 1.8 Jar Versions and then while building, update the JRE Versions in Execute environment to 1.8 from Run Configurations and hit RUN

blocks|key|2927336|text|如果您使用的是Eclipse+IDE，请进入窗口菜单并选择首选项，然后在其中搜索已安装的JRE，然后选择构建项目所需的JRE|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2927337|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are using Eclipse IDE then go inside Window menu and select preferences and there you search for installed JREs and select the JRE you need to build the project

blocks|key|139903|text|正如Camila+Macedo所提到的，您必须明确指出编译器插件的java版本。对于spring+boot，您可以通过next属性来执行此操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139904|++<properties>
++++<java.version>1.8</java.version>
++++<maven.compiler.release>8</maven.compiler.release>
++</properties>|code-block|syntax|javascript|139905|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

As mentioned by Camila Macedo - you have to explicitly point the java version for compiler-plugin. For spring boot you can do that by next property:

<pre><code> &lt;properties&gt;
 &lt;java.version&gt;1.8&lt;/java.version&gt;
 &lt;maven.compiler.release&gt;8&lt;/maven.compiler.release&gt;
 &lt;/properties&gt;
</code></pre>

blocks|key|2927452|text|使用IntelliJ，我只需要安装另一个(更高)的版本。重新启动IDE后，一切正常，甚至所有的依赖关系都得到了解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2927453|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Using IntelliJ I just had to install another (higher) JDK Version. After restarting IDE, everything worked and even all dependencies were solved.

blocks|key|141174|text|在我的例子(IntelliJ)中，我需要检查是否为maven设置了正确的Runner：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141175|141176|Preferences|ordered-list-item|141177|Build，Execution，Deployment|141178|Maven+->+Runner|141179|141180|​|141181|📷|atomic|offset|length|141182|141183|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6d4297bad9993789d6de590dd43db6eb.png|imageAlt^0|0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|15|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|18|8|@]|9|@$P|19|Q|1A|1|1B]]|A|$]]|$1|R|3|L|5|6|7|1C|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z|10|-4]]]]

In my case (IntelliJ), I needed to check if I had the right Runner for maven:
<ol>
<li>Preferences</li>
<li>Build, Execution, Deployment</li>
<li>Maven -&gt; Runner</li>
</ol>
<a href="https://i.stack.imgur.com/OHSxI.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/OHSxI.png" alt="Preferences" /></a>

blocks|key|139953|text|当我尝试将我的spring+boot项目部署到heroku时，我也遇到了类似的问题，尽管我的问题是invalid+target+release:+11。我通过添加一个新文件system.properties来解决这个问题，添加到该文件的内容是java.runtime.version=11+(对于我来说，我使用的是JDK11)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|139954|entityMap^0|1D|Q|2E|H|3D|N|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

I have similar problem when I was trying to deploy my spring boot project to heroku, although my problem is <code>invalid target release: 11</code>.
I solved it by adding a new file <code>system.properties</code> and the content added to the file is <code>java.runtime.version=11</code> (For me I am using JDK 11).

blocks|key|143517|text|NETBEANS编译错误:无法在项目doit上执行目标编译(+org.apache.maven.pluginsmaven-compiler-plugin3.1compile+-)致命错误编译无效的目标发行版11+-1|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|143518|我是如何解决问题的：+.Right点击项目。属性的.Go。源上的.Click。将.Go转换为源代码/二进制格式并更改为最新版本|143519|在我的例子中(1.8)|143520|entityMap^0|2G|J|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

NETBEANS
Error:
Failed to execute goal org.apache.maven.pluginsmaven-compiler-plugin3.1compile (default-compile) on project doit Fatal error compiling invalid target release 11 - [Help 1]
How I solved my problem:
.Right click on the project.
.Go to Properties.
.Click on Source.
.Go to Source/Binary Format and change to the latest version
In my case (1.8)

blocks|key|2927527|text|首先，如果您使用的是eclipse，请检查Build+Path+->+Configure+Build+Path+->+Java+Build+Path，看看您的项目使用的是哪个java版本。我推荐使用Java+1.8。其次，检查pom.xml文件。按ctrl+%2BF搜索文本"java.version“=>将其更改为1.8。第三，安装Java1.8，然后将JAVE_HOME路径更改为指向Java1.8文件夹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2927528|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

First, if you are using eclipse, please check Build Path -&gt; Configure Build Path -&gt; Java Build Path, see which java version your project is using. I recommend using Java 1.8.
Second, check the pom.xml file. ctrl + F to search the text &quot;java.version&quot; =&gt; change it to 1.8.
Third install Java 1.8 and then change your JAVE_HOME path to point to Java 1.8 folder.

Similar problem like one posted on <a href="https://stackoverflow.com/questions/19891423/invalid-target-release-1-7">invalid target release: 1.7</a> but after following the blog my problem is still unresolved.

<blockquote>
 Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project hm_app: Fatal error compiling: invalid target release: 1.8 -> [Help 1]
</blockquote>

I was following <a href="http://maven.apache.org/guides/getting-started/index.html" rel="noreferrer">as tutorial</a> when I faced this problem.

<pre><code>abt java &amp; mvn

C:\mvn&gt;echo %JAVA_HOME% 
C:\mvn&gt;echo %JRE_HOME%
C:\mvn&gt;echo %MAVEN_HOME% yields
</code></pre>

outputs

<pre><code>C:\Program Files\Java\jdk1.7.0_51
C:\Program Files\Java\jre7
C:\apache-maven-3.0.4
</code></pre>

Fatal error compiling: invalid target release: 1.8 -> [Help 1]

编译器

Windows

Eclipse

容器

Docker

Java

类似于在上发布的问题，但是在关注了博客之后，我的问题仍然没有得到解决。无法在项目hm_app上执行目标org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (默认编译)：致命错误编译:无效的目标版本: 1.8 ->帮助1当我遇到这个问题时，我正在关注。ab...

问编译时发生致命错误:无效的目标版本: 1.8 -> [帮助1]
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编译时发生致命错误:无效的目标版本: 1.8 -> [帮助1]EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编译时发生致命错误:无效的目标版本: 1.8 -> [帮助1]
EN