]
Vineet Reynolds updated FORGE-1133:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
This displays warnings in the Shell for collection and resolution errors in the full
project build. It also displays warnings for problems found in the Maven project model.
Error and exception handling for Maven dependency resolution does not
warn of unresolved dependencies
-----------------------------------------------------------------------------------------------------
Key: FORGE-1133
URL:
https://issues.jboss.org/browse/FORGE-1133
Project: Forge
Issue Type: Bug
Components: Build Tools - Maven
Affects Versions: 1.4.0.Final
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Maven dependency resolution errors are not caught and handled appropriately, especially
during plugin installation. The following behavior is observed when installing the Forge
Arquillian plugin in an environment with an invalid Maven central location, like the one
described
[
here|http://books.sonatype.com/nexus-book/reference/maven-sect-single-gro...], but
without the mirror:
{noformat}
[no project] vineet $ forge install-plugin arquillian
Connecting to remote repository
[
https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
***INFO*** Preparing to install plugin: arquillian
***INFO*** Checking out plugin source files to [/tmp/forgetemp161339604102750966] via
'git'
***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
? The project does not appear to be a Forge Plugin Project, install anyway? [y/N]
{noformat}
It would be better to display warnings or errors and possibly terminate any operations
should this occur.
--
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: