[
https://issues.apache.org/jira/browse/EAGLE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412922#comment-15412922
]
Hao Chen commented on EAGLE-430:
--------------------------------
The package structure should be as following, and we shouldn't separate static
web resource out of jar packages.
{code}
/eagle
/conf (application.conf)
/bin (add class path)
/lib
/core/eagle-server.jar
/assets/index.html
/apps
app1.jar
/META-INF/apps/app1/metadata.xml
/assets/apps/app1/index.js
app2.jar
/META-INF/apps/app2/metadata.xml
/assets/apps/app2/index.js
{code}
> explore new packaging method for eagle using new app framework
> --------------------------------------------------------------
>
> Key: EAGLE-430
> URL: https://issues.apache.org/jira/browse/EAGLE-430
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Edward Zhang
> Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> New app framework will manage application jars in central place, while
> application jars include topology jars and web jars.
> We need figure out Eagle 0.5 binary layout.
> The goal is with only Eagle 0.5 server we can start any topology remotely.
> /eagle-server
> /conf (application.conf)
> /bin (add class path)
> /lib
> /eagle-server.jar
> /apps
> app1.jar
> app1-web.jar
> app2.jar
> /web
> index.html
> /js
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
