I get the same results that you get. So it seems the correct solution is to
remove org.apache.commons.io.xwork completely. When I do this, it also works
just fine. In fact, it appears that we can remove both
org.apache.commons.io.xwork and the objectweb shading - which is what I was
planning
Sorry to keep coming back to this guys, but I'm still mulling over this...
If any of you get the chance, can you look over StrutsPrepareFilter,
InitOperations, PrepareOperations and StrutsExecuteFilter and tell me
that a single Dispatcher instance isn't simply shared across all of a
web-app's life
On 14 February 2011 16:11, John Lindal wrote:
> Try locally reverting the change to xwork-core/pom.xml in ticket XW-388 and
> see if it helps.
Sure that it helps, if I rollback to the previous version (the one
with the commons.lang typo) everything works like a charm.
As far as I can understand s
Try locally reverting the change to xwork-core/pom.xml in ticket XW-388 and see
if it helps.
I'll investigate on my end, too. The strange thing is that the
maven-shade-plugin configuration doesn't mention FileExistsException, and I
can't find any references to "org.apache.commons.io.xwork" in
Hi!
During the weekend I spent some time getting the embedded environment
updated to Pluto 2.0.2. So now it should be possible to use it with
JSR286 portlets.
Nils-H
On Thu, Jan 27, 2011 at 10:27 AM, Rene Gielen wrote:
> Hey Nils,
>
> thanks for jumping in! Good to have this on Github so we cou
