[gentoo-dev] JBoss 'source' ebuild vs. Tomcat 'binary' ebuild

[Lars Willemsens <lwillems@easynet.be>]

Hi,

I have recently been trying to compile JBoss from source, first by using 
the JBoss ebuild and then by manually compiling the latest version of 
JBoss (3.0.6).
When compiling with the ebuild for version 3.0.1_rc1 I came across bug 
10014 which is, I think, due to the fact that I use Blackdown's JDK 
version 1.4.1_01.
When compiling JBoss 3.0.6 manually I came across a trivial error where 
a certain Ant build file (build.xml) was lacking a target named 'all'. 
Apparently someone else came across another trivial compilation bug in 
an earlier release (release 3.0.4, bug 15642).

It seems to me that the JBoss source releases are filled with trivial 
bugs in the build system and that those source releases are not meant to 
be compileable without some fine tuning. The parts of JBoss that do 
compile generate an enormous amount of warnings.

Tomcat's ebuild, downloads the binary release and installs that. So I 
wonder why certain ebuilds download Java source and others download Java 
binaries (when both are available).

Wouldn't it be better if the JBoss ebuild would download the binary 
release just like the Tomcat ebuild? The alternative would be to write a 
set of patches for each new JBoss release that would fix the 'bugs' in 
JBoss's build system for that release, but as I said I have the 
impression that the source releases are 'snapshots' that are taken when 
the JBoss code itself was stable (not caring about the build system).
I am, of course, willing to write such an ebuild, but only if it would 
be of any use. Such an ebuild could also be provided as an alternative 
to the source ebuild.

Cheers,
Lars




--
gentoo-dev@gentoo.org mailing list