Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 899103 (JBEWS-131)

Summary: EWS - tomcat 5 tests from the source bundle
Product: [JBoss] JBoss Enterprise Web Server 1 Reporter: Aleksandar Kostadinov <akostadinov>
Component: unspecifiedAssignee: Coty Sutherland <csutherl>
Status: CLOSED EOL QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: EWS 1.0.0.GACC: akostadinov, jclere, pcheung, rebecca.jboss
Target Milestone: ---   
Target Release: TBD EWS   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEWS-131
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-04 15:06:18 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ews_tctestbuild.xml none

Description Aleksandar Kostadinov 2009-03-23 15:52:43 UTC 
Date of First Response: 2009-03-24 12:45:10
project_key: JBEWS

Hallo,

On last EWS QE meeting we talked about that we and customers that want to run project's test suite over the installation will need a change to the tomcat 5 build scripts.

For tomcat 6 one can specify -Dtomcat.build and have the tests executed against these binaries. Tomcat 5 is not that easy. There are a number of modules
apache-tomcat-5.5.27-src]$ find . -name test
./connectors/jk/jkstatus/test
./connectors/jk/test
./connectors/jk/test/org/apache/ajp/test
./connectors/ajp/ajplib/test
./connectors/coyote/src/test
./connectors/http11/src/test
./connectors/jni/test
./container/catalina/src/test
./container/modules/cluster/test
./container/modules/groupcom/test
./container/modules/groupcom/test/java/org/apache/catalina/tribes/test
./container/modules/ha/test
./container/modules/storeconfig/test
./container/modules/storeconfig-ha/test
./commons-pool-1.4-src/src/test
./commons-dbcp-1.2.2-src/src/test

And for example looking at container/catalina the only way one can execute against external binaries is modifying "test.classpath" definition in build.xml to remove references to built classes and include the EWS distribution binaries.

So can such modification of modules' build files be done in the distributed to customers sources?
Comment 1 Permaine Cheung 2009-03-24 16:45:10 UTC 
What are the exact changes needed and is container/catalina/build.xml the only file that needs updating?
Comment 2 Aleksandar Kostadinov 2009-03-24 17:41:24 UTC 
I think every component we ship needs the change.
Comment 4 Permaine Cheung 2009-03-24 20:15:53 UTC 
Moving this to the next CP
Comment 5 Permaine Cheung 2010-01-04 15:17:21 UTC 
Hi Alex,
Can you please specify the exact changes needed, and which files need to be updated?

Thanks,
Permaine
Comment 7 Aleksandar Kostadinov 2010-01-26 19:00:44 UTC 
Yes, please move it to the next CP. IIRC we have considered that a low risk and it is a time consuming task to modify a test suite in such a way.
Comment 8 Permaine Cheung 2010-01-26 19:12:01 UTC 
Moving to the next CP.
Comment 9 Ondřej Žižka 2010-02-04 14:34:03 UTC 
Link: Added: This issue related JBQA-3065
Comment 10 Ondřej Žižka 2010-02-04 14:59:52 UTC 
Link: Added: This issue related JBQA-3040
Comment 11 Permaine Cheung 2010-08-05 13:46:36 UTC 
Dave, can you please look into this? Thanks!
Comment 12 Anne-Louise Tangring 2010-10-28 19:08:50 UTC 
Permaine to ping Dave again. Candidate for 1.0.2
Comment 13 David Knox 2010-11-03 17:09:31 UTC 
Hi, 

After reviewing the build files, I think the solution is an Ant build script that is owned by the EWS build. As I see it, this Ant script would consolidate the test locations and run each in a sequence. A property can point to the customer's installation. It would assume the EWS directory structure when defining the classpath. The EWS build would contain this build file and inject it into the distribution. This has not been an issue upstream, so I recommend we make this an EWS 'feature' versus a tomcat5 feature. 

Does that satisfy the requirements? 
-- dave
Comment 14 Permaine Cheung 2011-03-16 16:32:17 UTC 
Dave, QE think that's ok as a fix. Do we have enough time to put this into EWS 1.0.2? If so, please move this back to 1.0.2.
Comment 15 David Knox 2011-04-14 15:58:21 UTC 
good, we're agreed. There are some security fixes for RHEL and Fedora tomcats that need to be done first. This is on my short list.
Comment 16 David Knox 2011-04-21 18:39:38 UTC 
Experimental script
Comment 17 David Knox 2011-04-21 18:39:38 UTC 
Attachment: Added: ews_tctestbuild.xml
Comment 18 David Knox 2011-04-21 18:46:29 UTC 
Aleks - Take a look at the attached experimental script to see if is what you wanted. Only the http11 target is filled out for now. The script is documented.

I'm having trouble running due to a security exception: signer information does not match signer information of other classes in the same package.