geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder" <ammul...@alumni.princeton.edu>
Subject Re: 1.1 Blocker - Bad deployment jams repo
Date Sat, 10 Jun 2006 17:40:49 GMT
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
> > >
> > >
> >
> >
> >
>

Mime
View raw message