[
http://jira.codehaus.org/browse/MECLIPSE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184816#action_184816
]
Jörg Hohwiller commented on MECLIPSE-185:
-----------------------------------------
For non @agregator Mojos we should learn that having two different checked
exceptions to throw that in the end do mainly the same thing is not sufficient.
There should also be an exception to tell maven that the module failed but the
build should be continued.
I wonder how plugins like the maven-site-plugin make the "Reactor Summary" so
the status per module is corrent?
> 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
> (.classpath)
> 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
