[
http://jira.codehaus.org/browse/MECLIPSE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184815#action_184815
]
Jörg Hohwiller commented on MECLIPSE-185:
-----------------------------------------
Just to give my 2 cents:
What if you just set a flag in such case and at the end of the build throw an
exception if the error-flag was set.
I am not sure if your Mojo is an @agregator or not...
My problem is NOT that the build continues but the SUCCESS message at the end.
The log is quite large in my project and I often miss problems that occurred
but scrolled
away faster than my eyes could cover. When I see SUCCESS I expect there was no
problem.
> 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
