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: dev-h...@struts.apache.org
