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 to do with the ticket in the first place.
Any objections? John On 2/14/11 7:27 AM, "Maurizio Cucchiara" <maurizio.cucchi...@gmail.com> wrote: On 14 February 2011 16:11, John Lindal <lind...@yahoo-inc.com> 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 since you have corrected the shade configuration, maven starts to copy FileUtils.class along the path org.apache.commons.io.xwork. I think that the NoClassDefFoundError is a side effect of the current path of FileUtils class (the class loader was trying to find the error class out in the current path). > 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 trunk. Please, let me know. -- Maurizio Cucchiara --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
