Wow! We've passed the equator!

Hi. I just noticed there's now more RESOLVED bugs (25) than unresolved ones (23) -- not counting enhancements. Sounds like it will soon be worth issuing a 1.8.1 Please help by looking at the pending bugs and: - Review and comment - Assign priorities and severities appropriately - Try to reprodu

cvs commit: jakarta-jmeter build.xml

jsalvata2003/01/10 16:15:36 Modified:.build.xml Log: Made diagnosing usage of deprecated APIs easier. Revision ChangesPath 1.83 +12 -8 jakarta-jmeter/build.xml Index: build.xml === R

DO NOT REPLY [Bug 7378] - HTTP Proxy Server doesn't do "https"

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

Re: Change log

Hey - I am much happier with that. I was assuming that the list was put together manually and was trying to help out. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com On 11/01/2003 9:09 AM, "Mike Stover" <[EMAIL PROTECTED]

JUnit in binary dist.

Mike wrote: I'm also wary of pulling JUnit from the distribution. How sure are you this won't be a problem? Have you tested all of JMeter's functionality without it? I've been thinking about this. You're right: as we discussed a while ago, we want to have the unit tests in the product's .java

Re: Change log

Mike Stover wrote: Ick. That's what cvs log messages are for. I have a little program that extracts the log messages from a huge log output - it makes it very easy to see what has changed since the last release, so long as people write meaningful cvs log comments. I'm with Mike on this. I do

Re: Change log

Ick. That's what cvs log messages are for. I have a little program that extracts the log messages from a huge log output - it makes it very easy to see what has changed since the last release, so long as people write meaningful cvs log comments. -Mike On 11 Jan 2003 at 8:59, Scott Eade wrote

Re: [re-vote] Coding standards

Scott Eade wrote: A vote needs to have a final conclusion, and I don't think the coding standards vote had one. Please vote on the following: 1. Switch from tabs to spaces for indentation. [The overwhelming consensus is for spaces, but I am retaining this here for one last round of objections -

Re: [VOTE] JMeter distribution packaging

Jordi Salvat i Alabart wrote: Hi. I've been playing with build.xml and the Gump configuration files. Looks like we'll shortly have useable nightly builds. In the process, I've rearranged the way jmeter is packed, with two intents: 1/ Trying to be more consistent with how other jakarta projects

Re: Non-gui broken on Linux - Attn: Oliver

Scott Eade wrote: [snip] Whether or not the attached fix is correct depends on the long term plans are for PluginManager. I have taken the view that it may actually do more than just deal with icons and have thus passed it a flag indicating whether or not a gui is to be used so that it can then o

Change log

How about when we do a commit we also update the changes.xml file with a brief description of our efforts - this will make it easier to enumerate the changes when we next do a release. I'll add my changes in the next day or so. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http:/

Re: JMeter site

> Do you all have accounts on jakarta.apache.org? I don't, AFAIK. I asked [EMAIL PROTECTED] to get one, but got no answer. Having the docs in CVS makes it convenient, because all you need to do is log in to jakarta.apache.org, cd to the right directory, and type "cvs update -d", and you're do

Re: (Clarification) RE: [re-vote] Coding standards

Unless someone is going to scream out whenever they spot a *minor* violation of the selected coding standard then the discussion is moot. IMO the reason we are deciding upon a coding stand is so that we can all produce fairly consistent looking code without each of us having to reformat the code t

Re: (Clarification) RE: [re-vote] Coding standards

Boutcher, James K. wrote: Did I vote +1 for Turbine's standards? No, you voted +0. Which AFAIK, means you're for it but not ready to do the work. Or am I wrong in this interpretation? > And, please don't try to infer that I'm changing text to suit some > motives of mine. [...] You didn't cha

Re: JMeter site

Publishing the docs nightly, from my experience, would be a bad idea. We don't see the problem now, when we're just tweaking things here and there. The problem comes in when you're getting ready to release JMeter 1.9 - then, wholesale changes will be needed, by multiple people, over a period of a

DO NOT REPLY [Bug 15252] - URL Rewriter doesn't work in non-GUI mode

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

DO NOT REPLY [Bug 15252] - URL Rewriter doesn't work in non-GUI mode

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

RE: (Clarification) RE: [re-vote] Coding standards

Did I vote +1 for Turbine's standards? And, if they say "use two blank lines here", and "use one blank line here" - please explain how "one" and "single" are somehow not synonymous? It says "One blank line should always be used" - it does NOT say "One or more blank lines should always be used".

