incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Morel (JIRA)" <>
Subject [jira] [Resolved] (S4-67) S4R packaging: improve packaging of dependencies
Date Fri, 20 Jul 2012 07:37:33 GMT


Matthieu Morel resolved S4-67.

    Resolution: Fixed
      Assignee: Matthieu Morel

S4R packaging and classloading improvements were implemented in S4-72.
Library shading is a separate ticket S4-80
> S4R packaging: improve packaging of dependencies
> ------------------------------------------------
>                 Key: S4-67
>                 URL:
>             Project: Apache S4
>          Issue Type: Improvement
>    Affects Versions: 0.5
>            Reporter: Matthieu Morel
>            Assignee: Matthieu Morel
>             Fix For: 0.5
> Currently, the creation of the S4R package involves unpackaging all dependencies, then
putting them altogether in a single file along with the S4 application classes.
> This is very inefficient (and therefore potentially long, resulting in long development
cycles) because there is a lot of file copying involved. In addition it may be brittle due
to name conflicts.
> We should improve the process by:
> - including external jars in the S4R archive without unpackaging them, typically in the
/lib dir
> - updating the classloading mechanism in S4. Ideas could be taken from Hadoop's RunJar
class. We should avoid fancy stuff here, and the current multi-classloader is not really needed
if we have a single app per S4 node.
> - "shading" platform classes and dependencies, in order to avoid any conflict between
S4 platform dependencies and application dependencies?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message