You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Lukasz Lenart <lu...@googlemail.com> on 2010/01/06 08:37:28 UTC
Re: XWork has landed!
2009/12/28 Paul Benedict <pb...@apache.org>:
> My fault for not being clear. I was intending to say XWork should be a
> "child module" (in the Maven sense) so it's actually part of Struts2
> build and versioning process.
Any news? I would like to start some refactoring in Xwork and it will
be nice to know where we are ;-)
Regards
--
Lukasz
http://www.lenart.org.pl/
http://javarsovia.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Mon, Jan 18, 2010 at 9:24 AM, Musachy Barroso <mu...@gmail.com> wrote:
> Martin does this sound good to you? I think going with just core is a
> safe option.
I have no problem with it. I just want to make sure everyone
understands, and is on board with, exactly what we're doing before we
do it.
--
Martin Cooper
> musachy
>
> //when is gmail going to realize that no...I meant "musachy" not "mustache" :)
>
> On Fri, Jan 15, 2010 at 11:09 AM, Wes Wannemacher <we...@wantii.com> wrote:
>> The xwork module are core, plugins and showcase. It was only recently
>> that xwork was broken up and I think it was meant to make things more
>> manageable. Personally, my vote is for #2 as well. If we need to make
>> xwork-specific plugins or continue building the xwork showcase, then
>> we can move those over to the apps and plugins struts2 modules.
>> Struts2 depends on xwork-core, so I think we start with that one and
>> bring plugins and showcase over if the need dictates.
>>
>> -Wes
>>
>> /summary - (b)
>>
>> On Fri, Jan 15, 2010 at 1:47 PM, Musachy Barroso <mu...@gmail.com> wrote:
>>> Well, I would like to hear from Rene or Rainer about #2
>>>
>>> "2) (a) all of XWork, (b) just the XWork core, (c) some other subset of XWork"
>>>
>>> To be honest I don't even know what the other stuff is(I vaguely
>>> remember something about plugins for xwork), I think we should go with
>>> b) just core.
>>>
>>> On Fri, Jan 15, 2010 at 10:34 AM, Martin Cooper <ma...@apache.org> wrote:
>>>> On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso <mu...@gmail.com> wrote:
>>>>> we are all now in the same page right? (meaning we agree to move xwork
>>>>> under http://svn.apache.org/repos/asf/struts/struts2/trunk/)
>>>>
>>>> We don't have an answer to #2 yet (I saw opinions for both a and b),
>>>> but we have answers to #1 and #3, so we're close. ;-)
>>>>
>>>> --
>>>> Martin Cooper
>>>>
>>>>
>>>>> musachy
>>>>>
>>>>> On Sat, Jan 9, 2010 at 12:51 AM, Musachy Barroso <mu...@gmail.com> wrote:
>>>>>> yes I meant under struts2, sorry for the confusion
>>>>>>
>>>>>> On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>>>> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>>>>>>>
>>>>>>> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>>>>>>>
>>>>>>> and S2 is here:
>>>>>>>
>>>>>>> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>>>>>>
>>>>>>> Since there is no 'struts/trunk', what you said above is unlikely to
>>>>>>> be what you actually mean. This is why I'm trying to get an accurate
>>>>>>> specification of what you *really* want. How can we agree if you're
>>>>>>> not accurately stating what you want / plan to do?
>>>>>>>
>>>>>>>> and make it a module just like core
>>>>>>>> is, so the release is coupled to the struts release and everything can
>>>>>>>> be built easily
>>>>>>>
>>>>>>> Great. I have no problem with that. Now, why is 1a better than 1c, for
>>>>>>> example? And what is the answer to 2? Neither of these are answered by
>>>>>>> the statement that you want to be able to build easily.
>>>>>>>
>>>>>>> --
>>>>>>> Martin Cooper
>>>>>>>
>>>>>>>
>>>>>>>> musahcy
>>>>>>>>
>>>>>>>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>>>>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>>>>>>>
>>>>>>>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>>>>>>>> especially (c).
>>>>>>>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>>>>>>>> which of the options this is.
>>>>>>>>> 3) Unclear. Maybe (b)?
>>>>>>>>>
>>>>>>>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>>>>>>>> proposal and an explanation of why it's the right way to go.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Martin Cooper
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>>>>>>>> <lu...@googlemail.com> wrote:
>>>>>>>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>>>>>>>> emerge.
>>>>>>>>>>>
>>>>>>>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>>>>>>>> release process (XWork will be released with Struts2 together) and
>>>>>>>>>>> allow me to work with XWork and see at the same time what will happen
>>>>>>>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>> --
>>>>>>>>>>> Lukasz
>>>>>>>>>>> Kapituła Javarsovia 2010
>>>>>>>>>>> http://javarsovia.pl
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Wes Wannemacher
>>
>> Head Engineer, WanTii, Inc.
>> Need Training? Struts, Spring, Maven, Tomcat...
>> Ask me for a quote!
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
Martin does this sound good to you? I think going with just core is a
safe option.
musachy
//when is gmail going to realize that no...I meant "musachy" not "mustache" :)
On Fri, Jan 15, 2010 at 11:09 AM, Wes Wannemacher <we...@wantii.com> wrote:
> The xwork module are core, plugins and showcase. It was only recently
> that xwork was broken up and I think it was meant to make things more
> manageable. Personally, my vote is for #2 as well. If we need to make
> xwork-specific plugins or continue building the xwork showcase, then
> we can move those over to the apps and plugins struts2 modules.
> Struts2 depends on xwork-core, so I think we start with that one and
> bring plugins and showcase over if the need dictates.
>
> -Wes
>
> /summary - (b)
>
> On Fri, Jan 15, 2010 at 1:47 PM, Musachy Barroso <mu...@gmail.com> wrote:
>> Well, I would like to hear from Rene or Rainer about #2
>>
>> "2) (a) all of XWork, (b) just the XWork core, (c) some other subset of XWork"
>>
>> To be honest I don't even know what the other stuff is(I vaguely
>> remember something about plugins for xwork), I think we should go with
>> b) just core.
>>
>> On Fri, Jan 15, 2010 at 10:34 AM, Martin Cooper <ma...@apache.org> wrote:
>>> On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso <mu...@gmail.com> wrote:
>>>> we are all now in the same page right? (meaning we agree to move xwork
>>>> under http://svn.apache.org/repos/asf/struts/struts2/trunk/)
>>>
>>> We don't have an answer to #2 yet (I saw opinions for both a and b),
>>> but we have answers to #1 and #3, so we're close. ;-)
>>>
>>> --
>>> Martin Cooper
>>>
>>>
>>>> musachy
>>>>
>>>> On Sat, Jan 9, 2010 at 12:51 AM, Musachy Barroso <mu...@gmail.com> wrote:
>>>>> yes I meant under struts2, sorry for the confusion
>>>>>
>>>>> On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>>> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>>>>>>
>>>>>> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>>>>>>
>>>>>> and S2 is here:
>>>>>>
>>>>>> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>>>>>
>>>>>> Since there is no 'struts/trunk', what you said above is unlikely to
>>>>>> be what you actually mean. This is why I'm trying to get an accurate
>>>>>> specification of what you *really* want. How can we agree if you're
>>>>>> not accurately stating what you want / plan to do?
>>>>>>
>>>>>>> and make it a module just like core
>>>>>>> is, so the release is coupled to the struts release and everything can
>>>>>>> be built easily
>>>>>>
>>>>>> Great. I have no problem with that. Now, why is 1a better than 1c, for
>>>>>> example? And what is the answer to 2? Neither of these are answered by
>>>>>> the statement that you want to be able to build easily.
>>>>>>
>>>>>> --
>>>>>> Martin Cooper
>>>>>>
>>>>>>
>>>>>>> musahcy
>>>>>>>
>>>>>>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>>>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>>>>>>
>>>>>>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>>>>>>> especially (c).
>>>>>>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>>>>>>> which of the options this is.
>>>>>>>> 3) Unclear. Maybe (b)?
>>>>>>>>
>>>>>>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>>>>>>> proposal and an explanation of why it's the right way to go.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Martin Cooper
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>>>>>>> <lu...@googlemail.com> wrote:
>>>>>>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>>>>>>> emerge.
>>>>>>>>>>
>>>>>>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>>>>>>> release process (XWork will be released with Struts2 together) and
>>>>>>>>>> allow me to work with XWork and see at the same time what will happen
>>>>>>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> --
>>>>>>>>>> Lukasz
>>>>>>>>>> Kapituła Javarsovia 2010
>>>>>>>>>> http://javarsovia.pl
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
>
> --
> Wes Wannemacher
>
> Head Engineer, WanTii, Inc.
> Need Training? Struts, Spring, Maven, Tomcat...
> Ask me for a quote!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Wes Wannemacher <we...@wantii.com>.
The xwork module are core, plugins and showcase. It was only recently
that xwork was broken up and I think it was meant to make things more
manageable. Personally, my vote is for #2 as well. If we need to make
xwork-specific plugins or continue building the xwork showcase, then
we can move those over to the apps and plugins struts2 modules.
Struts2 depends on xwork-core, so I think we start with that one and
bring plugins and showcase over if the need dictates.
-Wes
/summary - (b)
On Fri, Jan 15, 2010 at 1:47 PM, Musachy Barroso <mu...@gmail.com> wrote:
> Well, I would like to hear from Rene or Rainer about #2
>
> "2) (a) all of XWork, (b) just the XWork core, (c) some other subset of XWork"
>
> To be honest I don't even know what the other stuff is(I vaguely
> remember something about plugins for xwork), I think we should go with
> b) just core.
>
> On Fri, Jan 15, 2010 at 10:34 AM, Martin Cooper <ma...@apache.org> wrote:
>> On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso <mu...@gmail.com> wrote:
>>> we are all now in the same page right? (meaning we agree to move xwork
>>> under http://svn.apache.org/repos/asf/struts/struts2/trunk/)
>>
>> We don't have an answer to #2 yet (I saw opinions for both a and b),
>> but we have answers to #1 and #3, so we're close. ;-)
>>
>> --
>> Martin Cooper
>>
>>
>>> musachy
>>>
>>> On Sat, Jan 9, 2010 at 12:51 AM, Musachy Barroso <mu...@gmail.com> wrote:
>>>> yes I meant under struts2, sorry for the confusion
>>>>
>>>> On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>>>>>
>>>>> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>>>>>
>>>>> and S2 is here:
>>>>>
>>>>> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>>>>
>>>>> Since there is no 'struts/trunk', what you said above is unlikely to
>>>>> be what you actually mean. This is why I'm trying to get an accurate
>>>>> specification of what you *really* want. How can we agree if you're
>>>>> not accurately stating what you want / plan to do?
>>>>>
>>>>>> and make it a module just like core
>>>>>> is, so the release is coupled to the struts release and everything can
>>>>>> be built easily
>>>>>
>>>>> Great. I have no problem with that. Now, why is 1a better than 1c, for
>>>>> example? And what is the answer to 2? Neither of these are answered by
>>>>> the statement that you want to be able to build easily.
>>>>>
>>>>> --
>>>>> Martin Cooper
>>>>>
>>>>>
>>>>>> musahcy
>>>>>>
>>>>>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>>>>>
>>>>>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>>>>>> especially (c).
>>>>>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>>>>>> which of the options this is.
>>>>>>> 3) Unclear. Maybe (b)?
>>>>>>>
>>>>>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>>>>>> proposal and an explanation of why it's the right way to go.
>>>>>>>
>>>>>>> --
>>>>>>> Martin Cooper
>>>>>>>
>>>>>>>
>>>>>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>>>>>> <lu...@googlemail.com> wrote:
>>>>>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>>>>>> emerge.
>>>>>>>>>
>>>>>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>>>>>> release process (XWork will be released with Struts2 together) and
>>>>>>>>> allow me to work with XWork and see at the same time what will happen
>>>>>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> --
>>>>>>>>> Lukasz
>>>>>>>>> Kapituła Javarsovia 2010
>>>>>>>>> http://javarsovia.pl
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Wes Wannemacher
Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
Well, I would like to hear from Rene or Rainer about #2
"2) (a) all of XWork, (b) just the XWork core, (c) some other subset of XWork"
To be honest I don't even know what the other stuff is(I vaguely
remember something about plugins for xwork), I think we should go with
b) just core.
On Fri, Jan 15, 2010 at 10:34 AM, Martin Cooper <ma...@apache.org> wrote:
> On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso <mu...@gmail.com> wrote:
>> we are all now in the same page right? (meaning we agree to move xwork
>> under http://svn.apache.org/repos/asf/struts/struts2/trunk/)
>
> We don't have an answer to #2 yet (I saw opinions for both a and b),
> but we have answers to #1 and #3, so we're close. ;-)
>
> --
> Martin Cooper
>
>
>> musachy
>>
>> On Sat, Jan 9, 2010 at 12:51 AM, Musachy Barroso <mu...@gmail.com> wrote:
>>> yes I meant under struts2, sorry for the confusion
>>>
>>> On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
>>>> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>>>>
>>>> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>>>>
>>>> and S2 is here:
>>>>
>>>> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>>>
>>>> Since there is no 'struts/trunk', what you said above is unlikely to
>>>> be what you actually mean. This is why I'm trying to get an accurate
>>>> specification of what you *really* want. How can we agree if you're
>>>> not accurately stating what you want / plan to do?
>>>>
>>>>> and make it a module just like core
>>>>> is, so the release is coupled to the struts release and everything can
>>>>> be built easily
>>>>
>>>> Great. I have no problem with that. Now, why is 1a better than 1c, for
>>>> example? And what is the answer to 2? Neither of these are answered by
>>>> the statement that you want to be able to build easily.
>>>>
>>>> --
>>>> Martin Cooper
>>>>
>>>>
>>>>> musahcy
>>>>>
>>>>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>>>>
>>>>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>>>>> especially (c).
>>>>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>>>>> which of the options this is.
>>>>>> 3) Unclear. Maybe (b)?
>>>>>>
>>>>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>>>>> proposal and an explanation of why it's the right way to go.
>>>>>>
>>>>>> --
>>>>>> Martin Cooper
>>>>>>
>>>>>>
>>>>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>>>>> <lu...@googlemail.com> wrote:
>>>>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>>>>> emerge.
>>>>>>>>
>>>>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>>>>> release process (XWork will be released with Struts2 together) and
>>>>>>>> allow me to work with XWork and see at the same time what will happen
>>>>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> --
>>>>>>>> Lukasz
>>>>>>>> Kapituła Javarsovia 2010
>>>>>>>> http://javarsovia.pl
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso <mu...@gmail.com> wrote:
> we are all now in the same page right? (meaning we agree to move xwork
> under http://svn.apache.org/repos/asf/struts/struts2/trunk/)
We don't have an answer to #2 yet (I saw opinions for both a and b),
but we have answers to #1 and #3, so we're close. ;-)
--
Martin Cooper
> musachy
>
> On Sat, Jan 9, 2010 at 12:51 AM, Musachy Barroso <mu...@gmail.com> wrote:
>> yes I meant under struts2, sorry for the confusion
>>
>> On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
>>> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>>>
>>> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>>>
>>> and S2 is here:
>>>
>>> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>>
>>> Since there is no 'struts/trunk', what you said above is unlikely to
>>> be what you actually mean. This is why I'm trying to get an accurate
>>> specification of what you *really* want. How can we agree if you're
>>> not accurately stating what you want / plan to do?
>>>
>>>> and make it a module just like core
>>>> is, so the release is coupled to the struts release and everything can
>>>> be built easily
>>>
>>> Great. I have no problem with that. Now, why is 1a better than 1c, for
>>> example? And what is the answer to 2? Neither of these are answered by
>>> the statement that you want to be able to build easily.
>>>
>>> --
>>> Martin Cooper
>>>
>>>
>>>> musahcy
>>>>
>>>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>>>
>>>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>>>> especially (c).
>>>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>>>> which of the options this is.
>>>>> 3) Unclear. Maybe (b)?
>>>>>
>>>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>>>> proposal and an explanation of why it's the right way to go.
>>>>>
>>>>> --
>>>>> Martin Cooper
>>>>>
>>>>>
>>>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>>>> <lu...@googlemail.com> wrote:
>>>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>>>> emerge.
>>>>>>>
>>>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>>>> release process (XWork will be released with Struts2 together) and
>>>>>>> allow me to work with XWork and see at the same time what will happen
>>>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>> --
>>>>>>> Lukasz
>>>>>>> Kapituła Javarsovia 2010
>>>>>>> http://javarsovia.pl
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Paul Benedict <pb...@apache.org>.
You would move it here:
http://svn.apache.org/repos/asf/struts/struts2/trunk/xwork/
Paul
On Fri, Jan 15, 2010 at 12:23 PM, Musachy Barroso <mu...@gmail.com> wrote:
> we are all now in the same page right? (meaning we agree to move xwork
> under http://svn.apache.org/repos/asf/struts/struts2/trunk/)
>
> musachy
>
> On Sat, Jan 9, 2010 at 12:51 AM, Musachy Barroso <mu...@gmail.com> wrote:
>> yes I meant under struts2, sorry for the confusion
>>
>> On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
>>> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>>>
>>> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>>>
>>> and S2 is here:
>>>
>>> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>>
>>> Since there is no 'struts/trunk', what you said above is unlikely to
>>> be what you actually mean. This is why I'm trying to get an accurate
>>> specification of what you *really* want. How can we agree if you're
>>> not accurately stating what you want / plan to do?
>>>
>>>> and make it a module just like core
>>>> is, so the release is coupled to the struts release and everything can
>>>> be built easily
>>>
>>> Great. I have no problem with that. Now, why is 1a better than 1c, for
>>> example? And what is the answer to 2? Neither of these are answered by
>>> the statement that you want to be able to build easily.
>>>
>>> --
>>> Martin Cooper
>>>
>>>
>>>> musahcy
>>>>
>>>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>>>
>>>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>>>> especially (c).
>>>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>>>> which of the options this is.
>>>>> 3) Unclear. Maybe (b)?
>>>>>
>>>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>>>> proposal and an explanation of why it's the right way to go.
>>>>>
>>>>> --
>>>>> Martin Cooper
>>>>>
>>>>>
>>>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>>>> <lu...@googlemail.com> wrote:
>>>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>>>> emerge.
>>>>>>>
>>>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>>>> release process (XWork will be released with Struts2 together) and
>>>>>>> allow me to work with XWork and see at the same time what will happen
>>>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>> --
>>>>>>> Lukasz
>>>>>>> Kapituła Javarsovia 2010
>>>>>>> http://javarsovia.pl
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
we are all now in the same page right? (meaning we agree to move xwork
under http://svn.apache.org/repos/asf/struts/struts2/trunk/)
musachy
On Sat, Jan 9, 2010 at 12:51 AM, Musachy Barroso <mu...@gmail.com> wrote:
> yes I meant under struts2, sorry for the confusion
>
> On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
>> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>>
>> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>>
>> and S2 is here:
>>
>> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>
>> Since there is no 'struts/trunk', what you said above is unlikely to
>> be what you actually mean. This is why I'm trying to get an accurate
>> specification of what you *really* want. How can we agree if you're
>> not accurately stating what you want / plan to do?
>>
>>> and make it a module just like core
>>> is, so the release is coupled to the struts release and everything can
>>> be built easily
>>
>> Great. I have no problem with that. Now, why is 1a better than 1c, for
>> example? And what is the answer to 2? Neither of these are answered by
>> the statement that you want to be able to build easily.
>>
>> --
>> Martin Cooper
>>
>>
>>> musahcy
>>>
>>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>>
>>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>>> especially (c).
>>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>>> which of the options this is.
>>>> 3) Unclear. Maybe (b)?
>>>>
>>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>>> proposal and an explanation of why it's the right way to go.
>>>>
>>>> --
>>>> Martin Cooper
>>>>
>>>>
>>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>>> <lu...@googlemail.com> wrote:
>>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>>> emerge.
>>>>>>
>>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>>> release process (XWork will be released with Struts2 together) and
>>>>>> allow me to work with XWork and see at the same time what will happen
>>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>> --
>>>>>> Lukasz
>>>>>> Kapituła Javarsovia 2010
>>>>>> http://javarsovia.pl
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
yes I meant under struts2, sorry for the confusion
On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper <ma...@apache.org> wrote:
> On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
>
> http://svn.apache.org/repos/asf/struts/xwork/trunk/
>
> and S2 is here:
>
> http://svn.apache.org/repos/asf/struts/struts2/trunk/
>
> Since there is no 'struts/trunk', what you said above is unlikely to
> be what you actually mean. This is why I'm trying to get an accurate
> specification of what you *really* want. How can we agree if you're
> not accurately stating what you want / plan to do?
>
>> and make it a module just like core
>> is, so the release is coupled to the struts release and everything can
>> be built easily
>
> Great. I have no problem with that. Now, why is 1a better than 1c, for
> example? And what is the answer to 2? Neither of these are answered by
> the statement that you want to be able to build easily.
>
> --
> Martin Cooper
>
>
>> musahcy
>>
>> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>>
>>> 1) (a), although I'm interested in the advantages of this over (b) or
>>> especially (c).
>>> 2) Unspecified, since you're referring to 'xwork' but not defining
>>> which of the options this is.
>>> 3) Unclear. Maybe (b)?
>>>
>>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>>> proposal and an explanation of why it's the right way to go.
>>>
>>> --
>>> Martin Cooper
>>>
>>>
>>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>>> <lu...@googlemail.com> wrote:
>>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>>> emerge.
>>>>>
>>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>>> release process (XWork will be released with Struts2 together) and
>>>>> allow me to work with XWork and see at the same time what will happen
>>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>>
>>>>>
>>>>> Regards
>>>>> --
>>>>> Lukasz
>>>>> Kapituła Javarsovia 2010
>>>>> http://javarsovia.pl
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Fri, Jan 8, 2010 at 4:20 PM, Musachy Barroso <mu...@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 here:
http://svn.apache.org/repos/asf/struts/xwork/trunk/
and S2 is here:
http://svn.apache.org/repos/asf/struts/struts2/trunk/
Since there is no 'struts/trunk', what you said above is unlikely to
be what you actually mean. This is why I'm trying to get an accurate
specification of what you *really* want. How can we agree if you're
not accurately stating what you want / plan to do?
> and make it a module just like core
> is, so the release is coupled to the struts release and everything can
> be built easily
Great. I have no problem with that. Now, why is 1a better than 1c, for
example? And what is the answer to 2? Neither of these are answered by
the statement that you want to be able to build easily.
--
Martin Cooper
> musahcy
>
> On Fri, Jan 8, 2010 at 3:56 PM, Martin Cooper <ma...@apache.org> wrote:
>> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>>
>> 1) (a), although I'm interested in the advantages of this over (b) or
>> especially (c).
>> 2) Unspecified, since you're referring to 'xwork' but not defining
>> which of the options this is.
>> 3) Unclear. Maybe (b)?
>>
>> I'm not trying to be a pain, but I'm not seeing a clearly stated
>> proposal and an explanation of why it's the right way to go.
>>
>> --
>> Martin Cooper
>>
>>
>>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>>> <lu...@googlemail.com> wrote:
>>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>>> emerge.
>>>>
>>>> I'm not so good in Maven but I'm for anything that will simplify
>>>> release process (XWork will be released with Struts2 together) and
>>>> allow me to work with XWork and see at the same time what will happen
>>>> with Struts2 code base (eg. launching tests in IDEA).
>>>>
>>>>
>>>> Regards
>>>> --
>>>> Lukasz
>>>> Kapituła Javarsovia 2010
>>>> http://javarsovia.pl
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Fri, Jan 8, 2010 at 4:29 PM, Wendy Smoak <ws...@gmail.com> wrote:
> On Fri, Jan 8, 2010 at 5:20 PM, Musachy Barroso <mu...@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 easily
>
> I agree. Right now it is a pain to release xwork separately, so let's
> not do that.
That is probably the one piece of the puzzle that is clear and agreed
upon right now. :-)
--
Martin Cooper
> I would put xwork underneath struts2/trunk, so that it is a sibling of
> 'core'. Here: http://svn.apache.org/repos/asf/struts/struts2/trunk/
>
> This means you build (and release) struts and xwork all together.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Frans Thamura <fr...@meruvian.org>.
is it possible if we talk struts3, we put REST as default main feature,
outside new Apache Xwork
F
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Fri, Jan 8, 2010 at 5:40 PM, Wendy Smoak <ws...@gmail.com> wrote:
> On Fri, Jan 8, 2010 at 6:27 PM, Martin Cooper <ma...@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, S2. There are multiple ways of achieving that, the use of
>> externals being one of them.
>
> Externals are fine for convenience like 'trunks' or 'current' to check
> out several things together, but they will cause trouble when you try
> to tag a release. Since they are just properties on a directory, they
> don't magically get updated when you tag. Definitely not recommended,
> at least when releasing with Maven.
>
> The best way to do this is to have everything together in Subversion
> in a directory structure that matches the Maven parent-and-child
> module structure.
Good answer. :-) Thanks, Wendy.
--
Martin Cooper
> (That doesn't mean that it has to be like this forever though. If the
> mythical Struts 3 appears and xwork needs to be separate... then we
> move it.)
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Jan 8, 2010 at 6:27 PM, Martin Cooper <ma...@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, S2. There are multiple ways of achieving that, the use of
> externals being one of them.
Externals are fine for convenience like 'trunks' or 'current' to check
out several things together, but they will cause trouble when you try
to tag a release. Since they are just properties on a directory, they
don't magically get updated when you tag. Definitely not recommended,
at least when releasing with Maven.
The best way to do this is to have everything together in Subversion
in a directory structure that matches the Maven parent-and-child
module structure.
(That doesn't mean that it has to be like this forever though. If the
mythical Struts 3 appears and xwork needs to be separate... then we
move it.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Fri, Jan 8, 2010 at 5:11 PM, Paul Benedict <pb...@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 caveat is if XWork really is valuable and would make it
> good in a theoretical Struts 3, it could stay where it is and be
> released separately. But, as already stated by others, it would mean
> it's an extra build -- but also forever tied to struts 2.
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, S2. There are multiple ways of achieving that, the use of
externals being one of them.
--
Martin Cooper
> Paul
>
> On Fri, Jan 8, 2010 at 6:48 PM, Musachy Barroso <mu...@gmail.com> wrote:
>> 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 <ws...@gmail.com> wrote:
>>> On Fri, Jan 8, 2010 at 5:20 PM, Musachy Barroso <mu...@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 easily
>>>
>>> I agree. Right now it is a pain to release xwork separately, so let's
>>> not do that.
>>>
>>> I would put xwork underneath struts2/trunk, so that it is a sibling of
>>> 'core'. Here: http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>>
>>> This means you build (and release) struts and xwork all together.
>>>
>>> --
>>> Wendy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Paul Benedict <pb...@apache.org>.
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 3, it could stay where it is and be
released separately. But, as already stated by others, it would mean
it's an extra build -- but also forever tied to struts 2.
Paul
On Fri, Jan 8, 2010 at 6:48 PM, Musachy Barroso <mu...@gmail.com> wrote:
> 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 <ws...@gmail.com> wrote:
>> On Fri, Jan 8, 2010 at 5:20 PM, Musachy Barroso <mu...@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 easily
>>
>> I agree. Right now it is a pain to release xwork separately, so let's
>> not do that.
>>
>> I would put xwork underneath struts2/trunk, so that it is a sibling of
>> 'core'. Here: http://svn.apache.org/repos/asf/struts/struts2/trunk/
>>
>> This means you build (and release) struts and xwork all together.
>>
>> --
>> Wendy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
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 <ws...@gmail.com> wrote:
> On Fri, Jan 8, 2010 at 5:20 PM, Musachy Barroso <mu...@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 easily
>
> I agree. Right now it is a pain to release xwork separately, so let's
> not do that.
>
> I would put xwork underneath struts2/trunk, so that it is a sibling of
> 'core'. Here: http://svn.apache.org/repos/asf/struts/struts2/trunk/
>
> This means you build (and release) struts and xwork all together.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Jan 8, 2010 at 5:20 PM, Musachy Barroso <mu...@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 easily
I agree. Right now it is a pain to release xwork separately, so let's
not do that.
I would put xwork underneath struts2/trunk, so that it is a sibling of
'core'. Here: http://svn.apache.org/repos/asf/struts/struts2/trunk/
This means you build (and release) struts and xwork all together.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
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 <ma...@apache.org> wrote:
> On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
>
> 1) (a), although I'm interested in the advantages of this over (b) or
> especially (c).
> 2) Unspecified, since you're referring to 'xwork' but not defining
> which of the options this is.
> 3) Unclear. Maybe (b)?
>
> I'm not trying to be a pain, but I'm not seeing a clearly stated
> proposal and an explanation of why it's the right way to go.
>
> --
> Martin Cooper
>
>
>> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
>> <lu...@googlemail.com> wrote:
>>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>>> emerge.
>>>
>>> I'm not so good in Maven but I'm for anything that will simplify
>>> release process (XWork will be released with Struts2 together) and
>>> allow me to work with XWork and see at the same time what will happen
>>> with Struts2 code base (eg. launching tests in IDEA).
>>>
>>>
>>> Regards
>>> --
>>> Lukasz
>>> Kapituła Javarsovia 2010
>>> http://javarsovia.pl
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <mu...@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:
1) (a), although I'm interested in the advantages of this over (b) or
especially (c).
2) Unspecified, since you're referring to 'xwork' but not defining
which of the options this is.
3) Unclear. Maybe (b)?
I'm not trying to be a pain, but I'm not seeing a clearly stated
proposal and an explanation of why it's the right way to go.
--
Martin Cooper
> On Fri, Jan 8, 2010 at 3:53 AM, Lukasz Lenart
> <lu...@googlemail.com> wrote:
>> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>>> emerge.
>>
>> I'm not so good in Maven but I'm for anything that will simplify
>> release process (XWork will be released with Struts2 together) and
>> allow me to work with XWork and see at the same time what will happen
>> with Struts2 code base (eg. launching tests in IDEA).
>>
>>
>> Regards
>> --
>> Lukasz
>> Kapituła Javarsovia 2010
>> http://javarsovia.pl
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: XWork has landed!
Posted by Martin Gainty <mg...@hotmail.com>.
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 unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Fri, 8 Jan 2010 11:54:46 -0800
> Subject: Re: XWork has landed!
> From: musachy@gmail.com
> To: dev@struts.apache.org
>
> 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
> <lu...@googlemail.com> wrote:
> > 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
> >>> emerge.
> >
> > I'm not so good in Maven but I'm for anything that will simplify
> > release process (XWork will be released with Struts2 together) and
> > allow me to work with XWork and see at the same time what will happen
> > with Struts2 code base (eg. launching tests in IDEA).
> >
> >
> > Regards
> > --
> > Lukasz
> > Kapituła Javarsovia 2010
> > http://javarsovia.pl
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/196390709/direct/01/
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
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
<lu...@googlemail.com> wrote:
> 2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>>> emerge.
>
> I'm not so good in Maven but I'm for anything that will simplify
> release process (XWork will be released with Struts2 together) and
> allow me to work with XWork and see at the same time what will happen
> with Struts2 code base (eg. launching tests in IDEA).
>
>
> Regards
> --
> Lukasz
> Kapituła Javarsovia 2010
> http://javarsovia.pl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Lukasz Lenart <lu...@googlemail.com>.
2010/1/6 Musachy Barroso <mu...@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 sure I saw a consensus
>> emerge.
I'm not so good in Maven but I'm for anything that will simplify
release process (XWork will be released with Struts2 together) and
allow me to work with XWork and see at the same time what will happen
with Struts2 code base (eg. launching tests in IDEA).
Regards
--
Lukasz
Kapituła Javarsovia 2010
http://javarsovia.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
hum, that's what i understood mot people wanted from our original
discussion and the last time we talked about this. It keeps xwork
independent (well sort of) and it will be part of the same release
process.
On Wed, Jan 6, 2010 at 10:11 AM, Martin Cooper <ma...@apache.org> wrote:
> On Wed, Jan 6, 2010 at 9:27 AM, Musachy Barroso <mu...@gmail.com> wrote:
>> I think the agreement is to move it under the struts trunk and make it
>> a maven module, like core.
>
> 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 sure I saw a consensus
> emerge.
>
> --
> Martin Cooper
>
>
>> musachy
>>
>> On Tue, Jan 5, 2010 at 11:37 PM, Lukasz Lenart
>> <lu...@googlemail.com> wrote:
>>> 2009/12/28 Paul Benedict <pb...@apache.org>:
>>>> My fault for not being clear. I was intending to say XWork should be a
>>>> "child module" (in the Maven sense) so it's actually part of Struts2
>>>> build and versioning process.
>>>
>>> Any news? I would like to start some refactoring in Xwork and it will
>>> be nice to know where we are ;-)
>>>
>>>
>>> Regards
>>> --
>>> Lukasz
>>> http://www.lenart.org.pl/
>>> http://javarsovia.pl
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Martin Cooper <ma...@apache.org>.
On Wed, Jan 6, 2010 at 9:27 AM, Musachy Barroso <mu...@gmail.com> wrote:
> I think the agreement is to move it under the struts trunk and make it
> a maven module, like core.
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 sure I saw a consensus
emerge.
--
Martin Cooper
> musachy
>
> On Tue, Jan 5, 2010 at 11:37 PM, Lukasz Lenart
> <lu...@googlemail.com> wrote:
>> 2009/12/28 Paul Benedict <pb...@apache.org>:
>>> My fault for not being clear. I was intending to say XWork should be a
>>> "child module" (in the Maven sense) so it's actually part of Struts2
>>> build and versioning process.
>>
>> Any news? I would like to start some refactoring in Xwork and it will
>> be nice to know where we are ;-)
>>
>>
>> Regards
>> --
>> Lukasz
>> http://www.lenart.org.pl/
>> http://javarsovia.pl
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: XWork has landed!
Posted by Musachy Barroso <mu...@gmail.com>.
I think the agreement is to move it under the struts trunk and make it
a maven module, like core.
musachy
On Tue, Jan 5, 2010 at 11:37 PM, Lukasz Lenart
<lu...@googlemail.com> wrote:
> 2009/12/28 Paul Benedict <pb...@apache.org>:
>> My fault for not being clear. I was intending to say XWork should be a
>> "child module" (in the Maven sense) so it's actually part of Struts2
>> build and versioning process.
>
> Any news? I would like to start some refactoring in Xwork and it will
> be nice to know where we are ;-)
>
>
> Regards
> --
> Lukasz
> http://www.lenart.org.pl/
> http://javarsovia.pl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org