Mercurial > hg > Blog

comparison content/Maven/default-jdk-for-cross-jdk-profiles.md @ 56:483a5f25ccb6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
update the nabble link
author Dirk Olmes <dirk@xanthippe.ping.de>
date Sun, 04 Jan 2015 05:55:08 +0100
parents 4cd9b65e10e4
children
comparison
equal deleted inserted replaced
55:3f6c9b512b85 56:483a5f25ccb6
2 Date: 2009-04-25 2 Date: 2009-04-25
3 Lang: en 3 Lang: en
4 4
5 In my [previous blog post about Cross JDK project files with Maven](|filename|./cross-jdk-project-files-continued.md) I described a way to generate a custom JDK name into the Eclipse project files using the `maven-eclipse-plugin`. 5 In my [previous blog post about Cross JDK project files with Maven](|filename|./cross-jdk-project-files-continued.md) I described a way to generate a custom JDK name into the Eclipse project files using the `maven-eclipse-plugin`.
6 6
7 That approach still had one shortcoming: you would either have to rename your JDK to match the default configured in the POM or you would have to give the JDK name on the commandline. Now I stumbled over a [good tip on the maven user's list](http://n2.nabble.com/org.apache.maven.plugins%3Amaven-eclipse-plugin%3A2.7-SNAPSHOT-ignores--maven-compiler-plugin-tp2689287p2689425.html) that allows you to configure a sensible, cross platform default for the JDK. 7 That approach still had one shortcoming: you would either have to rename your JDK to match the default configured in the POM or you would have to give the JDK name on the commandline. Now I stumbled over a [good tip on the maven user's list](http://maven.40175.n5.nabble.com/org-apache-maven-plugins-maven-eclipse-plugin-2-7-SNAPSHOT-ignores-maven-compiler-plugin-td120284.html#a120285) that allows you to configure a sensible, cross platform default for the JDK.
8 8
9 In short, the trick is not to use a concrete name of a JDK but to specify the name of a Java runtime environment. Eclipse automatically tries to match any configured JDK to an internal list of runtime environments. 9 In short, the trick is not to use a concrete name of a JDK but to specify the name of a Java runtime environment. Eclipse automatically tries to match any configured JDK to an internal list of runtime environments.
10 10
11 So if you put the following into your pom: 11 So if you put the following into your pom:
12 12