|
Lines 259-291
Link Here
|
| 259 |
</body> |
259 |
</body> |
| 260 |
</section> |
260 |
</section> |
| 261 |
<section id="preferred-vm"> |
261 |
<section id="preferred-vm"> |
| 262 |
<title>Preferred VM</title> |
262 |
<title>Preferred Build VM</title> |
| 263 |
<body> |
263 |
<body> |
| 264 |
|
264 |
|
| 265 |
<p> |
265 |
<p> |
| 266 |
While merging Java packages, the VM can and will be switched as necessary. |
266 |
While merging Java packages, the VM used for building can sometimes be different |
|
|
267 |
from the one currently set as the system VM. |
| 267 |
</p> |
268 |
</p> |
| 268 |
|
269 |
|
| 269 |
<p> |
270 |
<p> |
| 270 |
Because of the wide variety of available VMs, we do not have the resources to |
271 |
This merge time VM switching is needed when, for example, your system-vm is |
| 271 |
test and verify every package works on all of them. So to ensure that every |
272 |
set to a 1.6 VM and the package you are merging requires a 1.5 VM. While merging |
| 272 |
packages merges smoothly, we have defined a list of <e>default/supported |
273 |
it will select and use a 1.5 VM, leaving your system-vm choice intact. |
| 273 |
VMs</e> per arch. You can find them in |
|
|
| 274 |
<path>/usr/share/java-config-2/config/jdk-defaults.conf</path>. When you are |
| 275 |
merging a Java package, and it detects one of the VM in that file is installed, |
| 276 |
it will automatically use that VM, instead of the system-vm. |
| 277 |
</p> |
274 |
</p> |
| 278 |
|
275 |
|
| 279 |
<p> |
276 |
<p> |
| 280 |
The merge time VM switching is also needed when, for example, your system-vm is |
277 |
To define which VM is selected when a switch is needed, we have created a list of <e>default/supported |
| 281 |
set a 1.4 VM and the package you are merging requires a 1.5 VM. While merging |
278 |
VMs</e> per arch. You can find them in |
| 282 |
it will use the preferred 1.5 VM, leaving your system-vm choice intact. |
279 |
<path>/usr/share/java-config-2/config/jdk-defaults.conf</path>. |
| 283 |
</p> |
280 |
</p> |
| 284 |
|
281 |
|
| 285 |
<p> |
282 |
<p> |
| 286 |
Of course, Gentoo is all about choice, so you can override these defaults in |
283 |
Of course, Gentoo is all about choice, so you can override these defaults (and even your |
|
|
284 |
selected system VM) in |
| 287 |
<path>/etc/java-config-2/build/jdk.conf</path> and have complete control over |
285 |
<path>/etc/java-config-2/build/jdk.conf</path> and have complete control over |
| 288 |
which VM will get used. Some examples: |
286 |
which VM will get used for merging. Some examples: |
| 289 |
</p> |
287 |
</p> |
| 290 |
|
288 |
|
| 291 |
<pre caption="Example /etc/java-config-2/build/jdk.conf"> |
289 |
<pre caption="Example /etc/java-config-2/build/jdk.conf"> |
|
Lines 307-314
Link Here
|
| 307 |
|
305 |
|
| 308 |
<warn> |
306 |
<warn> |
| 309 |
You do not <e>have</e> to edit this file. If you change these options to use a |
307 |
You do not <e>have</e> to edit this file. If you change these options to use a |
| 310 |
unsupported VM, things could possibly break. Bugs reported with a unsupported VM |
308 |
unsupported VM, things could possibly break. Because of the wide variety of available |
| 311 |
won't be prioritized as much as bugs present within supported VMs. |
309 |
VMs, we do not have the resources to test and verify every package works on all of them. |
|
|
310 |
Bugs reported with a unsupported VM won't be prioritized as much as bugs present within |
| 311 |
supported VMs. |
| 312 |
</warn> |
312 |
</warn> |
| 313 |
|
313 |
|
| 314 |
</body> |
314 |
</body> |
