[
http://jira.codehaus.org/browse/MECLIPSE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147391#action_147391
]
Barrie Treloar commented on MECLIPSE-185:
-----------------------------------------
This affects the IT tests too.
I've noticed that project-34 (a multi-module project) is failing in the output
log because it is missing some system dependencies. The root pom for
project-34 appears to be copied from master-test. Even though it fails because
of missing dependencies the plugin indicates successful generation. See
MECLIPSE-486
> 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
> Components: Core : Dependencies resolution and build path
> Affects Versions: 2.2
> Reporter: Hans Dockter
> Assignee: Brian Fox
>
> 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
