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 66.249.82.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=p8N/jyl+szHKRRPrOyJHLqB1OzjfRzL7CD8urDcx7TwBVOyeuMuZsO+DYA5k3jzr0Bfn0UBY+cf/a2EWWRWSF09sUPnWrP4a3TeOlDVIGc3vGwOxx5qzLt3Ao6eHSRbfqFx7E1GIW72RzOjxQQkGP5iSIzZGU0lvZREL1bmGTMM=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <6D5B863D-3408-4634-8802-374EA1E3CB4F@iq80.com>
References: <A511B22C-FD80-4F0D-B3B8-2FAC87ED86B0@iq80.com>
 <DC5400AC-4987-4E2A-931B-E1F6A751D11F@yahoo.com>
 <6D5B863D-3408-4634-8802-374EA1E3CB4F@iq80.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <37B47658-E7ED-4BEF-BCCD-AF7A9C302D23@planet57.com>
Content-Transfer-Encoding: 7bit
From: Jason Dillon <jason@planet57.com>
Subject: Re: Assembly is caching old junk
Date: Wed, 25 Oct 2006 13:49:56 -0700
To: dev@geronimo.apache.org
Sender: Jason Dillon <jason.dillon@gmail.com>

Since people is still down I can't do much on gbuild, as there are  
too may deps missing, and it would take too long to build the deps or  
upload from my network...

I looked into this problem... may have a fix, though I'm not 100%  
sure this is all that needs to be done.  Looks like when we install  
configs into the assembly's target store, we skip modules that exist  
already.  I'm going to add a flag (default to true) which will  
trigger existing modules to be uninstalled first instead of just  
skipping them.

--jason


On Oct 19, 2006, at 4:34 PM, Dain Sundstrom wrote:

> I don't understand how any of this stuff works.  All I know is when  
> I run mvn install I don't get my source changes.  It would be nice  
> to have a single command that does something reasonable.
>
> -dain
>
> On Oct 19, 2006, at 4:17 PM, David Jencks wrote:
>
>> It might help anyone trying to fix this if you can determine what  
>> is out of date in the assembly.  For instance,
>>
>> -- assembly might pick up timestamped jars instead of locally  
>> build -SNAPSHOT jars
>> -- assembly might include old copies of jars
>>
>> As workarounds for the first you can build offline after removing  
>> all g. timestamped jars from your m2 repo
>> for the second perhaps running mvn -o clean install in assembly  
>> would help.
>>
>> Pesonally I try to only rebuild stuff that I've changed or depends  
>> on stuff I've changed
>>
>>
>> thanks
>> david jencks
>>
>> On Oct 19, 2006, at 3:40 PM, Dain Sundstrom wrote:
>>
>>> The tck is moving very slow because when I make a simple change  
>>> to a jar the final assembly is getting the old code.  For  
>>> example, I do the following:
>>>
>>> * changing some code (In my case naming)
>>> * run "mvn install" from the geronimo/server/trunk
>>>
>>> At this point if I unpack an assembly and debug, it I get the old  
>>> code. The only way I have found around this is to run a clean  
>>> build (and a clean build again in the tck), which means the turn  
>>> around time to test a single fix to a tck bug is about 30  
>>> minutes.  Can someone please fix this?
>>>
>>> -dain
>