I changed things to use the webXml tag a while ago. I did this
because I was getting very confused when the authentication filters
were running twice per-request. Obviously I was reading old
documentation...
A simple solution is to do away with the web.full.xml,
web.gadgets.xml, etc.
Is anyone actually using these for anything? The only usage I see is
setting runType to differing values in the top level pom?
On Jan 22, 2009, at 2:24 PM, Citron, David wrote:
Perhaps due to changes in the "jetty:run-war" goal of the
maven-jetty-plugin, the usage in shindig/pom.xml is no longer correct.
We have:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<tempDirectory>${basedir}/java/server/target/work</tempDirectory>
<webApp>${basedir}/java/server/target/shindig-server-$
{pom.version}.war<
/webApp>
<contextPath>/</contextPath>
<webXml>${basedir}/java/server/target/shindig-server-${pom.version}/
WEB-
INF/web.${runType}.xml</webXml>
</configuration>
</plugin>
However, in the current version of "jetty:run-war" as documented
here --
http://jetty.mortbay.org/jetty/maven-plugin/run-war-mojo.html -- and
verified by my testing,
1) <tempDirectory> should be replaced with <tmpDirectory>
2) <webXml> is not a valid parameter and is ignored
(Number 2 caused us quite a bit of debugging time).
For number 1, it's pretty clear how to fix the problem :-)
For number 2, however, the solution could be trickier. The closest
thing
that the plugin seems to support is <overrideWebXml>, the use of which
would require a bit of refactoring of our various web*.xml files
into a
base web.xml and various add-ons. For now, the plugin is always simply
using web.xml.
Anyone else encounter this?
Thanks,
Dave
