Re: [gentoo-java] Split migration-packages

[Calvin Austin <caustin@spikesource.com>]

I've been working through about 130 packages to gen2 using prefix'd 
builds (EAPI="prefix"), it was an interesting challenge to move 
everything to JDK 5.0 and I have a few fixes and new ebuilds etc to 
commit somewhere. I have the following thoughts on making JDK 5 stable.

1. source vs jars ebuilds.
I built everything from source minus one jar file. I had to drop to 
source 1.4 or patch the code in some cases. However some projects are 
based on maven jar repositories, getting a source version of these can 
be a huge project in itself.

2. Using open source components vs certified binary components.
Downloading certified jars from Sun or other vendors was a pain, however 
picking up a free implementation that may have never been certified may 
be just as bad if you don't know what you are doing (and caused a long 
tail of dependencies of cause)

3. Varying dependencies
I ended up with a very simple hibernate 3.1 ebuild for example, the 
current migration ebuild essentially pulls in the rest of jboss

regards
calvin

Krzysiek Pawlik wrote:

>As of now all packages ported to generation 2 are moved from
>gentoo-java-experimental to migration-packages.
>
>Any new migrated package has to be moved to migration-packages as well.
>It will ease integration of ported packages into the portage tree.
>
>  
>

-- 
gentoo-java@gentoo.org mailing list