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
to provide it. It is only available on the
compilation
classpath, and is not transitive.
However, in a small project I've created to test dependency scopes, it
seems that a dependency declared with the provided scope is
available when compiling the source, compiling the test cases as well
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
/Dependency-scopes-tf2109159.html#a5860766
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
PROTECTED] wrote on 08/15/2006 08:32:26 AM:
Hello,
I would like to ask a question regarding dependency scopes in
Maven2. After reading the article Introduction to the Dependency
Mechanism [1], I've got several questions that may have been answered
previously. I apologize in advance
classpath, and is not transitive.
However, in a small project I've created to test dependency scopes, it
seems that a dependency declared with the provided scope is
available when compiling the source, compiling the test cases as well
as when running them (the test cases). Thus, it looks like
Hello,
I would like to ask a question regarding dependency scopes in
Maven2. After reading the article Introduction to the Dependency
Mechanism [1], I've got several questions that may have been answered
previously. I apologize in advance if that is the case.
The said article mentions the notion
PROTECTED] wrote on 08/15/2006 08:32:26 AM:
Hello,
I would like to ask a question regarding dependency scopes in
Maven2. After reading the article Introduction to the Dependency
Mechanism [1], I've got several questions that may have been answered
previously. I apologize in advance
I *really* don't fully grasp dependency scopes. Could somebody in the know please have a look at http://docs.codehaus.org/display/MAVENUSER/Dependency+Scopes> and correct some points?
Or at least, give a 1-sentence use case (example) for each of the scopes?
Until now, I found the follow
tation?
From: ir. ing. Jan Dockx [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 04, 2005 4:57 AM
To: Maven Users List
Subject: dependency scopes
I *really* don't fully grasp dependency scopes. Could somebody in the
know please have a look at
http://docs.codeha
Dockx [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 04, 2005 4:57 AM
To: Maven Users List
Subject: dependency scopes
I *really* don't fully grasp dependency scopes. Could somebody
in the
know please have a look at
http
I don't understand the dependency scope mechanism. Therefor, I created a page in the Wiki to get this sorted out.
http://docs.codehaus.org/display/MAVENUSER/Dependency+Scopes>
In the first version of this page, I am trying to make sense of different sources about the topic. This me
Hi Tim,
I have the same needs and wrote a plugin that merely copy all dependencies into
a directory of your choice - it's largely inspired from war plugin, of course
:) Let me know if you are interested.
Yann
--- Brett Porter [EMAIL PROTECTED] a écrit :
Scope is a default for the packaging
On 25/09/05, Brett Porter [EMAIL PROTECTED] wrote:
There is an open JIRA for the war plugin to allow this (specifically
for applets and jnlp). It has not yet been implemented.
For those interested this is http://jira.codehaus.org/browse/MNG-896.
Mark
On 25/09/05, Brett Porter [EMAIL PROTECTED] wrote:
You can work around it by writing your own small plugin (or use the
antrun plugin), to copy the jar into place in an earlier phase.
BTW, I tried this with antrun using the maven ant tasks for transitive
deps, but encountered MNG-1017.
Hi,
I've set up a simple web-app (war) project with Maven 2. Now I need to
place some artifacts from my repository (a few jar's accessed by JNLP)
in the root of the war. Just declaring them as dependencies puts them in
the WEB-INF/lib directory.
Is it possible to define a new kind of
Scope is a default for the packaging rule, not a packaging rule in itself.
There is an open JIRA for the war plugin to allow this (specifically
for applets and jnlp). It has not yet been implemented.
You can work around it by writing your own small plugin (or use the
antrun plugin), to copy the
21 matches
Mail list logo