maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <>
Subject [jira] Closed: (MNG-3175) Take another pass over the exceptions that can occur during execution and project handling
Date Mon, 17 Dec 2007 00:25:57 GMT


John Casey closed MNG-3175.

      Assignee: John Casey  (was: Jason van Zyl)
    Resolution: Fixed

I've started with the implementations of Exception that are handled in the outermost layers
of Maven (The embedder and cli), and encoded the specific error conditions that lead to those
exceptions into methods in the CoreErrorReporter and ProjectErrorReporter interfaces, diving
in up to two or three exception-wrapping layers sometimes to get at an error that's more useful
to report on.

Obviously, as new behavior (or behavioral changes) evolve, it may become necessary to modify
the error reporter interfaces. However, the api should probably be relatively stable, unless/until
we get around to refactoring DefaultMavenProjectBuilder, DefaultLifecycleExecutor, or DefaultPluginManager.
At that time, the aspects binding the reporter apis to the main body of code will have to
be adjusted to collect the proper context elements (project instances, files, etc.).

> Take another pass over the exceptions that can occur during execution and project handling
> ------------------------------------------------------------------------------------------
>                 Key: MNG-3175
>                 URL:
>             Project: Maven 2
>          Issue Type: Task
>          Components: Embedding
>    Affects Versions: 2.1-alpha-1
>            Reporter: Jason van Zyl
>            Assignee: John Casey
>             Fix For: 2.1-alpha-1
> The problems that can occur during execution and project handing:
> - POM parsing errors
> - missing metadata
> - error retrieving metadata
> - version range violations
> - circular dependency violations
> - missing artifacts
> - error retrieving artifacts
> I have most of this handled in the ArtifactResolutionResult, but the ProjectBuildingResult
and the MavenExecutionResult need some work to make sure that everything is passed through
correctly. This is of the utmost important for embedding because it means from the UI that
integrators can give users exact details as to problems that occur. Milos has really gone
a long way to work around the fact we don't do this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message