Re: [gentoo-java] migration-overlay entering main tree

[Wiktor Wandachowicz]

Here are my experiences with Java upgrade on a second machine, done step
after step like in the Java Upgrade Guide. Sorry for the length, but I wanted
to be as specific as possible.

After unmasking packages, I removed sun-jdk-1.4*, sun-jdk-1.5* and java-config.
Then I emerged java-config-1* and java-config-2*. All was fine. After emerging
the first JVM I've noticed an error:

# emerge -av =sun-jdk-1.4*
...
!!! ERROR: The active vm could not be found
 *  After installing sun-jdk-1.4.2.12 this
 *  was set as the default JVM to run.
 * No valid generation-1 system-vm set, setting to sun-jdk-1.4.2.12

Nothing serious that a simple "/usr/sbin/env-update && source /etc/profile"
couldn't resolve. And only after two last commands the "java-check-environment"
was able to report success with generation_1_system_vm. I double checked
via "java-config-1 -L" and "java-config-2 -L" that only one JVM was present at
the moment. All was fine.

Then I emerged sun-jdk-1.5 and run the "java-1.5-fixer". Now it became
interesting, because the tool reported *twice* missing packages:

# java-1.5-fixer
 * You need to emerge portage-utils.
# emerge -av portage-utils
 * You need to emerge >=javatoolkit-0.1.6
# emerge -av javatoolkit
# java-1.5-fixer

Well, that's was a little surprise, because the Guide didn't mention these
two packages at all. Not actually confusing for me, but the Guide could at
least explain that need. Less fluent Gentooers can be surprised and
completely unnecessary topics on the forums may arise.

Another intriguing thing was the output while emerging javatoolkit. I've seen:
...
>>> /usr/share/doc/javatoolkit-9.9.9/
>>> /usr/share/doc/javatoolkit-9.9.9/sun-fetch/
>>> /usr/share/doc/javatoolkit-9.9.9/sun-fetch/AUTHORS
>>> /usr/share/doc/javatoolkit-9.9.9/sun-fetch/README
>>> /usr/share/doc/javatoolkit-9.9.9/COPYING
>>> /usr/share/doc/javatoolkit-9.9.9/NEWS
>>> /usr/share/doc/javatoolkit-9.9.9/findclass/
>>> /usr/share/doc/javatoolkit-9.9.9/findclass/AUTHORS
>>> /usr/share/doc/javatoolkit-9.9.9/findclass/README
>>> /usr/share/doc/javatoolkit-9.9.9/AUTHORS
>>> /usr/share/doc/javatoolkit-9.9.9/README
>>> /usr/share/doc/javatoolkit-9.9.9/ChangeLog
>>> /usr/share/doc/javatoolkit-9.9.9/TODO

even though I installed javatoolkit-0.1.9 and not -0.9.9

Last problematic thing I've noticed was the number and order of
packages java-fixer was about to repair:

# java-1.5-fixer
 * Generating a list of jars which ant uses ...                          [ ok ]
 * Checking for > 1.4 bytecode in ant jars ...                           [ ok ]
 * Generating a list of jars in the system ...                           [ ok ]
 * Checking for > 1.4 bytecode in system jars ...                        [ ok ]
 * Attempting to fix broken packages ...
 * Packages to fix this run:
=dev-db/hsqldb-1.7.3.1-r2 =dev-db/hsqldb-1.7.3.1-r2
=dev-db/hsqldb-1.7.3.1-r2 =dev-java/servletapi-2.3-r2
=sys-libs/db-4.3.29

I turned out that even though hsqldb was listed three times, it still
depended on servletapi, which was scheduled fourth. So it broke:

classes:
    [javac] Compiling 111 source files to
/var/tmp/portage/hsqldb-1.7.3.1-r2/work/hsqldb/classes
    [javac] /var/tmp/portage/hsqldb-1.7.3.1-r2/work/hsqldb/src/org/hsqldb/Servlet.java:73:
cannot access javax.servlet.ServletConfig
    [javac] bad class file:
/var/tmp/portage/hsqldb-1.7.3.1-r2/work/hsqldb/lib/servlet.jar(javax/servlet/ServletConfig.class)
    [javac] class file has wrong version 49.0, should be 48.0
    [javac] Please remove or make sure it appears in the correct
subdirectory of the classpath.
    [javac] import javax.servlet.ServletConfig;
    [javac]                      ^
    [javac] 1 error

I needed to remerge servletapi manually and restart java-1.5-fixer. Which,
of course, built hsqldb three times :-( Which was, of course, unnecessary.
How about at least making the packages that java-1.5-fixer is going to fix
unique? And how about figuring a better ordering of packages?

After all the above I think I've finally migrated my machine to Generation-2.
Whoopiee!

In general all was fun and problems were minor IMHO. But migration was
not automatic, like some users would like it to see. Maybe some things
coul dbe improved before stabilization?

HTH,
Wiktor Wandachowicz

-- 
Registered Linux user #390131 (http://counter.li.org)
-- 
gentoo-java@g.o mailing list