Hello again, Sergiu provided a Maven eclipse:eclipse command line to use, and it reminded me that I have so far ignored the issue of Maven profiles. When I built from the command line I didn't specify any profiles, and I'm guessing that defaulted to hsqldb,jetty (among other profiles). My real target is pgsql and Tomcat. So I should probably rebuild with -Pci,integration-tests,legacy,pgsql. For Tomcat deployment, all I really want is a WAR file. I'm guessing I'm going to have to include the jetty profile as well, even though I'm not targeting Jetty. xwiki-enterpirse-jetty pulls in needed generic web stuff and the only other way to get that would be to use the glassfish profile. There is no Tomcat profile. From what I see in the POMs, the only downside of specifying the jetty profile when Tomcat is being targeted is that it will pull in xwiki-platform-tool-jetty-resources, which will package up a complete Jetty runtime that I can then ignore. OTOH, maybe I should take the path of least resistance and use Jetty instead of Tomcat for the time being. Do I have this right? --Gary