[
http://jira.codehaus.org/browse/MNG-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-3186.
---------------------------
Assignee: John Casey
Resolution: Fixed
We've got a reporting system in place now, covered by implementations of:
org.apache.maven.errors.CoreErrorReporter
org.apache.maven.project.error.ProjectErrorReporter
These provide a host of very specific methods taking relevant context
information from aspect bindings in the build, and rendering one concise,
user-oriented message per method. They are meant to be deadly simple, without a
lot of decision logic...just to help make the reporting api explicit for anyone
who wants to implement it.
BTW, The MavenExecutionRequest and Configuration (in the embedder) both have
methods for setting a custom reporter, to allow IDE integrators better access
to the context information. In CLI mode, all error reports are flushed out at
the end of the build, via the CLIReportingUtils utility class.
> First iteration of concise, user-centric error reporting
> --------------------------------------------------------
>
> Key: MNG-3186
> URL: http://jira.codehaus.org/browse/MNG-3186
> Project: Maven 2
> Issue Type: New Feature
> Components: Embedding
> Reporter: Jason van Zyl
> Assignee: John Casey
> Fix For: 2.1-alpha-1
>
>
--
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
