gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: Meaning of "runtime" (was: [PATCH] HttpClient HEAD dependenci es)
Date Thu, 08 Jan 2004 12:50:38 GMT
On Thu, 08 Jan 2004, Sebastian BAZLEY
<Sebastian.BAZLEY@london.sema.slb.com> wrote:
>> From: Stefan Bodewig [mailto:bodewig@apache.org]
>> Sent: 08 January 2004 07:53
>> On Tue, 6 Jan 2004, Sebastian Bazley
>> <Sebastian.Bazley@london.sema.slb.com> wrote:
>> 
>> > I don't understand how the runtime attribute is used *within* a
>> > project.
>> 
>> Not at all.
> 
> OK.
> 
> So the attribute is "altruistic" in the sense that it is only of use
> to others!

Yes 8-)

>> > For example JMeter has several types of dependency: - compile -
>> > test (needs the same jars as compile, plus the jars created from
>> > the complied classes) - printable docs (uses Anakia - which is
>> > not needed elsewhere - and does not need all the other jars)
>> > 
>> > So which of these are "runtime"?
>> 
>> Only those you need to run JMeter.
>> 
> 
> Sorry, but I'm still not sure what "run" means:

In that altruistic sense - whatever a user of JMeter would need.  You
mark as runtime in JMeter the things that anybody who wants to use
JMeter during building of his project would need.

> By "run" do you mean the Ant "java" task ?

I think I do.

> What about using a "junit" task to test JMeter - would that count as
> "run"?

Possibly so - but JUnit itself wouldn't become a runtime dependency
for anybody using JMeter to load-test his application at build time,
would it?

Stefan

Mime
View raw message