| 1 |
Uwe Klosa wrote: |
| 2 |
> |
| 3 |
> Joshua Nichols wrote: |
| 4 |
>> Uwe Klosa wrote: |
| 5 |
>>>> Hi |
| 6 |
>>>> |
| 7 |
>>>> I've been using the migration overlay for about two weeks now and there haven't been any problems. I observed only one thing with the |
| 8 |
>>>> emerge of ant-1.6.5. When jdk-1.4 and jdk-1.5 are installed with 1.4 being the system vm the emerge of ant used 1.5 for compilation. I |
| 9 |
>>>> got ridd of that by removing 1.5. I don't know if this is a known issue or if it was only on my system where I had been using 1.5 as |
| 10 |
>>>> the system vm for quite some time. But this problem occured after migrating to the migration overlay and fixing all 1.5 issues. |
| 11 |
|
| 12 |
Same here, sun-jdk-1.4 set as system vm both for generation 1 and 2. |
| 13 |
|
| 14 |
# emerge -1 ant-core |
| 15 |
Calculating dependencies... done! |
| 16 |
>>> Emerging (1 of 1) dev-java/ant-core-1.6.5-r13 to / |
| 17 |
>>> checking ebuild checksums ;-) |
| 18 |
>>> checking auxfile checksums ;-) |
| 19 |
>>> checking miscfile checksums ;-) |
| 20 |
>>> checking apache-ant-1.6.5-src.tar.bz2 ;-) |
| 21 |
* Using: sun-jdk-1.5 |
| 22 |
>>> Unpacking source... |
| 23 |
<ctrl+c> |
| 24 |
|
| 25 |
>> Are you positive that you were using a 1.4 JDK for the system vm of |
| 26 |
>> generation 1? java-check-environment _should_ be checking for this, and |
| 27 |
>> warning you about i. If that's not the case, I'd be interested to see if |
| 28 |
>> you could replicate that behavior, because I certainly haven't had this |
| 29 |
>> problem. |
| 30 |
>> |
| 31 |
> |
| 32 |
|
| 33 |
I'm positive, java-check-environment reports no problem. |
| 34 |
|
| 35 |
BTW I thought the new system was to allow 1.5 jdk to be used for builds |
| 36 |
that are known to support it. Maybe it's the case of ant-core? |
| 37 |
|
| 38 |
Caster |
| 39 |
-- |
| 40 |
gentoo-java@g.o mailing list |
Archives