« Return to Thread: What can possibly go wrong with Maven
Re: What can possibly go wrong with Maven
by Mauro Talevi
::
Rate this Message:
- Classloader problems: often difficult to debug them when artifacts are coming from different
"transitive sources". Would be great to have a better way to display a trace of the dependency
tree, without being swamped by all the non-dependency "noise". Maybe a new debug flag (different
from -X and -e) would help here.
Jason van Zyl wrote:
> Hi,
>
> I'm trying to collect everything that can go wrong inside Maven so that
> it can be clearly pointed out to a user. We currently have a mechanism
> that analyzes stack traces, isn't localized, and is not very friendly
> for embedding as everything is couched in the form of console output.
> Here's the list that I came up with so far and I want to make to make a
> mechanism that says exactly what's wrong.
>
> Anyone have anything else? I'm not trying to consider everything that
> happens in plugins. I've identified almost all the places where those
> errors occur and I would like them to surface at the top in a form that
> is useful to embedding. As a by product it's easy to produce console
> output for the CLI. I don't care if the try/catch is a mile long it's
> going to tell users exactly what happened when something goes wrong.
> I've pushed all console logging out of DefaultMaven and into the CLI.
> Moved the monitor into the core, but we still have console-centric
> logging in a bunch of the major components which I should be able to
> purge by the release of 2.1-alpha-1.
>
> Here's the list:
>
> - bad command line parameter
> - malformed settings
> - malformed POM
> - local repository not writable
> - remote repositories not available
> - artifact metadata missing
> - extension metadata missing
> - extension artifact missing
> - artifact metadata retrieval problem
> - version range violation
> - circular dependency
> - artifact missing
> - artifact retrieval exception
> - plugin metadata missing
> - plugin metadata retrieval problem
> - plugin artifact missing
> - plugin artifact retrieval problem
> - plugin dependency metadata missing
> - plugin dependency metadata retrieval problem
> - plugin configuration problem
> - plugin execution failure due to something that is know to possibly go
> wrong (like compilation failure)
> - plugin execution error due to something that is not expected to go
> wrong (the compiler executable missing)
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
"transitive sources". Would be great to have a better way to display a trace of the dependency
tree, without being swamped by all the non-dependency "noise". Maybe a new debug flag (different
from -X and -e) would help here.
Jason van Zyl wrote:
> Hi,
>
> I'm trying to collect everything that can go wrong inside Maven so that
> it can be clearly pointed out to a user. We currently have a mechanism
> that analyzes stack traces, isn't localized, and is not very friendly
> for embedding as everything is couched in the form of console output.
> Here's the list that I came up with so far and I want to make to make a
> mechanism that says exactly what's wrong.
>
> Anyone have anything else? I'm not trying to consider everything that
> happens in plugins. I've identified almost all the places where those
> errors occur and I would like them to surface at the top in a form that
> is useful to embedding. As a by product it's easy to produce console
> output for the CLI. I don't care if the try/catch is a mile long it's
> going to tell users exactly what happened when something goes wrong.
> I've pushed all console logging out of DefaultMaven and into the CLI.
> Moved the monitor into the core, but we still have console-centric
> logging in a bunch of the major components which I should be able to
> purge by the release of 2.1-alpha-1.
>
> Here's the list:
>
> - bad command line parameter
> - malformed settings
> - malformed POM
> - local repository not writable
> - remote repositories not available
> - artifact metadata missing
> - extension metadata missing
> - extension artifact missing
> - artifact metadata retrieval problem
> - version range violation
> - circular dependency
> - artifact missing
> - artifact retrieval exception
> - plugin metadata missing
> - plugin metadata retrieval problem
> - plugin artifact missing
> - plugin artifact retrieval problem
> - plugin dependency metadata missing
> - plugin dependency metadata retrieval problem
> - plugin configuration problem
> - plugin execution failure due to something that is know to possibly go
> wrong (like compilation failure)
> - plugin execution error due to something that is not expected to go
> wrong (the compiler executable missing)
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
« Return to Thread: What can possibly go wrong with Maven
| Free embeddable forum powered by Nabble | Forum Help |
