Mercurial > hg > Blog

comparison content/Maven/cross-jdk-project-files-continued.md @ 98:1d9382b0329b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Specify the syntax on markdown blocks to avoid broken output that has class=err
author Dirk Olmes <dirk@xanthippe.ping.de>
date Thu, 19 Dec 2019 10:04:33 +0100
parents 4cd9b65e10e4
children
comparison
equal deleted inserted replaced
97:e99db3bc53c1 98:1d9382b0329b
4 4
5 In [my last blog entry](|filename|./cross-jdk-project-files.md) I described the steps for cross-JDK Eclipse project files. 5 In [my last blog entry](|filename|./cross-jdk-project-files.md) I described the steps for cross-JDK Eclipse project files.
6 6
7 Unfortunately there's more Eclipse internals involved when dealing with cross platform issues. It turns out that the correct JRE_CONTAINER for Linux and Windows is 7 Unfortunately there's more Eclipse internals involved when dealing with cross platform issues. It turns out that the correct JRE_CONTAINER for Linux and Windows is
8 8
9 :::shell
9 org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk 10 org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk
10 11
11 but that doesn't work for Mac where it needs to be like this: 12 but that doesn't work for Mac where it needs to be like this:
12 13
14 :::shell
13 org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.launching.macosx.MacOSXType/jdk 15 org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.launching.macosx.MacOSXType/jdk
14 16
15 So for real cross platform project files you need to put the launcher type into a property and override that in a mac specific profile. The final pom will look similar to this 17 So for real cross platform project files you need to put the launcher type into a property and override that in a mac specific profile. The final pom will look similar to this
16 18
17 :::xml 19 :::xml