Although, re-thinking this, one of the reasons I wanted it in the properties file is so that different users could easily disable different items to customize JMeter for their purposes. I'm imagining that, a year from now, there could well be literally hundreds of JMeter plug-in components, and who wants to see them all? Probably, if I'm doing web testing, I just don't want to see database, SMTP, FTP, EJB components....
-Mike > -----Original Message----- > From: Stover, Michael [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 02, 2001 9:10 AM > To: 'JMeter Developers List' > Subject: RE: Question > > > It should work. You can also try putting the string returned by > "getClassLabel()" in the not_in_menu list. Also make sure > there aren't > breaks in the line. > > I like the idea of adding a method into the interface of > JMeterComponentModel. That's probably the best option. > > -Mike > > > -----Original Message----- > > From: Scott Coleman [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, November 01, 2001 9:59 AM > > To: 'JMeter Developers List' > > Cc: Scott Coleman > > Subject: Re: Question > > > > > > Hi All > > > > I am adding a new protocol and a configuration component. The > > configuration > > component should not be added to the popup menu. I have added this > > components class name to the not_in_menu list in the > > jmeter.properties file, > > but it is still displayed. Any hints? > > Also has anyone thought about adding a new interface to > > declare that the > > component should be added to the menu? > > > > Regards > > Scott > > > > -- > > To unsubscribe, e-mail: > > <mailto:jmeter-dev-> [EMAIL PROTECTED]> > > For > > additional commands, > > e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: > <mailto:jmeter-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
