[JBoss JIRA] (FORGE-894) Forge DependencyFacet cannot resolve transitive dependencies in reactor projects without first installing necessary dependencies in the local Repository
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-894?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-894:
-------------------------------------
Description:
As the title states, maven project building requests do not resolve transitive 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.
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}
was:
As the title states, maven project building requests do not resolve transitive 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.
> Forge DependencyFacet cannot resolve transitive 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 resolve transitive 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.
> 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}
--
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
12 years, 11 months
[JBoss JIRA] (FORGE-894) Forge DependencyFacet cannot resolve transitive dependencies in reactor projects without first installing necessary dependencies in the local Repository
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-894:
----------------------------------------
Summary: Forge DependencyFacet cannot resolve transitive 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 resolve transitive 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.
--
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
12 years, 11 months
[JBoss JIRA] (FORGE-710) Forge shell hangs on exit
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-710?page=com.atlassian.jira.plugin.... ]
George Gastaldi reopened FORGE-710:
-----------------------------------
Assignee: James Perkins
Since I can't reproduce, I am reopening the issue and assigning it to you, is that OK? You can assign it to me once the cause is found.
> Forge shell hangs on exit
> -------------------------
>
> Key: FORGE-710
> URL: https://issues.jboss.org/browse/FORGE-710
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 1.1.2.Final
> Environment: Fedora 17 Linux 3.6.7-4.fc17.x86_64 #1 SMP Tue Nov 20 19:40:01 UTC 2012 x86_64 x86_64 GNU/Linux
> java version "1.6.0_37"
> Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)
> Reporter: James Perkins
> Assignee: James Perkins
> Attachments: jstacktrace, kill-3
>
>
> When attempting to exit Forge by typing exit and pressing enter a hang occurs. Using CTRL+D does seem to work.
--
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
12 years, 11 months
[JBoss JIRA] (FORGE-710) Forge shell hangs on exit
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/FORGE-710?page=com.atlassian.jira.plugin.... ]
James Perkins commented on FORGE-710:
-------------------------------------
Sorry for the delay. I see it occasionally, but it's not all the time. If it comes up again I'll debug it and really drill down and figure it out.
> Forge shell hangs on exit
> -------------------------
>
> Key: FORGE-710
> URL: https://issues.jboss.org/browse/FORGE-710
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 1.1.2.Final
> Environment: Fedora 17 Linux 3.6.7-4.fc17.x86_64 #1 SMP Tue Nov 20 19:40:01 UTC 2012 x86_64 x86_64 GNU/Linux
> java version "1.6.0_37"
> Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)
> Reporter: James Perkins
> Attachments: jstacktrace, kill-3
>
>
> When attempting to exit Forge by typing exit and pressing enter a hang occurs. Using CTRL+D does seem to work.
--
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
12 years, 11 months
[JBoss JIRA] (FORGE-794) Refactor PropertyCompleter from Java EE Impl to Forge Core
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-794?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-794:
----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 1.3.0.Final
Resolution: Done
Merged
> Refactor PropertyCompleter from Java EE Impl to Forge Core
> ----------------------------------------------------------
>
> Key: FORGE-794
> URL: https://issues.jboss.org/browse/FORGE-794
> Project: Forge
> Issue Type: Enhancement
> Affects Versions: 1.2.1.Final
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
> Priority: Minor
> Fix For: 1.3.0.Final
>
>
> The {{org.jboss.forge.spec.javaee.validation.completer.PropertyCompleter}} class is useful as a generic property completer.
> It has nothing specific to the Java EE APIs, and hence could be moved to Forge Core from the Java EE impl project, where it could be exposed to all plugins.
--
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
12 years, 11 months