Well actually you don't NEED to have the context.xml in a webapp, WEB-INF is required but META-INF/context.xml is not required (perhaps maven assumes that it's required, but that is a different argument).
Is there an override param/element to have it excluded? Or am I screwed in this scenario? Is there NO way to do it? Also what do you mean by: "context.xml is defined by a configuration paramater" On 4/24/08 11:39 AM, "Jörg Schaible" <[EMAIL PROTECTED]> wrote: > Alessandro Ferrucci wrote: >> I'm just bumping this email back up the listserv stack to see if >> anyone knows how I can do this :) >> >> thanks >> >> Alessandro Ferrucci >> >> >> Alessandro Ferrucci wrote: >>> hey guys >>> >>> I'm trying to exclude a context.xml from a webapp. I have the >>> following snippet in my build element: >>> >>> <resources> >>> <resource> >>> <directory>src/main/resources</directory> >>> <excludes> >>> <exclude>**/application.jmx.properties</exclude> >>> <exclude>**/log4j.properties</exclude> >>> </excludes> </resource> <resource> >>> <directory>src/main/java/webapp/META-INF</directory> >>> <excludes> <exclude>**/context.xml</exclude> >>> </excludes> </resource> >>> </resources> >>> >>> >>> my directory structure over context.xml looks like this: >>> >>> >>> src/main/java/webapp/META-INF/context.xml >>> >>> context.xml is still not being excluded, but >>> application.jmx.properties and log4j.properties are, anyone know >>> what gives? > > You *need* a context.xml for a web app and the context.xml is defined by a > configuration parameter. Therefore exclusions don't apply here :) > > - Jörg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
