Distinguish between runtime and compile time libraries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
RevAger |
Fix Released
|
Undecided
|
Johannes Wettinger |
Bug Description
With the inclusion of launch4j in trunk/r23 (http://
1.) All jar-files in lib get included into the jar file when running our dist-target. This makes the resulting binary more fat than it should be - I suggest, we should divide the libraries into compile time and runtime libraries, and only include the runtime libraries by default. (instead of modifying our build script and adding exception rules each time we add a new development time library)
2.) All 3rd-Party libs should be only included as JAR-File with an appropiate License.txt, named <NAME_OF_
Maybe, we should also document this for the future by establishing a policy / documentation blueprint for dealing with 3rd party libs.
Changed in revager: | |
status: | New → Fix Committed |
assignee: | nobody → Johannes Wettinger (jojow) |
Changed in revager: | |
status: | Fix Committed → Fix Released |