To summarize this discussion, it is now working when I declared the
dependency below

<dependency org="org.slf4j" name="slf4j-jdk14" rev="1.4.0" />

Note that the org="org.slf4j" instead of org="org.slf4j.slf4j".


Always check if the location is actually exist, DO NOT RELY ON
mvnrepository.com  :-)


On 7/4/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
On 7/4/07, hezjing <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> Following my previous problem of "Unresolved dependencies -
> spring-context", I have installed the non-official ivy.jar (built from
> trunk on 29th June).
>
> Based on
> http://www.mvnrepository.com/artifact/org.slf4j.slf4j/slf4j-jdk14/1.1.0-RC0
> ,
>
> <dependency>
> <groupId>org.slf4j.slf4j</groupId>
> <artifactId>slf4j-jdk14</artifactId>
> <version>1.1.0-RC0</version>
> </dependency>
>
>
> I created below Ivy dependency,
>
> <dependency org="org.slf4j.slf4j" name="slf4j-jdk14" rev="1.1.0-RC0" />
>
>
> When run, I got another unresolved dependencies
>
> ::::::::::::::::::::::::::::::::::::::::::::::
> ::          UNRESOLVED DEPENDENCIES         ::
> ::::::::::::::::::::::::::::::::::::::::::::::
> :: [ org.slf4j.slf4j | slf4j-jdk14 | 1.1.0-RC0 ]: not found
> ::::::::::::::::::::::::::::::::::::::::::::::
>
> :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>
>
> Do you have any idea how to resolve this problem?


Even without verbose or debug, Ivy should tell you  at which location it
tried to locate the module. Check if at least one of these locations
actually exist (with a browser if you use http repository). If it doesn't
Ivy can't do much for you :-)

In this case it seems that it's mvnrepository.com which is the source of
your problem. With:
http://www.mvnrepository.com/search.html?query=slf4j+jdk
you find two modules, the one you tried and another one ([ org.slf4j |
slf4j-jdk14 ]). The one you tried does not actually exist on maven 2
repository, while the other one seems to exist. Usually when only one
revision is available, it's a sign that the module may be the wrong one.

How to turn-on the debug message level to see more details?


Use standard Ant message levels command line options: -debug or -verbose

HTH,

Xavier

--
>
> Hez
>



--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/



--

Hez

Reply via email to