Point taken.
Not sure it would make sense to have more than one classpath in a
TestPlan, so perhaps the best place for it would be to add it to the
TestPlan element.
However ...
If the extra class-path entries are only needed whilst running a test,
then it should be fairly straightforward to upd
Hi,
I think it makes a perfect sense to keep a class paths with a test plan.
In this case one will be able to open a new test plan and the class
paths will be modified according to plan content. If class paths are set
as a properties, one needs to restart JMeter.
sebb wrote:
Not sure it's
Not sure it's necessary to have a GUI to do this.
The additional classpaths are probably known before starting JMeter,
so would it not be simpler to use a property to define the extra
classpaths?
S.
On 15/09/05, Peter Lin <[EMAIL PROTECTED]> wrote:
> I'm planning on adding another feature to the
I'm planning on adding another feature to the 2.1 branch and provide a way
for users to add classpaths to JMeter in the GUI.
I was thinking of something like User Defined Classpath. Users can then
select the jar files they want and the config element will add them to the
classloader. Any though
4 matches
Mail list logo
