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

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163737#comment-13163737 ] 

Steven Hawkins commented on TEIID-3948:
---------------------------------------

> teaching one to do the CLI scripts

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).

> migration issues

Can you elaborate on that?  Do you mean that it's better to have a self contained artifact?

> 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)

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.

> if we go this route, then we can bring all these together under single repo, possibly with no duplicates.

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.


> Provide a different mechanism to update odata wars
> --------------------------------------------------
>
>                 Key: TEIID-3948
>                 URL: https://issues.jboss.org/browse/TEIID-3948
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Server
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 9.0, 8.12.5
>
>
> Directly modifying the wars under the base modules is a bad practice.  We need to have users modify non-kit artifact files in a different location.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)