| 1 |
On Mon, 2006-12-25 at 00:15 +0100, Enrico Weigelt wrote: |
| 2 |
> |
| 3 |
> Well, they told me, I won't need them ... who the hell's right ? |
| 4 |
|
| 5 |
Your asking users questions you should be asking the Tomcat developers. |
| 6 |
Most all Tomcat users never ever even get close to compiling Tomcat. |
| 7 |
Either ask the developers, or don't take any ones word and go look at |
| 8 |
the sources. There is a build.properties.default file, which is pretty |
| 9 |
much all you need to determine Tomcat's dependencies. |
| 10 |
|
| 11 |
For the most part users are clueless and by posting there just opened up |
| 12 |
a can of worms. Much less all kinds of false impressions of the state of |
| 13 |
Tomcat on gentoo. Thanks for that, although I assume it was not done in |
| 14 |
spite or to cause the Gentoo community grief. If so, die now :) |
| 15 |
|
| 16 |
> In other words: tomcat ships lots of bundled third-party packages, |
| 17 |
> while gentoo takes them from the upstream ? |
| 18 |
|
| 19 |
Ships a few, and uses even more that are not shipped to build Tomcat. At |
| 20 |
the moment we are leaving the build time stuff linked in at runtime. It |
| 21 |
does no harm since the stuff is already on your system. If anything it's |
| 22 |
a few less commonly used libs on has to link in. |
| 23 |
|
| 24 |
> But then I wonder: if the tomcat folks can simply bundle them in, |
| 25 |
> why does gentoo has to suffer from these download restrictions ? |
| 26 |
|
| 27 |
Because instead of using every apps bundled dependencies. We install a |
| 28 |
dependency once, and as many apps can link to it as needed. Less |
| 29 |
duplicate more re-use. |
| 30 |
|
| 31 |
> hmm, we should do some deeper investigations @ dev@tomcat ... |
| 32 |
|
| 33 |
It's a waste of time. Upstream devs are not to responsive, and TC 5.5.x |
| 34 |
is not really being actively developed. All efforts are going towards |
| 35 |
Tomcat 6.0.x which was WAY less deps. |
| 36 |
|
| 37 |
> Okay, since I'm not using it in production yet, I'll try the masked 6.0.6. |
| 38 |
|
| 39 |
Fine, I will likely unmask it soon and version the ebuild. Despite |
| 40 |
upstream sources not being versioned with beta or alpha. :( |
| 41 |
|
| 42 |
> BTW: |
| 43 |
> |
| 44 |
> What does the jni useflag actually do ? Switch between java and native |
| 45 |
> implementation of certain things (SSL, and what else?) ? |
| 46 |
|
| 47 |
It will build the libtcnative.so or Tomcat's SSL accelerator. Which for |
| 48 |
some reason they ship tarred up sources to in the binary Tomcat. Not to |
| 49 |
mention Tomcat 6.0.x sources have the native sources in it, yet ant is |
| 50 |
set to download a tarball of the sources. It's quite a mess. |
| 51 |
|
| 52 |
So at the moment the JNI flag does nothing, but cause breakage. Ideally |
| 53 |
it will build and install libtcnative.so. So Tomcat can use it, |
| 54 |
hopefully out of the box. At which time we will be one of the only |
| 55 |
distros providing that ;) |
| 56 |
|
| 57 |
> And it seems that ecj is used instead of the default java compiler. |
| 58 |
> Can't jikes be used instead of ecj (IMHO, should be faster) ? |
| 59 |
|
| 60 |
Tomcat devs decided to switch to ecj. Both ecj and jikes come from IBM. |
| 61 |
Jikes is no longer being developed. ecj is actively being developed. ecj |
| 62 |
is faster than jikes, and many will argue it's faster than javac. Thus |
| 63 |
upstream switching to it. |
| 64 |
|
| 65 |
Also because of this, Tomcat only requires a JRE at runtime, not a full |
| 66 |
JDK anymore ;) |
| 67 |
|
| 68 |
-- |
| 69 |
William L. Thomson Jr. |
| 70 |
Gentoo/Java |
Archives