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 <[email protected]> wrote: > On Fri, Jan 8, 2010 at 11:54 AM, Musachy Barroso <[email protected]> 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 >> <[email protected]> wrote: >>> 2010/1/6 Musachy Barroso <[email protected]>: >>>>> 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: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
