[teiid-issues] [JBoss JIRA] (TEIID-3948) Provide a different mechanism to update odata wars

[ https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3948: ------------------------------------- The concern with that for me is two fold. - teaching one to do the CLI scripts - migration issues I much rather have this self-contained, so that we do not need to handle above. The down side is, we will be maintaining the web.xml in two separate projects, which are copies. I am already doing that for different security profiles. Ideally I want to move the whole "odata" project into separate repo and pull into kit during the kitting time. The desire is two fold again - Have this separate from main line Teiid code (not sure much benefit, I also was thinking to move away from query.lang classes as we talked before) - I want build WAR files based on the Teiid Embedded. This is so that it will be a drop in odata access to any data source. if we go this route, then we can bring all these together under single repo, possibly with no duplicates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)