On 8/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The difference between the runtime and test scopes is also not very
clear to me.
Nick Veys [EMAIL PROTECTED] wrote on 17.08.2006 06:16:40:
This was already answered, but the test dependencies aren't needed for
normal runtime, so
No, but maven is also used to create war, ear and other distribution
packages. These packages need those actual runtime dependencies inside
them.
So for testing I need junit, but not at runtime - test scope
For testing I may not have a need for oracle-jdbc (using hsqldb for
unittests), but at
So, this means that war and ear plug-ins reference the runtime classpath
instead of say compile or test. Correct?
Martijn Dashorst [EMAIL PROTECTED] wrote on 30.08.2006
15:37:56:
No, but maven is also used to create war, ear and other distribution
packages. These packages need those actual
Yes, but runtime classpath != runtime scope
runtime classpath == union(compile, runtime scope)
Martijn
On 8/30/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
So, this means that war and ear plug-ins reference the runtime classpath
instead of say compile or test. Correct?
Martijn Dashorst
Thanks!
Martijn Dashorst [EMAIL PROTECTED]
30.08.2006 16:17
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: Re: Re: Dependency scopes
Reviewed by Category
Yes, but runtime classpath
Nick,
I very much appreciate your response. I wish the article of reference
on subject, namely, Introduction to the Dependency Mechanism was
somewhat more precise. Perhaps the maintainers of the document could
have another look at it. Is filing a bug report appropriate?
Nick Veys [EMAIL
On 8/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Nick,
I very much appreciate your response. I wish the article of reference
on subject, namely, Introduction to the Dependency Mechanism was
somewhat more precise. Perhaps the maintainers of the document could
have another look at it. Is
Nick,
I very much appreciate your response. I wish the article of reference
on subject, namely, Introduction to the Dependency Mechanism was
somewhat more precise. Perhaps the maintainers of the document could
have another look at it. Is filing a bug report appropriate?
Good day to you,
Mike, thank you for taking the time to respond. My question had
several parts and your response relates to the difference between
runtime scope and the test scope. I wonder if someone would care to
respond to the remaining parts.
Mike Perham [EMAIL PROTECTED] wrote on 15.08.2006 18:04:17:
On 8/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The said article mentions the notion of runtime classpath. While I
can see what compile and test classpaths mean, I fail to understand
what a runtime classpath is, in particular how it differs from the
test classpath.
Think of Runtime as
Runtime - contains things that you don't need at compile but you do need
for your app to actually run. You might compile against JMS but require
ActiveMQ at runtime (i.e. a JMS engine).
Test - contains test specific classes. Junit, mocks, a lightweight
database like HSQLDB, etc.
[EMAIL
Ok, we have contact :-).
On 4 Dec 2005, at 17:20, Brian E. Fox wrote:
http://maven.apache.org/guides/introduction/introduction-to-dependency-m
echanism.html
Of course, but …
Dependency scope is used to limit the transitivity of a depedency, and
also to affect the classpath used for various
Nice. But can you give me an example of need and use? At first sight,
this goes for the entire java.* API. And if it is provided, why mention
it?
An example is the servlet.jar. You need it to compile, but don't want it
packaged in your war because the servlet container will provide it
13 matches
Mail list logo
