cutting a 2.2 release

[Sanjiva Weerawarana <sa...@watson.ibm.com>]

I would like to work on a 2.2 release ASAP. Matt has volunteered
to take over the release manager role and I will help with docs
and other stuff. Matt's going to post a list of things that we
know have to be done soon. If there are things you'd like to have
done before 2.2 is cut speak now or hold your peace forever. If
there are any posted bugs or patches that haven't been incorporated
please point them out ..

If there are any strong objections to cutting a 2.2 release please
raise them now.

Thanks,

Sanjiva.

RE: cutting a 2.2 release

["Matthew J. Duftler" <du...@watson.ibm.com>]

Hi Glen,

This is a good idea. I have some ANT-script to do this already, I will add
it to the build file.

Thanks,
-Matt

> -----Original Message-----
> From: Glen Daniels [mailto:gdaniels@macromedia.com]
> Sent: Wednesday, May 16, 2001 12:09 AM
> To: soap-dev@xml.apache.org
> Subject: Re: cutting a 2.2 release
>
>
> Off the top of my head, it would be really good if the build could be
> changed to put things in a .war-able form (I can do this part),
> and then the
> deployment and installation instructions for most servlet engines
> should be
> edited to be significantly easier.
>
> --G
>
> ----- Original Message -----
> From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
> To: "Apache SOAP" <so...@xml.apache.org>
> Cc: <so...@xml.apache.org>
> Sent: Tuesday, May 15, 2001 4:27 PM
> Subject: cutting a 2.2 release
>
>
> > I would like to work on a 2.2 release ASAP. Matt has volunteered
> > to take over the release manager role and I will help with docs
> > and other stuff. Matt's going to post a list of things that we
> > know have to be done soon. If there are things you'd like to have
> > done before 2.2 is cut speak now or hold your peace forever. If
> > there are any posted bugs or patches that haven't been incorporated
> > please point them out ..
> >
> > If there are any strong objections to cutting a 2.2 release please
> > raise them now.
> >
> > Thanks,
> >
> > Sanjiva.
> >
> >
>

Re: cutting a 2.2 release

[Glen Daniels <gd...@macromedia.com>]

Actually, I think (2) is the way to go.  The actual .war file is, as you say,
redundant - and a) it's super-easy to generate ("jar cf ../soap.war *"), and b)
most app-servers (I know JRun, Tomcat, and WebLogic at least can all do this)
will happily let you deploy from a directory as well as a .war file.

My point was just that it's important to get the samples into WEB-INF/classes,
and the soap.jar into WEB-INF/lib, so we can avoid all the nasty classpath
changes.

--Glen

----- Original Message -----
From: "Matthew J. Duftler" <du...@watson.ibm.com>
To: <so...@xml.apache.org>
Sent: Wednesday, May 16, 2001 9:18 AM
Subject: RE: cutting a 2.2 release


> Hi Glen,
>
> I should have mentioned one other thing. If the build file generates the war
> file at the time it generates the rest of the distribution, there will be a
> war file containing basically the same stuff that's in the webapps
> directory.
>
> The way I see it, our choices are:
>
> (1) Have both the expanded webapps directory (which is what we have now) and
> the war file in the distribution.
> (2) Have only the expanded webapps directory, but include the build script
> (or instructions on how to do it with JAR) to war it up.
> (3) Have only the war file, but include directions on how to expand it if
> necessary.
>
> Personally, I vote for (1). What do others think?
>
> Thanks,
> -Matt
>
> > -----Original Message-----
> > From: Glen Daniels [mailto:gdaniels@macromedia.com]
> > Sent: Wednesday, May 16, 2001 12:09 AM
> > To: soap-dev@xml.apache.org
> > Subject: Re: cutting a 2.2 release
> >
> >
> > Off the top of my head, it would be really good if the build could be
> > changed to put things in a .war-able form (I can do this part),
> > and then the
> > deployment and installation instructions for most servlet engines
> > should be
> > edited to be significantly easier.
> >
> > --G
> >
> > ----- Original Message -----
> > From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
> > To: "Apache SOAP" <so...@xml.apache.org>
> > Cc: <so...@xml.apache.org>
> > Sent: Tuesday, May 15, 2001 4:27 PM
> > Subject: cutting a 2.2 release
> >
> >
> > > I would like to work on a 2.2 release ASAP. Matt has volunteered
> > > to take over the release manager role and I will help with docs
> > > and other stuff. Matt's going to post a list of things that we
> > > know have to be done soon. If there are things you'd like to have
> > > done before 2.2 is cut speak now or hold your peace forever. If
> > > there are any posted bugs or patches that haven't been incorporated
> > > please point them out ..
> > >
> > > If there are any strong objections to cutting a 2.2 release please
> > > raise them now.
> > >
> > > Thanks,
> > >
> > > Sanjiva.
> > >
> > >
> >
>

