[
https://issues.jboss.org/browse/FORGE-894?page=com.atlassian.jira.plugin....
]
Lincoln Baxter III commented on FORGE-894:
------------------------------------------
I think we need to do some kind of separate build/manual resolution in order to get this
to work... I don't think even maven a top-down reactor build supports this without an
artifact installed in the repository, based on further testing.
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...
--
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