- Extract required libraries into JAR
- Package required libraries into JAR
- Copy required libraries into sub folder next to JAR
Extract required libraries into JAR - Extracts the actual
.class
files from the libraries your app uses and puts those.class
files inside the runnable JAR. So, the runnable JAR will not only contain the.class
files of your application, but also the.class
files of all the libraries your application uses.Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible.
Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the
.class
files of your application.
Option #2 is convenient because it packages everything neatly into a single JAR, and keeps the library JARs separated from your application's .class
files.
However, a downside to packaging everything inside of a single JAR (options #1 and #2) is that, if you update your application, then the user will have to download more data to update the application. If the JARs are kept separate, then the user would only have to download the JAR that contains your application code, instead of a single, massive JAR that contains your application code and all the library code.
'Archive' 카테고리의 다른 글
가독성의 기본 정리 (The Fundamental Theorem of Readability) (0) | 2012.05.11 |
---|---|
Python list의 +=와 append의 성능 분석 (보너스: +=와 extend 성능 분석) (0) | 2012.04.06 |
ls -l 명령어로 파일 크기 확인할 때 1M 단위로 보기 (0) | 2012.03.29 |
리팩토링을 망설이지 말자 (0) | 2012.03.29 |
PriorityQueue를 적재적소에 사용하자 (0) | 2012.03.27 |