[
http://jira.codehaus.org/browse/MECLIPSE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100832
]
Brian Fox commented on MECLIPSE-185:
------------------------------------
It appears that this was intentional in the code:
{code:title=AbstractIdeSupportMojo.java|borderStyle=solid}
catch ( ArtifactResolutionException e )
{
getLog().debug( e.getMessage(), e );
getLog().error(
Messages.getString(
"artifactresolution", new Object[] { //$NON-NLS-1$
e.getGroupId(),
e.getArtifactId(),
e.getVersion(),
e.getMessage()
} ) );
// if we are here artifactResolutionResult is null,
create a project without dependencies but don't fail
// (this could be a reactor projects, we don't want to
fail everything)
return new IdeDependency[0];
}
{code}
I'm not sure if this is really needed. Couldn't the user just specify -FAE to
continue through the reactor?
> mvn eclipse:eclipse report 'Build Successful' even when generation fails
> ------------------------------------------------------------------------
>
> Key: MECLIPSE-185
> URL: http://jira.codehaus.org/browse/MECLIPSE-185
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Hans Dockter
> Assignee: Brian Fox
> Fix For: 2.4
>
>
> When I start mvn eclipse:eclipse and for example some dependencies can't be
> downloaded. Then the plugin still reports at the end Build successful,
> although no new .classpath file was generated. Now ypu have to always verify
> the content of the output, to see if it was really successful.
--
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
