Github user peterlynch closed the pull request at:
https://github.com/apache/maven-indexer/pull/2
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What about component config errors in the plugin handling? I'll put it
back for artifact resolution too. I've done the MojoExecutionException
and the default diagnoser, and I'm checking that the main error message
doesn't include the root's message.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I only have 2 real problems here:
1. MojoExecutionException, which is meant to be a wrapper for some
unknown exception. This could be anything, and we REALLY cannot
guarantee that it's root cause is expressed in the top-level exception's
message, unl
... of course, I only did m2, not wagon.
I'd suggest restoring the root cause for the
ArtifactResolutionException, but make sure it grabs the IOException (I
saw the 503 on the clean checkout), and don't display it if the main
message contains that message.
- Brett
Brett Porter wrote:
>I'd plann
I'd planned to summarise what I did here tomorrow as its late...
I very carefully audited every exception in the codebase and ensured
that the message of each exception always captured any appropriate
message from the cause. There are no more "shoulder shrugs".
The root simply duplicated all of t
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter closed MNG-122:
Resolution: Fixed
> clean up of exception handling, error reporting and logging
> ---
>
>
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter updated MNG-122:
-
Fix Version: (was: 2.0-beta-3)
2.0-beta-4
> clean up of exception handling, error reporting and logg
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter updated MNG-122:
-
Fix Version: (was: 2.0-beta-2)
2.0-beta-3
> clean up of exception handling, error reporting and logg
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter updated MNG-122:
-
Component: maven-core
> clean up of exception handling, error reporting and logging
> ---
>
>
[ http://jira.codehaus.org/browse/MNG-564?page=all ]
Emmanuel Venisse closed MNG-564:
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 2.0-beta-1
Applied. Thanks.
> AbstractMavenReport.execut() exception handl
AbstractMavenReport.execut() exception handling
---
Key: MNG-564
URL: http://jira.codehaus.org/browse/MNG-564
Project: Maven 2
Type: Bug
Components: maven-reports
Versions: 2.0-alpha-3
Environment: gentoo
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter updated MNG-122:
-
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
> clean up of exception handling, error reporting and logg
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-17?page=all ]
Carlos Sanchez closed MPCHECKSTYLE-17:
--
Resolution: Cannot Reproduce
The offending code is no longer in the plugin, seems already fixed
> Exception handling always reports miss
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter updated MNG-122:
-
Fix Version: (was: 2.0-alpha-3)
2.0-beta-1
> clean up of exception handling, error reporting and logg
[ http://jira.codehaus.org/browse/MNG-122?page=all ]
Brett Porter updated MNG-122:
-
Fix Version: (was: 2.0-alpha-2)
2.0-alpha-3
> clean up of exception handling, error reporting and logg
being pushed back
to alpha-3 or later as it is definitely workable now.
> clean up of exception handling, error reporting and logging
> ---
>
> Key: MNG-122
> URL: http://jira.codehaus.org/browse/MNG-12
:
-
Key: MPCHECKSTYLE-17
Summary: Exception handling always reports missing license file
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-checkstyle-plugin
Versions
17 matches
Mail list logo
