You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by stuart robertson <st...@yahoo.com> on 2002/02/19 19:26:04 UTC
Nightly build status
I'm on the architecture team of a Fortune 100 company
that is about to start using Struts to build its web
applications.
It looks to me from reading the dev mailing list that
the core struts features are locked down, in
preparation for a release not too far off. We'd like
to give our developers a current snapshot, with the
intent to move to 1.1 when it comes out.
My question is, are there any particularly unstable
parts in the nightly builds that we should stay away
from? And are any particular nightly builds
recommended as a good starting point...that is, were
bleeding-edge changes checked in recently at some
point? We're fully aware that things are pre-release
still. But given that it seems to be so far along,
and that we should be able to submit bugfixes ourself
(hopefully) we'd like to go this route.
Any thoughts or comments on this would be very
helpful.
Thanks,
Stu
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Nightly build status -- one more question
Posted by stuart robertson <st...@yahoo.com>.
Any chance you tucked away a source version of that
nightly build? It looks like the apache nightly
builds only go back to early february. We'd like to
have the source for any builds we use so developers
can know how things work, and also so we could fix any
bugs that might pop up (unlikely, but still...).
Thanks for your help Ted.
Stu
--- Ted Husted <hu...@apache.org> wrote:
> The newest, bleeding edge features would be
>
> + the execute signature and declarative exceptions
> + role based security
> + multiple-configuration support
> + dynabeans
>
> These were added in January. The other features in
> the nightly build
> (mostly tag enchancements) have been in circulation
> much longer, and can
> be considered stable. (And, really should have been
> released in like Nov
> or Dec, but that was a busy time for all of us.)
>
> My very best advice would be to use a build from
> early January, until
> the latest wave of features settle in. I tucked away
> a binary from 12
> Jan that I've been using myself. This will work with
> the releases of
> Tiles and Validator that came about on or before
> that date.
>
>
http://husted.com/struts/resources/jakarta-struts-20020112.zip
>
> This will get you over the Commons dependencies
> hump, and put you in a
> good position to move over to the final release of
> 1.1, whenever that is
> ready.
>
> -Ted.
>
>
> stuart robertson wrote:
> >
> > I'm on the architecture team of a Fortune 100
> company
> > that is about to start using Struts to build its
> web
> > applications.
> >
> > It looks to me from reading the dev mailing list
> that
> > the core struts features are locked down, in
> > preparation for a release not too far off. We'd
> like
> > to give our developers a current snapshot, with
> the
> > intent to move to 1.1 when it comes out.
> >
> > My question is, are there any particularly
> unstable
> > parts in the nightly builds that we should stay
> away
> > from? And are any particular nightly builds
> > recommended as a good starting point...that is,
> were
> > bleeding-edge changes checked in recently at some
> > point? We're fully aware that things are
> pre-release
> > still. But given that it seems to be so far
> along,
> > and that we should be able to submit bugfixes
> ourself
> > (hopefully) we'd like to go this route.
> >
> > Any thoughts or comments on this would be very
> > helpful.
> >
> > Thanks,
> >
> > Stu
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Sports - Coverage of the 2002 Olympic Games
> > http://sports.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
> -- Ted Husted, Husted dot Com, Fairport NY US
> -- Developing Java Web Applications with Struts
> -- Tel: +1 585 737-3463
> -> Web: http://husted.com/about/services
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Nightly build status
Posted by stuart robertson <st...@yahoo.com>.
Thanks Ted. That's exactly what we'll do!
Stu
--- Ted Husted <hu...@apache.org> wrote:
> The newest, bleeding edge features would be
>
> + the execute signature and declarative exceptions
> + role based security
> + multiple-configuration support
> + dynabeans
>
> These were added in January. The other features in
> the nightly build
> (mostly tag enchancements) have been in circulation
> much longer, and can
> be considered stable. (And, really should have been
> released in like Nov
> or Dec, but that was a busy time for all of us.)
>
> My very best advice would be to use a build from
> early January, until
> the latest wave of features settle in. I tucked away
> a binary from 12
> Jan that I've been using myself. This will work with
> the releases of
> Tiles and Validator that came about on or before
> that date.
>
>
http://husted.com/struts/resources/jakarta-struts-20020112.zip
>
> This will get you over the Commons dependencies
> hump, and put you in a
> good position to move over to the final release of
> 1.1, whenever that is
> ready.
>
> -Ted.
>
>
> stuart robertson wrote:
> >
> > I'm on the architecture team of a Fortune 100
> company
> > that is about to start using Struts to build its
> web
> > applications.
> >
> > It looks to me from reading the dev mailing list
> that
> > the core struts features are locked down, in
> > preparation for a release not too far off. We'd
> like
> > to give our developers a current snapshot, with
> the
> > intent to move to 1.1 when it comes out.
> >
> > My question is, are there any particularly
> unstable
> > parts in the nightly builds that we should stay
> away
> > from? And are any particular nightly builds
> > recommended as a good starting point...that is,
> were
> > bleeding-edge changes checked in recently at some
> > point? We're fully aware that things are
> pre-release
> > still. But given that it seems to be so far
> along,
> > and that we should be able to submit bugfixes
> ourself
> > (hopefully) we'd like to go this route.
> >
> > Any thoughts or comments on this would be very
> > helpful.
> >
> > Thanks,
> >
> > Stu
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Sports - Coverage of the 2002 Olympic Games
> > http://sports.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
> -- Ted Husted, Husted dot Com, Fairport NY US
> -- Developing Java Web Applications with Struts
> -- Tel: +1 585 737-3463
> -> Web: http://husted.com/about/services
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Nightly build status
Posted by Ted Husted <hu...@apache.org>.
The newest, bleeding edge features would be
+ the execute signature and declarative exceptions
+ role based security
+ multiple-configuration support
+ dynabeans
These were added in January. The other features in the nightly build
(mostly tag enchancements) have been in circulation much longer, and can
be considered stable. (And, really should have been released in like Nov
or Dec, but that was a busy time for all of us.)
My very best advice would be to use a build from early January, until
the latest wave of features settle in. I tucked away a binary from 12
Jan that I've been using myself. This will work with the releases of
Tiles and Validator that came about on or before that date.
http://husted.com/struts/resources/jakarta-struts-20020112.zip
This will get you over the Commons dependencies hump, and put you in a
good position to move over to the final release of 1.1, whenever that is
ready.
-Ted.
stuart robertson wrote:
>
> I'm on the architecture team of a Fortune 100 company
> that is about to start using Struts to build its web
> applications.
>
> It looks to me from reading the dev mailing list that
> the core struts features are locked down, in
> preparation for a release not too far off. We'd like
> to give our developers a current snapshot, with the
> intent to move to 1.1 when it comes out.
>
> My question is, are there any particularly unstable
> parts in the nightly builds that we should stay away
> from? And are any particular nightly builds
> recommended as a good starting point...that is, were
> bleeding-edge changes checked in recently at some
> point? We're fully aware that things are pre-release
> still. But given that it seems to be so far along,
> and that we should be able to submit bugfixes ourself
> (hopefully) we'd like to go this route.
>
> Any thoughts or comments on this would be very
> helpful.
>
> Thanks,
>
> Stu
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Sports - Coverage of the 2002 Olympic Games
> http://sports.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
-- Ted Husted, Husted dot Com, Fairport NY US
-- Developing Java Web Applications with Struts
-- Tel: +1 585 737-3463
-> Web: http://husted.com/about/services
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>