Bug 151674

Summary: Installation error when installing tomcat5030 rpm
Product: [Retired] Red Hat Application Server Reporter: Permaine Cheung <pcheung>
Component: tomcatAssignee: Fernando Nasser <fnasser>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-28 14:30:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Permaine Cheung 2005-03-21 17:19:13 UTC
Description of problem:
On a clean machine, install the tomcat5030 rpm, errors about not finding Java
extension for this JVM come up.
This is actually an installer issue since the dependencies for tomcat5030 are
not installed before tomcat5030 itself.

Version-Release number of selected component (if applicable):
tomcat5030-5.0.30-4rh.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1. install the tomcat5030 rpm
2.
3.
  
Actual results:
* header for tomcat5030-5.0.30-4rh.noarch.rpm has no disc location tag, assuming
it's on the current CD
/usr/bin/build-jar-repository: error: could not find commons-beanutils Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find commons-fileupload Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find commons-digester Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find commons-logging Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find commons-modeler Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find commons-el Java extension
for this JVM
/usr/bin/build-jar-repository: error: could not find regexp Java extension for
this JVM
/usr/bin/build-jar-repository: error: could not find jmxri Java extension for
this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
/usr/bin/build-jar-repository: error: could not find commons-collections Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find commons-dbcp Java extension
for this JVM
/usr/bin/build-jar-repository: error: could not find commons-pool Java extension
for this JVM
/usr/bin/build-jar-repository: error: could not find commons-logging-api Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find commons-el Java extension
for this JVM
/usr/bin/build-jar-repository: error: could not find jaf Java extension for this JVM
/usr/bin/build-jar-repository: error: could not find jta Java extension for this JVM
/usr/bin/build-jar-repository: error: could not find jmxri Java extension for
this JVM
/usr/bin/build-jar-repository: error: could not find jspapi Java extension for
this JVM
/usr/bin/build-jar-repository: error: could not find servletapi5 Java extension
for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
/usr/bin/build-jar-repository: error: could not find jaxp_parser_impl Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find xml-commons-apis Java
extension for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
/usr/bin/build-jar-repository: error: could not find jakarta-taglibs-core Java
extension for this JVM
/usr/bin/build-jar-repository: error: could not find jakarta-taglibs-standard
Java extension for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
/usr/bin/build-jar-repository: error: could not find struts-1.1 Java extension
for this JVM
/usr/bin/build-jar-repository: error: All specified jars were not found for this jvm
error: %post(tomcat5030-5.0.30-4rh) scriptlet failed, exit status 7 

Expected results:
Successful installation without any errors

Additional info:

Comment 1 Fernando Nasser 2005-09-28 14:30:49 UTC
Perhaps it was fixed on the update.