RE: cutting a 2.2 release

["Matthew J. Duftler" <du...@watson.ibm.com>]

Hi Glen,

I should have mentioned one other thing. If the build file generates the war
file at the time it generates the rest of the distribution, there will be a
war file containing basically the same stuff that's in the webapps
directory.

The way I see it, our choices are:

(1) Have both the expanded webapps directory (which is what we have now) and
the war file in the distribution.
(2) Have only the expanded webapps directory, but include the build script
(or instructions on how to do it with JAR) to war it up.
(3) Have only the war file, but include directions on how to expand it if
necessary.

Personally, I vote for (1). What do others think?

Thanks,
-Matt

> -----Original Message-----
> From: Glen Daniels [mailto:gdaniels@macromedia.com]
> Sent: Wednesday, May 16, 2001 12:09 AM
> To: soap-dev@xml.apache.org
> Subject: Re: cutting a 2.2 release
>
>
> Off the top of my head, it would be really good if the build could be
> changed to put things in a .war-able form (I can do this part),
> and then the
> deployment and installation instructions for most servlet engines
> should be
> edited to be significantly easier.
>
> --G
>
> ----- Original Message -----
> From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
> To: "Apache SOAP" <so...@xml.apache.org>
> Cc: <so...@xml.apache.org>
> Sent: Tuesday, May 15, 2001 4:27 PM
> Subject: cutting a 2.2 release
>
>
> > I would like to work on a 2.2 release ASAP. Matt has volunteered
> > to take over the release manager role and I will help with docs
> > and other stuff. Matt's going to post a list of things that we
> > know have to be done soon. If there are things you'd like to have
> > done before 2.2 is cut speak now or hold your peace forever. If
> > there are any posted bugs or patches that haven't been incorporated
> > please point them out ..
> >
> > If there are any strong objections to cutting a 2.2 release please
> > raise them now.
> >
> > Thanks,
> >
> > Sanjiva.
> >
> >
>

Re: cutting a 2.2 release

[Glen Daniels <gd...@macromedia.com>]

Off the top of my head, it would be really good if the build could be
changed to put things in a .war-able form (I can do this part), and then the
deployment and installation instructions for most servlet engines should be
edited to be significantly easier.

--G

----- Original Message -----
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
To: "Apache SOAP" <so...@xml.apache.org>
Cc: <so...@xml.apache.org>
Sent: Tuesday, May 15, 2001 4:27 PM
Subject: cutting a 2.2 release


> I would like to work on a 2.2 release ASAP. Matt has volunteered
> to take over the release manager role and I will help with docs
> and other stuff. Matt's going to post a list of things that we
> know have to be done soon. If there are things you'd like to have
> done before 2.2 is cut speak now or hold your peace forever. If
> there are any posted bugs or patches that haven't been incorporated
> please point them out ..
>
> If there are any strong objections to cutting a 2.2 release please
> raise them now.
>
> Thanks,
>
> Sanjiva.
>
>