You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Lacoste, Dana" <da...@hp.com> on 2007/04/21 00:16:23 UTC
Selected for....
OK, this is a reach, and I'm trying to debug something
very very complicated that's kinda messy, but I thought
I'd ask, in case someone can give me a definitive answer.
Is there a simple logic flow diagram that shows what
maven 2.0.6 will do for a dependency?
I'm seeing a "Selected for null" on something when I've
set the scope manually. I can't seem to make it classpath
it. The part that confuses me is that it DOES work if
I call the pom directly: it only fails if I call the pom
from the parent instead of the child.
(i.e. A contains B and C. C depends on B. When running
mvn in C everything's fine, but when running in A it fails)
Now, B is definitely not a normal thing, but it's published
into the repo: I can't see why I can't tell maven to go get
it from the repo when building C (REGARDLESS of whether or
not it knows about B when building C from A. :)
I'm sure that there's some kind of naming convention or
other thing that I'm doing wrong, but I can't find any
maven docs on what it's SUPPOSED to do, so I can't figure
out how to diagnose the problem :)
Thanks for any suggestions!
--
Dana Lacoste
Software Design Engineer
HP Software
http://www.hp.com/go/software
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Selected for....
Posted by Piotr Tabor <pt...@newitech.com>.
Hi,
Look at: http://jira.codehaus.org/browse/MNG-2921
Piotr Tabor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Selected for....
Posted by Wendy Smoak <ws...@gmail.com>.
On 4/20/07, Lacoste, Dana <da...@hp.com> wrote:
> Oh, I forgot to add:
>
> This works FINE in 2.0.5. Whatever broke was a change in 2.0.6 :(
There is a dependency analyzer intended to help fix problems prior to
upgrading to 2.0.6:
http://maven.apache.org/plugins/maven-dependency-plugin/examples/preparing-dependencies.html
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Selected for....
Posted by "Lacoste, Dana" <da...@hp.com>.
Oh, I forgot to add:
This works FINE in 2.0.5. Whatever broke was a change in 2.0.6 :(
Thanks again!
--
Dana Lacoste
Software Design Engineer
HP Software
http://www.hp.com/go/software
-----Original Message-----
From: Lacoste, Dana
Sent: Friday, April 20, 2007 3:16 PM
To: Maven Users List
Subject: Selected for....
OK, this is a reach, and I'm trying to debug something very very
complicated that's kinda messy, but I thought I'd ask, in case someone
can give me a definitive answer.
Is there a simple logic flow diagram that shows what maven 2.0.6 will do
for a dependency?
I'm seeing a "Selected for null" on something when I've set the scope
manually. I can't seem to make it classpath it. The part that confuses
me is that it DOES work if I call the pom directly: it only fails if I
call the pom from the parent instead of the child.
(i.e. A contains B and C. C depends on B. When running mvn in C
everything's fine, but when running in A it fails)
Now, B is definitely not a normal thing, but it's published into the
repo: I can't see why I can't tell maven to go get it from the repo when
building C (REGARDLESS of whether or not it knows about B when building
C from A. :)
I'm sure that there's some kind of naming convention or other thing that
I'm doing wrong, but I can't find any maven docs on what it's SUPPOSED
to do, so I can't figure out how to diagnose the problem :)
Thanks for any suggestions!
--
Dana Lacoste
Software Design Engineer
HP Software
http://www.hp.com/go/software
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org