Re: build time vs. runtime dependency

[Brett Porter]

While this would work, it doesn't address all the cases from the 
original email, and even for tests I don't think it is the right 
solution. You want your tests built and run alongside you main code, not 
left to be run when you think to do it separately. For me, integrated 
unit tests is one of the biggest plusses for Maven.

Depenedencies have a "type" attribute in the POM, but I don't think that 
it is used at the moment... ideally plugins could set up a separate 
classpath when, for example, type == 'test' || type == null. Builds 
could use type == 'compile' || type == null.

I'm not sure - what else is type used for at the moment? I noticed it 
renaming JARs sometimes, so I took it out...

- Brett

[EMAIL PROTECTED] wrote:
Charles,


Hi, in Maven, we have only one way of specifying
dependency. In some cases, a project may have
different dependencies at runtime and at compile time.
I can think of two examples:


Naive thinking: manage the test sources in a separate project! This project
depends on the production code and on additional required dependencies. Your
production code could depend on the API's of another package, while your
test project adds to that a specific implementation of these API's to run
the tests.
I didn't try this myself, so if you give this a try, pleas post your
results.
Ringo

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Web Developer
f2 network ~ everything essential
02 8596 4437
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]