Still no answer to this question ...
Let me clarify :
RPM policies insist in having NO binary packages
included or required to build or deploy and use
a tool.
It's allready the case for JSSE, and if I build
RPM against JSSE to have SSL stuff compiled, the
requirement is not mandatory for run time operation.
But now with all the required jars, it just impossible
to have a 100% clean RPM since many of the needed jars
should be obtained from Sun.
I could be relax a little with RPM packaging rules but
we should have all the needed jars somewhere at apache.org.
Questions: Could we have the needed jars in a tarball somewhere
in TC 4.0 dist dir ?
-
Henri Gomez ___[_]____
EMAIL : [EMAIL PROTECTED] (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-----Original Message-----
>From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, September 20, 2001 12:37 PM
>To: [EMAIL PROTECTED]
>Subject: TC 4.0 RPM Packaging - WAS: [ANNOUNCEMENT] Apache Tomcat 4.0
>Fina l Release
>
>
>Hi to all,
>
>I've got many problems with TC 4.0 RPM packaging,
>since many jars used Sun licenses and so I couldn't
>have them included in TC 4.0, since it will broke
>RPM packaging policies.
>
>I'm also packaging tyrex, which include jta, but
>that inclusion is not following RPM packs rules.
>
>Questions:
>
>Could you include JAF/JNDI/LDAP/JMX jars in TC 4.0 tarball ?
>All the others could be found in jakarta for examples
>
>
>
>-
>Henri Gomez ___[_]____
>EMAIL : [EMAIL PROTECTED] (. .)
>PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
>PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>
