On 8 Sep 07, at 11:38 AM 8 Sep 07, Jorg Heymans wrote:
Jason van Zyl wrote:
Anyone have anything else? I'm not trying to consider everything that
Any chance that mvn could indicate the exact pom.xml locations of
duplicated projects ?
No reason why it couldn't, we know the source of eve
Jason van Zyl wrote:
Anyone have anything else? I'm not trying to consider everything that
Any chance that mvn could indicate the exact pom.xml locations of
duplicated projects ?
So instead of this:
[INFO] Project 'te
On 05/09/2007, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> You mean something like this?
>
> [EMAIL PROTECTED] ~/src/Codehaus/pico/java-2.x/nano/container-bsh $ mvn
> info:deps-runtime
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'info'.
> WAGON_VERSION: 1.
Mauro Talevi wrote:
> - 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
> ne
Component not found
Missing goal in plugin (probably the wrong version)
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, September 03, 2007 7:58 PM
To: Maven Developers List
Subject: What can possibly go wrong with Maven
Hi,
I'm trying to co
- 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 -
On 04/09/2007, at 7:40 PM, Jörg Schaible wrote:
Brett Porter wrote on Tuesday, September 04, 2007 10:31 AM:
On 04/09/2007, at 6:24 PM, Jörg Schaible wrote:
- calling a goal that does not need a POM in the current dir in a
multi-project root Examples:
mvn install:install-file
mvn archetype
Brett Porter wrote on Tuesday, September 04, 2007 10:31 AM:
> On 04/09/2007, at 6:24 PM, Jörg Schaible wrote:
>
>>
>> - calling a goal that does not need a POM in the current dir in a
>> multi-project root Examples:
>> mvn install:install-file
>> mvn archetype:create
>> Maven walks down the co
On 04/09/2007, at 6:24 PM, Jörg Schaible wrote:
- calling a goal that does not need a POM in the current dir in a
multi-project root
Examples:
mvn install:install-file
mvn archetype:create
Maven walks down the complete project hierarchy ...
But Maven can't tell the difference between "d
On 4 Sep 07, at 1:15 AM 4 Sep 07, Brett Porter wrote:
- invalid lifecycle phase (maybe same as bad CLI param, though you
were talking about embedder too)
Yup, this is caught with some validation code I added the other day
but it needs to filter up nicely. It doesn't currently.
- specif
- calling a goal that does not need a POM in the current dir in a multi-project
root
Examples:
mvn install:install-file
mvn archetype:create
Maven walks down the complete project hierarchy ...
Brett Porter wrote on Tuesday, September 04, 2007 10:15 AM:
> - invalid lifecycle phase (maybe same
- invalid lifecycle phase (maybe same as bad CLI param, though you
were talking about embedder too)
- specified is not found
- POM doesn't exist for a goal that requires one
- goal not found in a plugin (probably could list the ones that are)
- parent POM missing (in both the repository + relat
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. He
13 matches
Mail list logo
