Another scenario I recently experimented with came up when I was
thinking about a feasible process to enable a local CI infrastructure
for experimental changes on the s2 codebase. While we have our central
CI builds set up, they only make sense for features which are targeted
for immidiate impr
Andreas,
I agree that this is a very interesting finding and a useful scenario.
Nevertheless, I see two downsides of changing the default interceptor
order as you suggested:
1) (minor) the request_locale parameter will not be removed from the
request before params are applied, which might lead
Being able to quickly create git repos of the Subversion projects is
exactly what these are for. See this:
http://wiki.apache.org/general/GitAtApache
Don
On Wed, May 6, 2009 at 7:48 PM, Rene Gielen wrote:
> Another scenario I recently experimented with came up when I was thinking
> about a feas
great pointer, thanks Don
Don Brown schrieb:
Being able to quickly create git repos of the Subversion projects is
exactly what these are for. See this:
http://wiki.apache.org/general/GitAtApache
Don
On Wed, May 6, 2009 at 7:48 PM, Rene Gielen wrote:
Another scenario I recently experimented
Rainer,
I was just fiddling around in my own copy of the source and it looks
like you are breaking down the xwork build into multiple artifacts. I
like it, but it seems like the struts build gets broken by this... I
think I only noticed because I just blew away my .m2/repository (I'm
fiddling arou
Wes,
yes, we now have multiple artifacts in XWork. The former xwork-VERSION.jar
file
has been renamed to xwork-core-VERSION.jar.
Maybe this simple change would fix the break, I'll have a look at this
later today.
So, I think changeing the struts pom.xml should solve the problem.
later,
Rainer
>
On Wed, May 6, 2009 at 12:11 PM, Rainer Hermanns wrote:
> Wes,
>
> yes, we now have multiple artifacts in XWork. The former xwork-VERSION.jar
> file
> has been renamed to xwork-core-VERSION.jar.
> Maybe this simple change would fix the break, I'll have a look at this
> later today.
> So, I think c
2009/5/6 Wes Wannemacher :
> That doesn't seem like enough. I updated poms to use xwork-core and it
> seems like some of the classes that were shaded before are now gone.
> The only poms that point to xwork are the core and assembly pom. Here
> is what I'm getting when I try to compile by pointing
2009/5/6 Lukasz Lenart :
> 2009/5/6 Wes Wannemacher :
>> That doesn't seem like enough. I updated poms to use xwork-core and it
>> seems like some of the classes that were shaded before are now gone.
>> The only poms that point to xwork are the core and assembly pom. Here
>> is what I'm getting whe
