Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of jason.dillon@gmail.com
 designates 64.233.162.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=khdEeNaR9toWOjr8FT/083e2CZ8bspUDdjqOz/4Luty4bZ+EUcq+CqxRgrKBiBAVgfBrsnB/9N1tHVr0ttchdxvjmngx9pro1+uIGe8OsRfy/wxLNwnG3PKrZr0xBgSeovsdjA/b0vEtnviMFa8j4zgKmTAZQWUsZIvG2OB5tPI=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <457DC2FC.5060507@earthlink.net>
References: <189226.26437.qm@web31714.mail.mud.yahoo.com>
 <3CB807E2-5319-4121-96EA-8CD2B6A8EB1A@planet57.com>
 <457D29B5.80204@earthlink.net>
 <3A4EECEF-69ED-4294-BCD8-423F265DEC45@planet57.com>
 <457DC2FC.5060507@earthlink.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DC24B415-2D24-4FAB-904C-6C831250CD36@planet57.com>
Content-Transfer-Encoding: 7bit
From: Jason Dillon <jason@planet57.com>
Subject: Re: Strange build problem
Date: Mon, 11 Dec 2006 13:19:51 -0800
To: dev@geronimo.apache.org
Sender: Jason Dillon <jason.dillon@gmail.com>

On Dec 11, 2006, at 12:43 PM, Joe Bohn wrote:

> I wish I could say I "removed it" without any additional  
> qualification.  :-P However, what I actually said was that I  
> removed it *from the root pom*.   I still have references to the  
> java.net as a legacy repo in modules/geronimo-web-2.5-builder,  
> configs/tomcat6 and configs/jetty6 to pick up jstl 1.2.
>
> AFAIK this shouldn't cause a problem for modules/geronimo-cxf- 
> builder or generally anything other than children of the poms I  
> changed ... right?
>
> Joe

Ya, that is what I had thought.  I believe this is why the strange  
build problem is occurring, as Anita says it happens when building  
from modules/ and not when building from geronimo-cxf-builder.  When  
building from modules/ mvn will scan all modules and generate pom  
state for them, which includes setting up repos.

10 to 1, if you have the required artifacts in your repo already,  
then comment out those legacy repos (leaving the dependencies along),  
then this problem will go away.

Really need to find a better solution to this immediate need for jstl  
and keep in mind in the future to now include legacy repos in the build.

--jason