Re: XWork has landed!
On Mon, Jan 18, 2010 at 9:24 AM, Musachy Barroso musa...@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 w...@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 musa...@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 mart...@apache.org wrote: On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso musa...@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 musa...@gmail.com wrote: yes I meant under struts2, sorry for the confusion On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper mart...@apache.org wrote: 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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 w...@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 musa...@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 mart...@apache.org wrote: On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso musa...@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 musa...@gmail.com wrote: yes I meant under struts2, sorry for the confusion On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper mart...@apache.org wrote: 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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail:
Re: XWork has landed!
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 musa...@gmail.com wrote: yes I meant under struts2, sorry for the confusion On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper mart...@apache.org wrote: 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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 mart...@apache.org wrote: On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso musa...@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 musa...@gmail.com wrote: yes I meant under struts2, sorry for the confusion On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper mart...@apache.org wrote: 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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail:
Re: XWork has landed!
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 musa...@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 mart...@apache.org wrote: On Fri, Jan 15, 2010 at 10:23 AM, Musachy Barroso musa...@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 musa...@gmail.com wrote: yes I meant under struts2, sorry for the confusion On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper mart...@apache.org wrote: 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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail:
Re: XWork has landed!
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 musa...@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 musa...@gmail.com wrote: yes I meant under struts2, sorry for the confusion On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper mart...@apache.org wrote: 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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
yes I meant under struts2, sorry for the confusion On Fri, Jan 8, 2010 at 5:22 PM, Martin Cooper mart...@apache.org wrote: 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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
RE: XWork has landed!
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: musa...@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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@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!
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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 musa...@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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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 mart...@apache.org wrote: 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: 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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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 musa...@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 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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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, 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
is it possible if we talk struts3, we put REST as default main feature, outside new Apache Xwork F
Re: XWork has landed!
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 lukasz.len...@googlemail.com wrote: 2009/12/28 Paul Benedict pbened...@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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
On Wed, Jan 6, 2010 at 9:27 AM, Musachy Barroso musa...@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 lukasz.len...@googlemail.com wrote: 2009/12/28 Paul Benedict pbened...@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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
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 mart...@apache.org wrote: On Wed, Jan 6, 2010 at 9:27 AM, Musachy Barroso musa...@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 lukasz.len...@googlemail.com wrote: 2009/12/28 Paul Benedict pbened...@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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
2009/12/28 Paul Benedict pbened...@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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
Great News! Thanks Martin Happy Holidays, René Martin Cooper schrieb: As many of you have no doubt noticed already, I've checked in the XWork code base, and added the Apache License 2.0 headers. The new XWork tree is here: http://svn.apache.org/repos/asf/struts/xwork/ I have *not* added it to 'current' at this point. I'll leave that to whoever wants to integrate it further. -- Martin Cooper - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- René Gielen IT-Neering.net Saarstrasse 100, 52062 Aachen, Germany Tel: +49-(0)241-4010770 Fax: +49-(0)241-4010771 Cel: +49-(0)177-3194448 http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
Are we going to rename the maven artifact names and package names for 2.2? musachy On Sun, Dec 27, 2009 at 12:39 PM, Martin Cooper mart...@apache.org wrote: On Sun, Dec 27, 2009 at 12:30 PM, Paul Benedict pbened...@apache.org wrote: I recommend we immediately SVN tag or branch the initial check in so it can be refactored appropriately. I'm not sure I see a need to do that, given that we can create a tag or branch from a specific revision at any time. However, if you feel the need, you're welcome to do that. -- Martin Cooper Paul On Sun, Dec 27, 2009 at 1:18 PM, Lukasz Lenart lukasz.len...@googlemail.com wrote: 2009/12/27 Martin Cooper mart...@apache.org: As many of you have no doubt noticed already, I've checked in the XWork code base, and added the Apache License 2.0 headers. The new XWork tree is here: Hurra!!! Thanks a lot! Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
If no one objects, i can take a stab at taking care of this tonight... I haven't looked much at Martin's check-in, but we only need to port the xwork-core artifact... So, my plan would be to copy the source to the struts2 folder as a first-class sub-project (adding it to the modules section of the struts2 parent pom). Then, if that build works out, the next check-ins can be renaming / refactoring of classes, etc. But, if xwork-core is placed in the struts2 folder, alongside struts2-core, struts2-plugins, etc., then, if nothing else, it will make releasing easier. I'd imagine that refactoring class and package names will be a bit troublesome. Although the IDE can handle most of it for us, the trick isn't the easy stuff, the trick is finding the classes that are no longer necessary and/or duplicated between codebases. Thoughts? -Wes On Mon, Dec 28, 2009 at 1:16 PM, Musachy Barroso musa...@gmail.com wrote: Are we going to rename the maven artifact names and package names for 2.2? musachy On Sun, Dec 27, 2009 at 12:39 PM, Martin Cooper mart...@apache.org wrote: On Sun, Dec 27, 2009 at 12:30 PM, Paul Benedict pbened...@apache.org wrote: I recommend we immediately SVN tag or branch the initial check in so it can be refactored appropriately. I'm not sure I see a need to do that, given that we can create a tag or branch from a specific revision at any time. However, if you feel the need, you're welcome to do that. -- Martin Cooper Paul On Sun, Dec 27, 2009 at 1:18 PM, Lukasz Lenart lukasz.len...@googlemail.com wrote: 2009/12/27 Martin Cooper mart...@apache.org: As many of you have no doubt noticed already, I've checked in the XWork code base, and added the Apache License 2.0 headers. The new XWork tree is here: Hurra!!! Thanks a lot! Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
On Mon, Dec 28, 2009 at 10:29 AM, Wes Wannemacher w...@wantii.com wrote: If no one objects, i can take a stab at taking care of this tonight... I guess I sort of object, unless I'm the only one without a full and clear picture of the fate of this new code base that we own. I think we need to make sure we're all on the same page before we start making changes. I haven't looked much at Martin's check-in, but we only need to port the xwork-core artifact... So, my plan would be to copy the source to the struts2 folder as a first-class sub-project (adding it to the modules section of the struts2 parent pom). Then, if that build works out, the next check-ins can be renaming / refactoring of classes, etc. But, if xwork-core is placed in the struts2 folder, alongside struts2-core, struts2-plugins, etc., then, if nothing else, it will make releasing easier. I'd imagine that refactoring class and package names will be a bit troublesome. Although the IDE can handle most of it for us, the trick isn't the easy stuff, the trick is finding the classes that are no longer necessary and/or duplicated between codebases. Thoughts? What I checked in is the entire XWork repo, since XWork is now our responsibility. That is, we don't have a copy of XWork that we're maintaining, we own XWork now. We have adopted it, lock, stock and barrel. If people need enhancements to XWork, they will come to us from now on. (What we do with such requests is something we should discuss at some point in the near future.) I was envisaging that we would add XWork to the 'current' external in such a way that it would look exactly the same as it does today when someone checks it out as a peer of the 'struts2' folder. I take it this is not what you have in mind? I have to say that 'copy' is not a word I like to see in reference to source control. ;-) It implies a forking of the code base that we would need to be very sure about. Is that actually what you mean? -- Martin Cooper -Wes On Mon, Dec 28, 2009 at 1:16 PM, Musachy Barroso musa...@gmail.com wrote: Are we going to rename the maven artifact names and package names for 2.2? musachy On Sun, Dec 27, 2009 at 12:39 PM, Martin Cooper mart...@apache.org wrote: On Sun, Dec 27, 2009 at 12:30 PM, Paul Benedict pbened...@apache.org wrote: I recommend we immediately SVN tag or branch the initial check in so it can be refactored appropriately. I'm not sure I see a need to do that, given that we can create a tag or branch from a specific revision at any time. However, if you feel the need, you're welcome to do that. -- Martin Cooper Paul On Sun, Dec 27, 2009 at 1:18 PM, Lukasz Lenart lukasz.len...@googlemail.com wrote: 2009/12/27 Martin Cooper mart...@apache.org: As many of you have no doubt noticed already, I've checked in the XWork code base, and added the Apache License 2.0 headers. The new XWork tree is here: Hurra!!! Thanks a lot! Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
I am ok with moving it to under struts as a module, to make it part of the release, so we don't have to release it (and vote!) as a separate artifact. On Mon, Dec 28, 2009 at 10:57 AM, Martin Cooper mart...@apache.org wrote: On Mon, Dec 28, 2009 at 10:29 AM, Wes Wannemacher w...@wantii.com wrote: If no one objects, i can take a stab at taking care of this tonight... I guess I sort of object, unless I'm the only one without a full and clear picture of the fate of this new code base that we own. I think we need to make sure we're all on the same page before we start making changes. I haven't looked much at Martin's check-in, but we only need to port the xwork-core artifact... So, my plan would be to copy the source to the struts2 folder as a first-class sub-project (adding it to the modules section of the struts2 parent pom). Then, if that build works out, the next check-ins can be renaming / refactoring of classes, etc. But, if xwork-core is placed in the struts2 folder, alongside struts2-core, struts2-plugins, etc., then, if nothing else, it will make releasing easier. I'd imagine that refactoring class and package names will be a bit troublesome. Although the IDE can handle most of it for us, the trick isn't the easy stuff, the trick is finding the classes that are no longer necessary and/or duplicated between codebases. Thoughts? What I checked in is the entire XWork repo, since XWork is now our responsibility. That is, we don't have a copy of XWork that we're maintaining, we own XWork now. We have adopted it, lock, stock and barrel. If people need enhancements to XWork, they will come to us from now on. (What we do with such requests is something we should discuss at some point in the near future.) I was envisaging that we would add XWork to the 'current' external in such a way that it would look exactly the same as it does today when someone checks it out as a peer of the 'struts2' folder. I take it this is not what you have in mind? I have to say that 'copy' is not a word I like to see in reference to source control. ;-) It implies a forking of the code base that we would need to be very sure about. Is that actually what you mean? -- Martin Cooper -Wes On Mon, Dec 28, 2009 at 1:16 PM, Musachy Barroso musa...@gmail.com wrote: Are we going to rename the maven artifact names and package names for 2.2? musachy On Sun, Dec 27, 2009 at 12:39 PM, Martin Cooper mart...@apache.org wrote: On Sun, Dec 27, 2009 at 12:30 PM, Paul Benedict pbened...@apache.org wrote: I recommend we immediately SVN tag or branch the initial check in so it can be refactored appropriately. I'm not sure I see a need to do that, given that we can create a tag or branch from a specific revision at any time. However, if you feel the need, you're welcome to do that. -- Martin Cooper Paul On Sun, Dec 27, 2009 at 1:18 PM, Lukasz Lenart lukasz.len...@googlemail.com wrote: 2009/12/27 Martin Cooper mart...@apache.org: As many of you have no doubt noticed already, I've checked in the XWork code base, and added the Apache License 2.0 headers. The new XWork tree is here: Hurra!!! Thanks a lot! Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@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-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
I thought we had reached consensus on this back in August: http://old.nabble.com/Re%3A-Let%27s-kill-xwork-%28was-Re%3A-2.1.8-release-%29-p24966742.html -Dale - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
Having XWork as a separate module is actually preferred, but only because it's a better design decision. It will create a clear separation of concerns within the code base. Now with that said, XWork should be a *child* module of Struts -- not a separate release. Paul - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
On Mon, Dec 28, 2009 at 2:16 PM, Paul Benedict pbened...@apache.org wrote: Having XWork as a separate module is actually preferred, but only because it's a better design decision. It will create a clear separation of concerns within the code base. Now with that said, XWork should be a *child* module of Struts -- not a separate release. Paul When you (and Martin) are indicating a child of Struts, I assume you mean for it to be a child outside of Struts2. I am a team player and I'm willing to set it up, whatever the consensus, but I would really prefer for it to be a child of Struts2. I understand the implications of supporting it, etc. But, the biggest gripe (and *my* motivation for voting to move it over) is that we often wait to release Struts2 because we need a release of XWork. Not to knock Rainer, but sometimes this process takes a while. If it is a part of the Struts2 umbrella, then the release process outlined in the wiki will still apply, but everything (including xwork artifacts) will go out at once. Plus, one of my tasks for Struts 2.2 is to take advantage of maven's dependencyManagement and pluginManagement. We could probably work that into the struts-master, but I hate to push changes to Struts 1, since I don't use it much. I would just like to balance making our lives easier against other factors. In the end, if we make managing this beast easier we can move on things faster. I know that fast isn't necessarily a goal, but I'd still like to try to get to KISS so that potential patch-makers aren't so intimidated by our code and build process. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
On Mon, Dec 28, 2009 at 11:37 AM, Wes Wannemacher w...@wantii.com wrote: On Mon, Dec 28, 2009 at 2:16 PM, Paul Benedict pbened...@apache.org wrote: Having XWork as a separate module is actually preferred, but only because it's a better design decision. It will create a clear separation of concerns within the code base. Now with that said, XWork should be a *child* module of Struts -- not a separate release. Paul When you (and Martin) are indicating a child of Struts, I assume you mean for it to be a child outside of Struts2. I am a team player and I'm willing to set it up, whatever the consensus, but I would really prefer for it to be a child of Struts2. I understand the implications of supporting it, etc. But, the biggest gripe (and *my* motivation for voting to move it over) is that we often wait to release Struts2 because we need a release of XWork. Not to knock Rainer, but sometimes this process takes a while. If it is a part of the Struts2 umbrella, then the release process outlined in the wiki will still apply, but everything (including xwork artifacts) will go out at once. Plus, one of my tasks for Struts 2.2 is to take advantage of maven's dependencyManagement and pluginManagement. We could probably work that into the struts-master, but I hate to push changes to Struts 1, since I don't use it much. I would just like to balance making our lives easier against other factors. In the end, if we make managing this beast easier we can move on things faster. I know that fast isn't necessarily a goal, but I'd still like to try to get to KISS so that potential patch-makers aren't so intimidated by our code and build process. Where XWork lands up in the Struts repo, and how it gets built, have zero bearing on how it gets released (except if we see ourselves releasing it independently, which I did not think was the case). As I see it, we have a set of choices to make 1) (a) move, (b) copy, (c) create an 'external' reference for 2) (a) all of XWork, (b) just the XWork core, (c) some other subset of XWork 3) (a) to a peer of 'struts2', (b) to somewhere within 'struts2', (c) to somewhere else I believe 1c + 2a + 3a = what we have today except that it's one checkout instead of two. With that option, nothing about the build or the build documentation changes, AFAICT. Is that what we want? I don't know, I'm just suggesting that it's a low-cost way of moving forward now that the code is in our repo. I don't have a particular bias in regard to how we go about this, beyond some source control best practices. I just think we need to make sure we're all on the same page about where we want to end up. -- Martin Cooper -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
RE: XWork has landed!
-Original Message- From: Martin Cooper Sent: Monday, December 28, 2009 15:10 To: Struts Developers List Subject: Re: XWork has landed! On Mon, Dec 28, 2009 at 11:37 AM, Wes Wannemacher w...@wantii.com wrote: On Mon, Dec 28, 2009 at 2:16 PM, Paul Benedict pbened...@apache.org wrote: Having XWork as a separate module is actually preferred, but only because it's a better design decision. It will create a clear snip/ As I see it, we have a set of choices to make 1) (a) move, (b) copy, (c) create an 'external' reference for 2) (a) all of XWork, (b) just the XWork core, (c) some other subset of XWork 3) (a) to a peer of 'struts2', (b) to somewhere within 'struts2', (c) to somewhere else I believe 1c + 2a + 3a = what we have today except that it's one checkout instead of two. With that option, nothing about the build or the build documentation changes, AFAICT. Is that what we want? I don't know, I'm just suggesting that it's a low-cost way of moving forward now that the code is in our repo. I don't have a particular bias in regard to how we go about this, beyond some source control best practices. I just think we need to make sure we're all on the same page about where we want to end up. I think it would be best to have in the same source control repository, but keep it as separate as possible. We use the following tree here: /repoPerProjectGroup ./trunk ../subproject1 ../subproject2 ../subproject3 ./branches ./common ./private ./releases ./tmp Allowing subprojects to be freely independent and dependent at the same time. -Jason -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
On Mon, Dec 28, 2009 at 1:37 PM, Wes Wannemacher w...@wantii.com wrote: On Mon, Dec 28, 2009 at 2:16 PM, Paul Benedict pbened...@apache.org wrote: Having XWork as a separate module is actually preferred, but only because it's a better design decision. It will create a clear separation of concerns within the code base. Now with that said, XWork should be a *child* module of Struts -- not a separate release. 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. Paul - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
woot! thanks Martin and Rene for getting this done. musachy On Sun, Dec 27, 2009 at 10:25 AM, Martin Cooper mart...@apache.org wrote: As many of you have no doubt noticed already, I've checked in the XWork code base, and added the Apache License 2.0 headers. The new XWork tree is here: http://svn.apache.org/repos/asf/struts/xwork/ I have *not* added it to 'current' at this point. I'll leave that to whoever wants to integrate it further. -- Martin Cooper - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: XWork has landed!
2009/12/27 Martin Cooper mart...@apache.org: As many of you have no doubt noticed already, I've checked in the XWork code base, and added the Apache License 2.0 headers. The new XWork tree is here: Hurra!!! Thanks a lot! Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
