[
https://issues.apache.org/jira/browse/EAGLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416028#comment-15416028
]
ASF GitHub Bot commented on EAGLE-437:
--------------------------------------
GitHub user yonzhang opened a pull request:
https://github.com/apache/incubator-eagle/pull/327
Eagle assembly for new app framework
https://issues.apache.org/jira/browse/EAGLE-437
https://issues.apache.org/jira/browse/EAGLE-430
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yonzhang/incubator-eagle develop
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/327.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #327
----
commit feeece3f2b5af9e2c2fa17af6e8806f50a8a2930
Author: yonzhang <[email protected]>
Date: 2016-08-10T21:17:04Z
eagle assembly for new app framework
----
> create workable fat jar for starting application remotely
> ---------------------------------------------------------
>
> Key: EAGLE-437
> URL: https://issues.apache.org/jira/browse/EAGLE-437
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Edward Zhang
> Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Explore ways to package fat jar for starting applications
> 1) package all topology jars together into one single fat jar. Need fix
> a. metadata.xml should be differentiated by different directory, for
> example metadata.xml is under directory of
> /META-INF/apps/<APPNAME>/metadata.xml
> b. SPI configuration file should be removed and
> ApplicationProviderSPILoader should be redesign to get all providers
> 2) package fat jar on demand.
> No far jar after packaging.
> Need remember all dependent jars and write code to package fat jar on
> demand
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
