You mean *not* a runtime dependency, right? Ant is almost always a
"compile time only" dependency.
Only for clarity ('cos we are agreeing) I was trying to speak "gump". I
meant:
That would require properly marking up the runtime attributes, which
is not
| dist| test
--
build| build | test
compile | compile-time| test-compile
run | runtime | test-time
Hmm this grows to something like
dist
test
build
build
test
compile
compile-time
test-compile
run
runtime
test-time
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
I'd add test-compile and test-runtime. JUnit is often necessary for both,
but rarely for the production code compile/runtime itself. But maybe you put
these in build? --DD
> -Original Message-
> From: Nick Chalko [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 24, 2003 11:15 AM
> To: Gump
Stefan Bodewig wrote:
On Thu, 24 Jul 2003, Nick Chalko <[EMAIL PROTECTED]> wrote:
But can we capture teh difference betwwen "build" time and "compile"
time dependencies into gump
Are there any compile time dependencies (i.e. things your code
imports) that are not runtime dependencies as w
On Thu, 24 Jul 2003, Nick Chalko <[EMAIL PROTECTED]> wrote:
> But can we capture teh difference betwwen "build" time and "compile"
> time dependencies into gump
Are there any compile time dependencies (i.e. things your code
imports) that are not runtime dependencies as well?
"build time" would b
Stefan Bodewig wrote:
On Thu, 24 Jul 2003, Nick Chalko <[EMAIL PROTECTED]> wrote:
Ant is almost always a "compile time only" dependency.
Most the time it is not a compile time dependency, just the tool
used to compile.
s/compile/build/ in my sentence.
OK?
agree,.
But can we c
On Thu, 24 Jul 2003, Nick Chalko <[EMAIL PROTECTED]> wrote:
>>Ant is almost always a "compile time only" dependency.
>>
> Most the time it is not a compile time dependency, just the tool
> used to compile.
s/compile/build/ in my sentence.
OK?
Stefan
Stefan Bodewig wrote:
On Thu, 24 Jul 2003, Adam Jack <[EMAIL PROTECTED]> wrote:
Maybe a choice could be to ignore changes for components that are a
"runtime" dependency.
You mean *not* a runtime dependency, right? Ant is almost always a
"compile time only" dependency.
Most the time it
Hola a todos:
I'm actually de moderator of gump list, i will go on vacation from 5/08
to 25/08, and i need to recruit someone to take that role, anyone
interested, please send me private mail, and we will solve the bloody
details..
Thanks in advance..
Saludos,
Ignacio J. Ortega
---
On Thu, 24 Jul 2003, Adam Jack <[EMAIL PROTECTED]> wrote:
> Maybe a choice could be to ignore changes for components that are a
> "runtime" dependency.
You mean *not* a runtime dependency, right? Ant is almost always a
"compile time only" dependency.
That would require properly marking up the r
> BTW: I really wish we could improve gump to be smarter and (1) only
> re-build something if something inside it (or below) has changed
At least for the "full" Gumps this will be more or less useless as Ant
changes quite often - and all projects depend on Ant.
May
Stefan Bodewig wrote, On 24/07/2003 10.58:
On Wed, 23 Jul 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
I mean, would it pertain to Gump to have code that does nagging that
is not necessarily related to building something?
In a certain sense it already does when a build contains checkstyle
On Wed, 23 Jul 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
> I mean, would it pertain to Gump to have code that does nagging that
> is not necessarily related to building something?
In a certain sense it already does when a build contains checkstyle
reports and style violations have been
dims2003/07/22 07:00:30
Modified:project xml-axis-wsil.xml xml-axis.xml xml-rpc.xml
xml-soap.xml
Log:
- Updated nag for ws.apache.org projects
- Added xmlunit dependency to Axis.
Revision ChangesPath
1.5 +1 -1 jakarta-gump/project
15 matches
Mail list logo
