==> migrates only java sources (not jsp's)
props.setProperty( "log4j.appender.outlog", "org.apache.log4j.ConsoleAppender" );
props.setProperty( "log4j.appender.outlog.layout", "org.apache.log4j.PatternLayout" );
props.setProperty( "jspwiki.useLucene", "false" );
props.setProperty( "log4j.rootCategory", "INFO,outlog" );
SEVERE: Exception starting filter WikiJSPFilter java.lang.NoClassDefFoundError: org/apache/log4j/Logger at org.goodjava.plugin.hitcounter.HitCounter.<clinit>(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186)
Initially we assumed that JSPWiki did not run "out of the box" on WebSphere. Well, this is not true anymore for WebSphere 6.1 upwards.
Up until WebSphere 6.0 the commons-logging-api.jar is shipped by default in the WebSphere lib directory, which is the root cause of the problem. For full details , see http://www-01.ibm.com/support/docview.wss?uid=swg27004610&aid=1
I just tested this morning a standard (log4j based) JSPWiki on WebSphere 6.1, and it runs fine without special tweaks to either JSPWiki or WebSphere (after pointing the pages and attachments directory to /tmp)