Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4CAA4DDC.6050003@udo.edu>
Date: Mon, 04 Oct 2010 23:57:48 +0200
From: Benjamin Bentmann <benjamin.bentmann@udo.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de;
 rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Maven Users List <users@maven.apache.org>
Subject: Re: Maven 2 & 3 + Hudson + Nexus
References: <AANLkTikYH0iG=zSkQ7E5EUNv91zNnm5iVqSUNRc5ZWc3@mail.gmail.com>
In-Reply-To: <AANLkTikYH0iG=zSkQ7E5EUNv91zNnm5iVqSUNRc5ZWc3@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hilco Wijbenga wrote:

> Any ideas how I can fix this? Any ideas as to what the problem is exactly?

I personally find it helpful to start with a precise description of what 
the issue actually is before trying to solve it. After all, there's a 
reason why the build produces a log and even if you can't spot the 
relevant pieces in there, others might be able to. So sharing the log of 
the failing module would be a good start. And with log, I don't mean the 
single line that says "[ERROR]", I mean the entire log that shows the 
actions taken by Maven that eventually lead to the error and contribute 
to the context required to understand the issue. If the log cannot be 
attached to the mail, using pastebin.com or similar can help. Other 
things that are nice to know is the directory listing of the directory 
in the local repo that contains the POM in question. Last but not least, 
the contents of all maven-metadata-*.xml in that directory can help to 
troubleshoot that issue.


Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org