[ https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3948: --------------------------------------- The cli scripts are already in charge of doing the war deployments and a modification to override the web.xml would be a copy/paste exercise (or just commented out in the cli script file). Can you elaborate on that? Do you mean that it's better to have a self contained artifact? We should separate that from this issue. Having a completely separate odata offering is appealing, but is a lot of work. As you say the simplest initial cut would be to incorporate Teiid embedded in the war. You mean if you rely on embedded and have a separate kitting option for EAP/AS. It still seems heavy weight for users to then do a git checkout, modification, and maven build to just update properties in the web.xml. I'm fine if you want to produce the war from a separate project, but to just override the web.xml it seems like there is a perfectly valid eap mechanism to do that already. For all other containers/scenarios you'll need a separate build anyway as you'll need to incorporate embedded and not rely on modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)