2010/1/6 Musachy Barroso musa...@gmail.com:
Really? I haven't seen much discussion since I posted what I believe
is the set of alternatives that we need to choose from. I saw quite a
few different opinions expressed, almost all in different terms (which
is why I posted what I did), but I'm not
just to close this, is anyone opposed to moving xwork under the struts
dir as a maven module?
On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
2010/1/6 Musachy Barroso musa...@gmail.com:
Really? I haven't seen much discussion since I posted what I believe
is
who will create the mojo?
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede
On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso musa...@gmail.com wrote:
just to close this, is anyone opposed to moving xwork under the struts
dir as a maven module?
Uh, it's already under the 'struts' dir as a Maven project.
In the context of the options I listed before, you appear to want:
What we have been talking about and (vaguely) mentioned before is to
move it under /struts/trunk/xwork and make it a module just like core
is, so the release is coupled to the struts release and everything can
be built easily
musahcy
On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper
On Fri, Jan 8, 2010 at 5:20 PM, Musachy Barroso musa...@gmail.com wrote:
What we have been talking about and (vaguely) mentioned before is to
move it under /struts/trunk/xwork and make it a module just like core
is, so the release is coupled to the struts release and everything can
be built
one small point I forgot to mention. If we do it this way we won't get
more folks complaining about struts not building because of a recent
change in xwork. It will make it easier for the dev making a release
and for people building from trunk.
On Fri, Jan 8, 2010 at 4:29 PM, Wendy Smoak
I agree with Wendy.
XWork is currently located here:
http://svn.apache.org/viewvc/struts/xwork/
I advocate its move to here:
http://svn.apache.org/viewvc/struts/struts2/trunk/xwork/ (doesn't exist)
PS: The one caveat is if XWork really is valuable and would make it
good in a theoretical Struts
On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso musa...@gmail.com wrote:
What we have been talking about and (vaguely) mentioned before is to
move it under /struts/trunk/xwork
Unless I'm mistaken, that is _not_ where you want to move it. You want
it under 'struts2', don't you?
Today it is
On Fri, Jan 8, 2010 at 4:29 PM, Wendy Smoak wsm...@gmail.com wrote:
On Fri, Jan 8, 2010 at 5:20 PM, Musachy Barroso musa...@gmail.com wrote:
What we have been talking about and (vaguely) mentioned before is to
move it under /struts/trunk/xwork and make it a module just like core
is, so the
On Fri, Jan 8, 2010 at 5:11 PM, Paul Benedict pbened...@apache.org wrote:
I agree with Wendy.
XWork is currently located here:
http://svn.apache.org/viewvc/struts/xwork/
I advocate its move to here:
http://svn.apache.org/viewvc/struts/struts2/trunk/xwork/ (doesn't exist)
PS: The one
On Fri, Jan 8, 2010 at 6:27 PM, Martin Cooper mart...@apache.org wrote:
We need to get past this. Where it lives does *not* have an impact on
whether it's built together with, or separately from, the rest of S2.
It can stay where it is and also be built along with, and released as
part of,
On Fri, Jan 8, 2010 at 5:40 PM, Wendy Smoak wsm...@gmail.com wrote:
On Fri, Jan 8, 2010 at 6:27 PM, Martin Cooper mart...@apache.org wrote:
We need to get past this. Where it lives does *not* have an impact on
whether it's built together with, or separately from, the rest of S2.
It can stay
is it possible if we talk struts3, we put REST as default main feature,
outside new Apache Xwork
F
14 matches
Mail list logo
