Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <448B1D51.3010000@hogstrom.org>
Date: Sat, 10 Jun 2006 15:28:17 -0400
From: Matt Hogstrom <matt@hogstrom.org>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: 1.1 Blocker - Bad deployment jams repo
References: <74e15baa0606092023m2458b085m800ce5151e050069@mail.gmail.com>
	 <448AED2E.6040806@yahoo.com>
	 <74e15baa0606101019m5a403f4ao8250cbc98d169565@mail.gmail.com>
 <74e15baa0606101040v21cb5f8bhe64f8989fe209e03@mail.gmail.com>
In-Reply-To: <74e15baa0606101040v21cb5f8bhe64f8989fe209e03@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Aaron,

Kevan had addressed this problem...perhaps there is another incident of it ?


Aaron Mulder wrote:
> Oh, I see that there was a previous fix for the EAR builder.  I've
> been doing more services lately, so perhaps the problem is just in the
> ServiceConfigBuilder now.
> 
> Thanks,
>    Aaron
> 
> On 6/10/06, Aaron Mulder <ammulder@alumni.princeton.edu> wrote:
>> In my experience this is substantially worse than 1.0.  In 1.0, I
>> could almost always either redeploy or undeploy to get around a
>> deployment failure.  In 1.1, neither of those works -- if a deployment
>> fails, there's seems to be nothing you can do except delete files out
>> of the repository.
>>
>> Thanks,
>>     Aaron
>>
>> On 6/10/06, Donald Woods <drw_web@yahoo.com> wrote:
>> > There have been postings to the user@geronimo list in the past about 
>> the
>> > same type of problems with 1.0, so maybe this can wait until 1.1.1
>> > unless its a very simple fix?
>> >
>> >
>> > -Donald
>> >
>> >
>> > Aaron Mulder wrote:
>> > > I thought maybe we could punt on this, but after using the current
>> > > build just a little bit, it's really nasty.  If a deployment fails,
>> > > you can't deploy that same module again (ever) without manually
>> > > deleting files from the repository:
>> > >
>> > > http://issues.apache.org/jira/browse/GERONIMO-2101
>> > >
>> > > I think we need to fix this for 1.1.
>> > >
>> > > I don't know if the better solution is to try to delete the files 
>> from
>> > > the repository when the deployment fails, or to be willing to
>> > > overwrite when a new deployment finds old files already there.  Any
>> > > suggestions?
>> > >
>> > > Thanks,
>> > >    Aaron
>> > >
>> > >
>> >
>> >
>> >
>>
> 
> 
>