You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/09/23 21:50:07 UTC

DO NOT REPLY [Bug 23366] New: - JMeter restricts classpath to jars

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23366>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23366

JMeter restricts classpath to jars

           Summary: JMeter restricts classpath to jars
           Product: JMeter
           Version: 1.9
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: jweder@icsaward.com


We are developing an enterprise business system in Java/J2EE. I am unable to 
add tests that can run under JMeter because I cannot set the classpath 
properly. I require setting the classpath to a path. The current implementation 
restricts this to jars only. 

Please help. There is no way that I'm gonna jar up all my classes in order to 
use JMeter. We like it otherwise. If you want to support the entire Java stack, 
then let the user set up the classpath. JMeter can still include all its jars 
like it currently does.