You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/04/30 18:33:45 UTC

[jira] Closed: (MNG-3553) cannot resolve dependency with scope import

     [ http://jira.codehaus.org/browse/MNG-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MNG-3553.
---------------------------

    Resolution: Won't Fix

We cannot fix the case where imported dependencies lose the repository definition they need from the imported POM into the new one. To add the custom repository definition to the importing POM could change the way the rest of that POMs dependencies resolve, especially in cases where snapshots are used. The workaround for this issue is to add the custom repository definition to the importing POM as well as the imported POM, so the dependencies may resolve even after they are imported.

Also, Arnaud's issue near the bottom of the page is separate from the main problem described here, and is captured in MNG-4148.

> cannot resolve dependency with scope import
> -------------------------------------------
>
>                 Key: MNG-3553
>                 URL: http://jira.codehaus.org/browse/MNG-3553
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.9, 2.1.0
>            Reporter: Thomas Diesler
>            Assignee: John Casey
>            Priority: Critical
>             Fix For: 2.0.11, 2.2.0
>
>         Attachments: mng-3553.zip, test-mng3553.zip
>
>
> This pom when added as a dependency of another project does not see repository http://snapshots.jboss.org/maven2
>   <!-- DependencyManagement -->
>   <dependencyManagement>
>     <dependencies>
>       <dependency>
>         <groupId>org.jboss.jbossas</groupId>
>         <artifactId>jboss-as-component-matrix</artifactId>
>         <version>${jboss.version}</version>
>         <type>pom</type>
>         <scope>import</scope>
>       </dependency>
>     </dependencies>
>   </dependencyManagement>
> with effective settings
> [tdiesler@tddell trunk]$ mvn help:effective-settings
> [INFO] Scanning for projects...
> [INFO] Reactor build order: 
> [INFO]   JBoss Web Services - Stack CXF
> [INFO]   JBoss Web Services - Stack CXF Management
> [INFO]   JBoss Web Services - Stack CXF Runtime Server
> [INFO]   JBoss Web Services - Stack CXF Runtime Client
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Web Services - Stack CXF
> [INFO]    task-segment: [help:effective-settings] (aggregator-style)
> [INFO] ------------------------------------------------------------------------
> [INFO] [help:effective-settings]
> [INFO] 
> Effective settings:
> <?xml version="1.0"?><settings>
>   <localRepository>/home/tdiesler/.m2/repository</localRepository>
>   <profiles>
>     <profile>
>       <activation>
>         <property>
>           <name>!jboss.repository.off</name>
>         </property>
>       </activation>
>       <repositories>
>         <repository>
>           <snapshots />
>           <id>snapshots.jboss.org</id>
>           <url>http://snapshots.jboss.org/maven2</url>
>         </repository>
>         <repository>
>           <snapshots>
>             <enabled>false</enabled>
>           </snapshots>
>           <id>repository.jboss.org</id>
>           <url>http://repository.jboss.org/maven2</url>
>         </repository>
>       </repositories>
>       <id>jboss.repository</id>
>     </profile>
>   </profiles>
>   <activeProfiles>
>     <activeProfile>user-profile</activeProfile>
>   </activeProfiles>
>   <pluginGroups>
>     <pluginGroup>org.jboss.maven.plugins</pluginGroup>
>   </pluginGroups>
> </settings>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira