Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'Struts Developers List'" <dev@struts.apache.org>
References: <1c661f2f0908052212v5d71396cyd3ca3b01640df3ff@mail.gmail.com>
 <b9e663070908102238q26f14757n9d491afcf95ca865@mail.gmail.com>
 <436d9a250908102252q1ccfe031s85f602a6f79521bc@mail.gmail.com>
 <DDF9E66F-0F69-400E-9DFB-BAC53F8553F6@pontarelli.com>
 <d8bdeb6f0908111937x39fb1c50w7119df581f50f628@mail.gmail.com>
 <b9e663070908121436y6a1961acye5e44a6386408da@mail.gmail.com>
 <adba96190908121445t19a735a3vdcd5c7bc27130857@mail.gmail.com>
 <b9e663070908121901p62fe14d2re3b9cb1dc3c8f452@mail.gmail.com>
 <436d9a250908121906h3b48ecb8h395f55e78e4fb48e@mail.gmail.com>
 <A0C1236D-FC17-4181-B8FD-F550A09E0BC0@pontarelli.com>
 <d8bdeb6f0908130944t3a584ac5i7b0f467ca42461ac@mail.gmail.com>
Subject: RE: Let's kill xwork (was Re: 2.1.8 release?)
Date: Thu, 13 Aug 2009 13:00:44 -0400
Organization: PD Inc
Message-ID: <A7E2A5FDDDD64DB1978304CF3C2AAB09@phoenix>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <d8bdeb6f0908130944t3a584ac5i7b0f467ca42461ac@mail.gmail.com>
Thread-Index: AcocNYHMuC/gMGkJSqe2BSad3aicNwAAc0sg

=20

> -----Original Message-----
> From: Musachy Barroso [mailto:musachy@gmail.com]=20
> Sent: Thursday, August 13, 2009 12:45
> To: Struts Developers List
> Subject: Re: Let's kill xwork (was Re: 2.1.8 release?)
>=20
> Have we reached any kind of consensus about bringing xwork=20
> in? If we are going to release a new major version could be=20
> another discussion.


(Assumption: waiting on release because patches made to trunk not yet =
included
into released jar....)

Why can we use their trunk or snapshots?

If we fork we are essentially loosing their QA process anyway...

My .02$

>=20
> musachy
>=20
> On Wed, Aug 12, 2009 at 9:27 PM, Brian=20
> Pontarelli<brian@pontarelli.com> wrote:
> > Why so hesitant to do another release? It has been a long=20
> time since=20
> > 2.0. I think it is time for some major rework and releasing=20
> a new major version.
> >
> > Sent from my iPhone
> >
> > On Aug 12, 2009, at 8:06 PM, Don Brown <mrdon@twdata.org> wrote:
> >
> >> On Thu, Aug 13, 2009 at 12:01 PM, Paul=20
> Benedict<pbenedict@apache.org>
> >> wrote:
> >>>
> >>> Are you sure it's not an incompatible change? I thought the=20
> >>> discussion was the importing of XWork and getting rid of its=20
> >>> branding. That means all of XWork's annotations and=20
> packages would=20
> >>> be changed to org.apache.struts. I don't believe there is=20
> any desire=20
> >>> to keep com.opensymphony when this occurs.
> >>> So my thinking would be this would be an incompatible=20
> change. Did I=20
> >>> get it wrong?
> >>
> >> I think completely removing any trace of xwork is a good long term=20
> >> 3.0 goal, but for now, we would simply fork it, keeping=20
> the package=20
> >> structure and class names.
> >>
> >> Don
> >>
> >>>
> >>> On Wed, Aug 12, 2009 at 4:45 PM, Wendy Smoak=20
> <wsmoak@gmail.com> wrote:
> >>>
> >>>> On Wed, Aug 12, 2009 at 2:36 PM, Paul=20
> >>>> Benedict<pbenedict@apache.org>
> >>>> wrote:
> >>>>>
> >>>>> I definitely agree that Struts 3 would be a good=20
> candidate to do=20
> >>>>> this
> >>>>
> >>>> XWork
> >>>>>
> >>>>> migration. It is not an appropriate candidate for 2.1, or 2.2.=20
> >>>>> However,
> >>>>
> >>>> if
> >>>>>
> >>>>> you like to do a 2.5 (I dislike superficial jumps in versions=20
> >>>>> though),
> >>>>
> >>>> then
> >>>>>
> >>>>> it might be acceptable in the 2.x branch.
> >>>>
> >>>> IMO "Struts 3" would imply a major change in Struts itself, the=20
> >>>> possibility of backwards incompatible changes, etc. =A0
> This isn't...
> >>>> community aspects aside, it's just moving some code from one svn=20
> >>>> repo to another. =A0-Wendy
> >>>>
> >>>>=20
> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For=20
> >>>> additional commands, e-mail: dev-help@struts.apache.org
> >>>>
> >>>>
> >>>
> >>
> >>=20
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For=20
> >> additional commands, e-mail: dev-help@struts.apache.org
> >>
> >
> >=20
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For=20
> > additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>=20
>=20
>=20
> --
> "Hey you! Would you help me to carry the stone?" Pink Floyd
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For=20
> additional commands, e-mail: dev-help@struts.apache.org
>=20
>=20


--
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
This message is copyright PD Inc, subject to license 20080407P00.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org