[forge-issues] [JBoss JIRA] (FORGE-894) Forge DependencyFacet cannot resolve dependencies in reactor projects without first installing necessary dependencies in the local Repository

[Alexander Heusingfeld (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773618#comment-12773618 ] 

Alexander Heusingfeld edited comment on FORGE-894 at 5/12/13 7:05 AM:
----------------------------------------------------------------------

Seems to me that none of the transitive dependencies are resolved in {{org.jboss.forge.maven.projects.facets.MavenDependencyFacet#getEffectiveDependencies()}}. If this is expected, we perhaps should make use of {{org.jboss.forge.maven.dependencies.MavenDependencyResolver}} here?!
                
      was (Author: aheusingfeld):
    Seems to me that none of the transitive dependencies are resolved in {org.jboss.forge.maven.projects.facets.MavenDependencyFacet#getEffectiveDependencies()}. If this is expected, we perhaps should make use of {org.jboss.forge.maven.dependencies.MavenDependencyResolver} here?!
                  
> Forge DependencyFacet cannot resolve dependencies in reactor projects without first installing necessary dependencies in the local Repository
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FORGE-894
>                 URL: https://issues.jboss.org/browse/FORGE-894
>             Project: Forge
>          Issue Type: Bug
>          Components: Maven Integration
>    Affects Versions: 2.0.0.Alpha3
>            Reporter: Lincoln Baxter III
>            Assignee: Lincoln Baxter III
>             Fix For: 2.0.0.Alpha4
>
>
> As the title states, maven project building requests do not resolv reactor project dependencies.
> {code}
> parent/
> - addon --> spi
> - api
> - impl
> - spi
> - tests --> addon
> {code}
> the tests/ module dependency resolution result does not contain a transitive dependency to the spi/ module, however, when building from maven cli, it clearly should and does have this dependency - so this is a pure tooling issue due to the fact that the addon/ sub-module actually cannot be resolved.
> This can be reproduced in the branch: https://github.com/forge/core/tree/FORGE-894 
> Running the test:
> {code}
> Failed tests:   testCreateAddonProject(org.jboss.forge.addons.AddonProjectConfiguratorTest): SPI module is not present in the TESTS module
> {code}
> Relevant code (where the resolution is performed) is here: https://github.com/forge/core/blob/FORGE-894/maven/impl-projects/src/main/java/org/jboss/forge/maven/projects/MavenFacetImpl.java#L271

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira