On Mon, May 11, 2009 at 9:48 AM, Todd Thiessen thies...@nortel.com wrote:
Are there many cases where you want something for compilation
that isn't needed at runtime? I don't see them as being separate.
Really? I am surprised. Yes there is a relation between compile and
runtime. However,
At test runtime I presume? You use the test scope. Is it
hurting anything if it's there on the test compile classpath?
Its an example of how the scope definition is overloaded. Whether or not
it hurts anything is moot.
-
To
Are there many cases where you want something for compilation
that isn't needed at runtime? I don't see them as being separate.
Really? I am surprised. Yes there is a relation between compile and
runtime. However, there is a different relation between compile and
test. Scope has multiple
2009/5/11 Todd Thiessen thies...@nortel.com
Are there many cases where you want something for compilation
that isn't needed at runtime? I don't see them as being separate.
Really? I am surprised. Yes there is a relation between compile and
runtime. However, there is a different relation
I think the answer here is that nobody had a good example at the
time!
And even when you do, you can use exclusions which you interesting
mention in your next response ;-). So if you want a particular compile
transitive dependency to be included only as test, exclude it and add it
to your local
2009/5/11 Todd Thiessen thies...@nortel.com
I think the answer here is that nobody had a good example at the
time!
And even when you do, you can use exclusions which you interesting
mention in your next response ;-). So if you want a particular compile
transitive dependency to be included
2009/5/11 Brian Fox bri...@infinity.nu:
At face value the logic seems to make sense, but I haven't thought through
all the ramifications. I thought Mark Hobson mentioned some cases where the
opposite was desired. At this point your best bet is to prepare a proposal
on
Just created http://jira.codehaus.org/browse/MNG-4156
Regards,
Stevo.
On Mon, May 11, 2009 at 6:40 PM, Mark Hobson markhob...@gmail.com wrote:
2009/5/11 Brian Fox bri...@infinity.nu:
At face value the logic seems to make sense, but I haven't thought
through
all the ramifications. I
Is there any reason why would local win in this particular case?
Regards,
Stevo.
On Sun, May 10, 2009 at 5:26 AM, Brian Fox bri...@infinity.nu wrote:
On Fri, May 8, 2009 at 11:17 AM, Todd Thiessen thies...@nortel.com
wrote:
Override the dependency defined in the POM, as Steve outline in
By local I mean the pom currently being built. Stuff defined here always
overrides dependencies and transitive dependencies.
On Sun, May 10, 2009 at 5:34 AM, Stevo Slavić ssla...@gmail.com wrote:
Is there any reason why would local win in this particular case?
Regards,
Stevo.
On Sun, May
Just because that's the way things are doesn't mean that's how they should
be., said a character in the movie Australia.
In this particular scenario, local test scoped dependency vs compile scope
transitive dependency, it's my opinion that current strategy is wrong. Local
test scoped dependencies
2009/5/10 Stevo Slavić ssla...@gmail.com
Just because that's the way things are doesn't mean that's how they should
be., said a character in the movie Australia.
I dig that.
In this particular scenario, local test scoped dependency vs compile scope
transitive dependency, it's my opinion
On Fri, May 8, 2009 at 11:17 AM, Todd Thiessen thies...@nortel.com wrote:
Override the dependency defined in the POM, as Steve outline in his
earlier response. Let me quote his explanation for ease of reference:
E.g. if project P has test scoped dependency to a LIB1, and compile
scoped
] On Behalf Of Jörg Schaible
Sent: Friday, May 08, 2009 9:11 AM
To: users@maven.apache.org
Subject: Re: Transitive and inherited dependencies -
potential bug, or my misunderstanding of the mechanism
Hi Stevo,
Stevo Slavić wrote at Freitag, 8. Mai 2009 14:15:
Issue is elsewhere. Initial
2009/5/8 Todd Thiessen thies...@nortel.com
Your argument Jorg I think applies to provided and runtime scope, but not
to test.
The root smell here lies in the definition of scope. Test scope means
needed to compile test code. Compile scope means needed to compile
production and test code.
-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Friday, May 08, 2009 11:00 AM
To: Maven Users List
Subject: Re: Re: Transitive and inherited dependencies -
potential bug, or my misunderstanding of the mechanism
2009/5/8 Todd Thiessen thies...@nortel.com
Your
16 matches
Mail list logo
