geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Daughtrey <er...@schemacity.org>
Subject Re: Installer -- Phase 2
Date Mon, 19 Dec 2005 21:05:49 GMT

Heinz,

I'm not in control of when this function gets pulled into the product.  The 
1.0 cutoff passed me by, but the current code should make it into 1.0.1.

The code that David's suggesting should not take too long, but this 
functionality was slated for 1.1. 

If you're willing to do a build, you could pull the latest patch off the JIRA 
GERONIMO-1192, apply it against branches/1.0, build it and give it a whirl.

The patch is: installer-branches-1.0-200512181734.patch.gz.
gunzip it and apply it in the geronimo directory:
patch -p0 < installer-branches-1.0-200512181734.patch.

Otherwise, I believe an installer will hit 1.0.1.

 On Monday 19 December 2005 14:05, Heinz Drews wrote:
> I will try to be patient.
>
> Can I get the Installer as Xmas gift :-)
>
> On 12/19/05, Erik Daughtrey <erikd@schemacity.org> wrote:
> > In principal, I agree with your comments about minimal, default and
> > custom install, but I don't think this approach is necessary yet.
> > Once you have the opportunity to try the installer I think you'll see
> > what I mean.  I could explain, but "a picture is worth a thousand words"
> > as they say.
> > There really are just a few options to select.  Mixing and matching these
> > options into various configuration matrices might actually be more
> > confusing.
> >
> >  On Monday 19 December 2005 12:41, Heinz Drews wrote:
> > > Hello Erik,
> > >
> > > the approach sounds just perfect.
> > >
> > > It would be great if the Installer would support a number of standard
> > > configurations.
> > >
> > > e.g "Minimal", "Default", ... "Custom".
> > >
> > > Best regards,
> > > Heinz
> > >
> > > On 12/19/05, Erik Daughtrey <erikd@schemacity.org> wrote:
> > > > The next phase of the installer is supposed to only install selected
> > > > components as well as activating them in config.xml.  Currently, the
> > > > installer installs all components and modifies config.xml to only
> > > > start those selected at install time.
> > > >
> > > > My current plan is to make this an optional feature by adding
> > > > somthing like a "Lean install" pack that can be selected.  This way
> > > > folks who happen to want everything installed, but only some parts
> > > > configured can have the current functionality.
> > > >
> > > > Does anyone vehemently disagree with this approach?
> > > >
> > > > --
> > > >
> > > > Regards,
> > > >
> > > > Erik
> >
> > --
> >
> > Regards,
> >
> > Erik

-- 

Regards,

Erik

Mime
View raw message