gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "BAZLEY, Sebastian" <Sebastian.BAZ...@london.sema.slb.com>
Subject RE: Meaning of "runtime" (was: [PATCH] HttpClient HEAD dependenci es)
Date Thu, 08 Jan 2004 12:31:21 GMT
 -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@apache.org]
> Sent: 08 January 2004 07:53
> To: gump@jakarta.apache.org
> Subject: Re: Meaning of "runtime" (was: [PATCH] HttpClient HEAD
> dependencies)
> 
> 
> 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!


> 
> > 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:

By "run" do you mean the Ant "java" task ?
What about using a "junit" task to test JMeter - would that count as "run"?

In other words, how does Gump decide which tasks are run-time and which are
not?

S.

Mime
View raw message