falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pragya Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1550) Bundle deploy.properties for server while packaging falcon in distributed mode
Date Mon, 19 Oct 2015 12:50:05 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pragya Mittal updated FALCON-1550:
----------------------------------
    Description: 
Currently, when falcon is deployed in distributed mode deploy.properties is packaged internally
in prism.war only.

{noformat}
pragya@8RPCG32:~/WORKSPACE/trial-falcon/prism/server/webapp/prism/WEB-INF/classes$ ls
builddef.lst  deploy.properties  falcon-buildinfo.properties  log4j.xml  META-INF  org
{noformat}

Server uses falcon-prism-(falcon.version)-classes.jar to access these properties. It does
not bundle deploy.properties explicitly in its war.
{noformat}
pragya@8RPCG32:~/WORKSPACE/trial-falcon/server/server/webapp/falcon/WEB-INF/classes$ ls
client.properties  falcon-buildinfo.properties  log4j.xml  META-INF  org

pragya@8RPCG32:~/WORKSPACE/trial-falcon/server/server/webapp/falcon/WEB-INF/lib$ ls | grep
prism
falcon-prism-0.8-SNAPSHOT-classes.jar
{noformat}

Although, I feel this is a hackaround and we should bundle falcon.war with its own deploy.properties.

> Bundle deploy.properties for server while packaging falcon in distributed mode
> ------------------------------------------------------------------------------
>
>                 Key: FALCON-1550
>                 URL: https://issues.apache.org/jira/browse/FALCON-1550
>             Project: Falcon
>          Issue Type: Improvement
>    Affects Versions: trunk
>         Environment: QA
>            Reporter: Pragya Mittal
>
> Currently, when falcon is deployed in distributed mode deploy.properties is packaged
internally in prism.war only.
> {noformat}
> pragya@8RPCG32:~/WORKSPACE/trial-falcon/prism/server/webapp/prism/WEB-INF/classes$ ls
> builddef.lst  deploy.properties  falcon-buildinfo.properties  log4j.xml  META-INF  org
> {noformat}
> Server uses falcon-prism-(falcon.version)-classes.jar to access these properties. It
does not bundle deploy.properties explicitly in its war.
> {noformat}
> pragya@8RPCG32:~/WORKSPACE/trial-falcon/server/server/webapp/falcon/WEB-INF/classes$
ls
> client.properties  falcon-buildinfo.properties  log4j.xml  META-INF  org
> pragya@8RPCG32:~/WORKSPACE/trial-falcon/server/server/webapp/falcon/WEB-INF/lib$ ls |
grep prism
> falcon-prism-0.8-SNAPSHOT-classes.jar
> {noformat}
> Although, I feel this is a hackaround and we should bundle falcon.war with its own deploy.properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message