Jörg Schaible wrote: > > > Can't you simply exclude the web.xml from the overlay? > > <plugin> > <artifactId>maven-war-plugin</artifactId> > <configuration> > <dependentWarExcludes>WEB-INF/web.xml</dependentWarExcludes> > </configuration> > </plugin> > > - Jörg > >
Hi Jörg - Thanks for the suggestion. I tried it but got the same result. What I want the plugin to do is use the web.xml file generated by jspc, which is what this configuration tries to do: <artifactId>maven-war-plugin</artifactId> <configuration> <webXml>${basedir}/target/jspweb.xml</webXml> </configuration> I found that this works fine if I'm just doing the precompile and the war packaging -- the jspc-generated jspweb.xml file gets used as the web.xml in the packaged war. But when I add the additional declaration to the pom to run the war:exploded goal during the process-resources phase, the final packaging uses the web.xml from the src/main/webapp tree instead. Any idea why the above configuration works in the first case but not in the second? George -- View this message in context: http://www.nabble.com/jsp-precompile-with-war-overlay-tf3187860s177.html#a8867524 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]