[ 
https://jira.codehaus.org/browse/MDEP-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279500#comment-279500
 ] 

kapila commented on MDEP-326:
-----------------------------

path in central is correct & in specific pom - its mentioned correctly. 
              <dependency>
                        <groupId>org.hibernate.ehcache</groupId>
                        <artifactId>ehcache</artifactId>
                        <version>3.3.1.GA</version>
                </dependency>

whereas its calling for path- org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA 
what i feel is some1 (internal) has wrongly mentioned the path in one of the 
dependent jar's. I need to dig which jar is causing this issue. but unable to 
find the dependency jars' 

pls advice to find that?

> mvn dependency tree not working
> -------------------------------
>
>                 Key: MDEP-326
>                 URL: https://jira.codehaus.org/browse/MDEP-326
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: analyze
>    Affects Versions: 2.3
>         Environment: maven version i am using is 
> /usr/local/apache-maven-3.0/bin/mvn 
>            Reporter: kapila
>            Assignee: Brian Fox
>            Priority: Blocker
>
> While building a sub-project where I am trying to find the jar dependency 
> showing up in compliation which i am not able to locate in code/pom.
>  
> Tried command ;- mvn dependency:tree 
> this doesnt show up the dependency tree 
> this jar doesnt exist on nexus even, so i wanna see where is this defined in 
> pom or dependency jar is calling it. 
> error is 
> Downloaded: 
> http://IP:8081/nexus/content/groups/public-snapshots/abc/abc-web-utils/1.1-SNAPSHOT/maven-metadata.xml
>  (351 B at 6.0 KB/sec) 
> Downloading: 
> http://IP:8081/nexus/content/groups/public/org/hibernate/ehcache/hibernate-core/3.3.1.GA/hibernate-core-3.3.1.GA.pom
>  
> [WARNING] The POM for org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA is 
> missing, no dependency information available 
> [INFO] 
> ------------------------------------------------------------------------ 
> [INFO] BUILD FAILURE 
> [INFO] 
> ------------------------------------------------------------------------ 
> [INFO] Total time: 6.065s 
> [INFO] Finished at: Tue Sep 20 16:29:32 IST 2011 
> [INFO] Final Memory: 8M/1009M 
> [INFO] 
> ------------------------------------------------------------------------ 
> [ERROR] Failed to execute goal on project com.abc.data.web: Could not resolve 
> dependencies for project com.abc:com.abc.data.web:war:3.0.0.M1: Could not 
> find artifact org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA in abc 
> (http://IP:8081/nexus/content/groups/public) -> [Help 1] 
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch. 
> [ERROR] Re-run Maven using the -X switch to enable full debug logging. 
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles: 
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>  
> /home/kapilacvs/data-3.0/data-web/data-web 
> have made entry in pom also - 
>                         <plugin> 
>                                 <groupId>org.apache.maven.plugins</groupId> 
>                                 
> <artifactId>maven-dependency-plugin</artifactId> 
>                                 <version>2.3</version> 
>                         </plugin> 
> i have tried to run same command- mvn dependency:analyze-only on its parent 
> pom its runs fine for other sub-projects. but give issue in this specific 
> project. Doesn't give any dependency graph at all build gives build failure. 
> was trying to understand what harm can these make expect cleaner code- 
> [WARNING] Used undeclared dependencies found: 
> [WARNING] Unused declared dependencies found: 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to