[ 
http://jira.codehaus.org/browse/MNG-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147117#action_147117
 ] 

David J. M. Karlsen commented on MNG-3553:
------------------------------------------

I have a slightly different problem.

Our super pom (artifact A) declares:

<dependencies>
    <dependency>
      <groupId>my.groupid</groupId>
      <artifactId>websphere-testenvironment</artifactId>
      <version>1.3-SNAPSHOT</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>

that is - in the dependencies section - not dep.management.



I then have an artifact B which have A as parent. The dependencies are not 
resolve, although to my surprise, if I run mvn help:effective-pom on artifact 
B, the dep is actually listed:

  <dependencies>
    <dependency>
      <groupId>my.groupid</groupId>
      <artifactId>websphere-testenvironment</artifactId>
      <version>1.3-SNAPSHOT</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>

All the dependencies in my.groupid:websphere-testenvironment:1.3-SNAPSHOT are 
declared as provided.

So there seems to be some inheritance problem.

> 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
>            Reporter: Thomas Diesler
>             Fix For: 2.0.11
>
>
> 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
> [EMAIL PROTECTED] 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

        

Reply via email to