DO NOT REPLY [Bug 8961] - utf8 url encoding not supported by deffault in jdk's older than 1.4

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

DO NOT REPLY [Bug 14618] - jMeter 1.8 doesn't seem to run under Windows 98

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

JMeter site

Hi. As you may be aware of, I broke the way the JMeter site used to be published :-( I still believe the approach of keeping in CVS only things that can't be obtained from source is cleaner, and better in the long term; but I need to reinstate a practical way to publish the docs. Possible way

Re: (Clarification) RE: [re-vote] Coding standards

H... Turbine's includes Sun's. There's no way to get one without the other. Anyway, looks like these sections you're citing are pretty subject to interpretation: they say you must use one blank line here, but it doesn't say you can't use one more, do they? You had to add the word "single"

(Clarification) RE: [re-vote] Coding standards

I thought my negative 1 might need some explanation: >>2. Adopt Sun's coding standards >>(http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html) >> >> James K Boutcher: -1 I'm all for clean coding, and I'm also for 95% of Sun's coding convention doc. Some of it goes a bit far, I think

RE: [re-vote] Coding standards

1. Switch from tabs to spaces for indentation. [The overwhelming consensus is for spaces, but I am retaining this here for one last round of objections - but remember this is consensus voting where the majority rule] James K Boutcher: +0 2. Adopt Sun's coding standards (http://java.sun.c

RE: [VOTE] JMeter distribution packaging

> VOTE: Rename the distribution files from ApacheJMeter.* to jakarta-jmeter.* James K Boutcher: +1 > VOTE: Put only binaries (the bare minimum needed to run JMeter) into the > binary distribution file. James K Boutcher: +1 -- To unsubscribe, e-mail: For additional

Re: JMeter distribution packaging

The "dist" target should also make a source-only distribution too, in this case. I was thinking about this... I have some doubts: Currently Gump is taking care of building the nightly src snapshots. Do we really need to do our own? Should these replace the gump-made ones? Which mechanism sho

cvs commit: jakarta-jmeter build.xml

jsalvata2003/01/10 07:42:04 Modified:.build.xml Log: We don't need junit in the binaries. Revision ChangesPath 1.82 +0 -2 jakarta-jmeter/build.xml Index: build.xml === RCS file: /ho

Re: [VOTE] JMeter distribution packaging

On 10 Jan 2003 at 3:45, Jordi Salvat i Alabart wrote: > Hi. > > I've been playing with build.xml and the Gump configuration files. Looks > like we'll shortly have useable nightly builds. > > In the process, I've rearranged the way jmeter is packed, with two intents: > 1/ Trying to be more consi

Re: [re-vote] Coding standards

Mike Stover: +0 to all. On 10 Jan 2003 at 14:43, Scott Eade wrote: > A vote needs to have a final conclusion, and I don't think the coding > standards vote had one. > > Please vote on the following: > > 1. Switch from tabs to spaces for indentation. > [The overwhelming consensus is for spaces,

cvs commit: jakarta-jmeter/src/core/org/apache/jmeter/timers/gui AbstractTimerGui.java

seade 2003/01/10 05:59:51 Modified:src/core/org/apache/jmeter/timers Timer.java src/components/org/apache/jmeter/timers/gui ConstantThroughputTimerGui.java GaussianRandomTimerGui.java ConstantTimerGui.java

cvs commit: jakarta-jmeter/src/core/org/apache/jmeter/resources messages_no.properties messages_ja.properties messages.properties messages_de.properties

seade 2003/01/10 05:52:04 Modified:src/core/org/apache/jmeter/resources messages_no.properties messages_ja.properties messages.properties messages_de.properties Log: Defines the missing running_test value that is reported wen running

cvs commit: jakarta-jmeter/src/functions/org/apache/jmeter/functions IntSum.java

seade 2003/01/10 05:44:31 Modified:xdocs/usermanual component_reference.xml src/core/org/apache/jmeter/resources messages_no.properties messages_ja.properties messages.properties messages_de.properties Added: src/fu

cvs commit: jakarta-jmeter/src/core/org/apache/jmeter/resources messages_no.properties messages.properties messages_ja.properties messages_de.properties

dgulino 2003/01/07 18:07:34 Modified:src/components/org/apache/jmeter/assertions/gui SizeAssertionGui.java src/components/org/apache/jmeter/assertions SizeAssertion.java src/core/org/apache/jmeter/resources mes

cvs commit: jakarta-jmeter/xdocs contributing.xml

kcassell2003/01/07 06:23:21 Modified:xdocscontributing.xml Log: "Cassell" instead of "Cassel" Revision ChangesPath 1.10 +1 -1 jakarta-jmeter/xdocs/contributing.xml Index: contributing.xml ===

cvs commit: jakarta-jmeter/src/components/org/apache/jmeter/visualizers StatVisualizer.java

seade 2003/01/06 18:54:50 Modified:src/components/org/apache/jmeter/visualizers StatVisualizer.java Log: Fixed a minor i18n mistake. Removed unused imports. Revision ChangesPath 1.8 +8 -11 jakarta-jmeter/src/components/org/apach

cvs commit: jakarta-jmeter/src/components/org/apache/jmeter/assertions ResponseAssertion.java

seade 2003/01/06 18:09:50 Modified:src/components/org/apache/jmeter/assertions ResponseAssertion.java Log: Made PatternCache static and used READ_ONLY patterns - this fixes a NPE that occurs in remote sessions. Revision ChangesPath 1.3 +9

Unit tests broken

Please remember to run "ant test" or "./build.sh test" before committing your changes. [java] There was 1 failure: [java] 1) testGUIComponents(org.apache.jmeter.junit.JMeterTest)junit.framework.AssertionFailedError: GUI-CLASS: Failed on org.apache.jmeter.assertions.gui.SizeAssertionGu

cvs commit: jakarta-jmeter build.xml

jsalvata2003/01/10 06:09:27 Modified:.build.xml Log: Improving "dist" target: better dist packages, packages javadoc, runs tests. Revision ChangesPath 1.81 +93 -53jakarta-jmeter/build.xml Index: build.xml ===

Re: jmeter-dev commit message

Scott Eade wrote: Hi, It seems that the jmeter-dev commit message are backed up again. Can someone please give these a kick along. Thanks, Scott, You probably are better directing list issues to [EMAIL PROTECTED] (I've copied this one). Usually the first commit from a committer to a list w

DO NOT REPLY [Bug 15426] - New function __intSum()

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

DO NOT REPLY [Bug 14618] - jMeter 1.8 doesn't seem to run under Windows 98

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

Re: [VOTE] Coding standards

> > 1. Switch from tabs to spaces for indentation. > > [The overwhelming consensus is for spaces, but I > am retaining this here for > > one last round of objections - but remember this > is consensus voting where > > the majority rule] Vote +1 > > 2. Adopt Sun's coding standards > > > (http://jav

Re: [VOTE] JMeter distribution packaging

> VOTE: Rename the distribution files from > ApacheJMeter.* to jakarta-jmeter.* Vote +1 > > VOTE: Put only binaries (the bare minimum needed to > run JMeter) into the > binary distribution file. Vote +1 __ Do you Yahoo!? Yahoo! Mail Plus - Powerfu

Re: [VOTE] JMeter distribution packaging

+1 for both -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: [re-vote] Coding standards

+1 for all four -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: JMeter distribution packaging

The docs will be packaged with the binaries, since users will need them. I'm thinking about what to do with javadocs. I'll most likely pack them separately, since doing otherwise is most difficult. Salut, Jordi. Michal Kostrzewa wrote: VOTE: Rename the distribution files from ApacheJMeter.* to

Re: [VOTE] JMeter distribution packaging

VOTE: Rename the distribution files from ApacheJMeter.* to jakarta-jmeter.* Michal Kostrzewa: +1 VOTE: Put only binaries (the bare minimum needed to run JMeter) into the binary distribution file. Michal Kostrzewa: +1 What about the docs? best regards Michal Kostrzewa -- To unsubscribe, e-mail:

AW: [VOTE] Coding standards

And for this one also +1 for all four votes, Wolfram -- To unsubscribe, e-mail: For additional commands, e-mail:

AW: [VOTE] JMeter distribution packaging

+1 on both (though I think a vote wouldn't have been necessary for it). Greetings, Wolfram P.S.: A bit under pressure at work AND private therefore rather loosely watching than actively working. This should end (at latest) around march... -- To unsubscribe, e-mail:

[VOTE] Coding standards

1. Switch from tabs to spaces for indentation. [The overwhelming consensus is for spaces, but I am retaining this here for one last round of objections - but remember this is consensus voting where the majority rule] Scott Eade: +1 Jordi Salvat: +1 2. Adopt Sun's coding standards (http://