配置Maven为不同的J2SE版本使用不同的JDK？

发布于 2024-10-12 17:26:54 字数 594 浏览 5 评论 0原文

我想将 Maven2 配置为使用 sun-java6-jdk 构建 Java SE 1.6 模块，并使用 openjdk-7 构建 Java SE 1.7 模块。是否可以？

然后，Maven2 应该自动选择正确的 JDK，以便在一个命令中构建不同的模块。

例如，它应该

$ mvn package

代替

$ cd module1
$ update-alternatives ... jdk6 ...
$ mvn package
...
$ cd module2
$ update-alternatives ... jdk7 ...
$ mvn package

P.S.这与 pom.xml 文件无关，这些文件已经使用不同的、设置了 maven-compiler-plugin不同模块的值。如果我选择使用 openjdk-7，Maven2 将生成 1.6 版本的类文件，但使用 openjdk-7 而不是 sun-java6-jdk。问题是如何配置 Java SE 配置文件。

原文

I want to configure Maven2 to use sun-java6-jdk to build Java SE 1.6 modules, and use openjdk-7 to build Java SE 1.7 modules. Is it possible?

Maven2 should then auto choose the correct JDK to build different modules in one command.

For example, it should be

$ mvn package

instead of

$ cd module1
$ update-alternatives ... jdk6 ...
$ mvn package
...
$ cd module2
$ update-alternatives ... jdk7 ...
$ mvn package

P.S. It's nothing about pom.xml files, which have already been setup maven-compiler-plugin with different <source>, <target> values for different modules. If I choose to use openjdk-7, Maven2 will generate version 1.6 class files, but using openjdk-7 rather then sun-java6-jdk. The question is about how to configure Java SE profiles.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

甜心 2024-10-19 17:26:54

我们通过在编译插件的配置中明确指定 javac 来解决这个问题（将 JAVA_HOME_6 和 JAVA_HOME_7 定义为环境变量）：

对于 Java 6 模块

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <source>1.6</source>
        <target>1.6</target>
        <showDeprecation>true</showDeprecation>
        <showWarnings>true</showWarnings>
        <executable>${env.JAVA_HOME_6}/bin/javac</executable>
        <fork>true</fork>
    </configuration>
</plugin>

和 Java 7 模块

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <source>1.7</source>
        <target>1.7</target>
        <showDeprecation>true</showDeprecation>
        <showWarnings>true</showWarnings>
        <executable>${env.JAVA_HOME_7}/bin/javac</executable>
        <fork>true</fork>
    </configuration>
</plugin>

we solved this problem by explicitely sepecify the javac in config of compile plugin (with JAVA_HOME_6 and JAVA_HOME_7 defined as environment variables):

and for Java 6 module

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <source>1.6</source>
        <target>1.6</target>
        <showDeprecation>true</showDeprecation>
        <showWarnings>true</showWarnings>
        <executable>${env.JAVA_HOME_6}/bin/javac</executable>
        <fork>true</fork>
    </configuration>
</plugin>

and for Java 7 module

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <source>1.7</source>
        <target>1.7</target>
        <showDeprecation>true</showDeprecation>
        <showWarnings>true</showWarnings>
        <executable>${env.JAVA_HOME_7}/bin/javac</executable>
        <fork>true</fork>
    </configuration>
</plugin>

回复收藏 0 原文

浊酒尽余欢 2024-10-19 17:26:54

您可以告诉 maven-compiler-plugin 使用不同的 JDK 编译源

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-compiler-plugin</artifactId>
  <version>2.3.2</version>
  <configuration>
    <executable><!-- path-to-javac --></executable>
  </configuration>
</plugin>

You can tell the maven-compiler-plugin to Compile Sources Using A Different JDK

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-compiler-plugin</artifactId>
  <version>2.3.2</version>
  <configuration>
    <executable><!-- path-to-javac --></executable>
  </configuration>
</plugin>

回复收藏 0 原文

深海里的那抹蓝 2024-10-19 17:26:54

从 @lweller 的回答的众多赞成票中，我猜这很奇怪，但是使用 1.7 作为 source 和 target maven 仍然尝试使用 java 1.5。而仅使用 7...就像这样：

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <source>7</source> <!-- see here, says only 7, not 1.7 -->
        <target>7</target> <!-- here as well -->
        <showDeprecation>true</showDeprecation>
        <showWarnings>true</showWarnings>
        <executable>${env.JAVA_HOME_7}/bin/javac</executable>
        <fork>true</fork>
    </configuration>
</plugin>

maven-compiler-plugin 版本 2.5.1。

From the numerous upvotes on @lweller's answer I guess it's wierd, but with 1.7 as source and target maven still tried to compile using java 1.5. Rather only with 7... Like so:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <source>7</source> <!-- see here, says only 7, not 1.7 -->
        <target>7</target> <!-- here as well -->
        <showDeprecation>true</showDeprecation>
        <showWarnings>true</showWarnings>
        <executable>${env.JAVA_HOME_7}/bin/javac</executable>
        <fork>true</fork>
    </configuration>
</plugin>

maven-compiler-plugin version 2.5.1.

回复收藏 0 原文

~没有更多了~