Differences

This shows you the differences between two versions of the page.

--- java:types-of-jar-files [2023/07/06 16:52] – odefta
+++ java:types-of-jar-files [2023/07/06 16:52] (current) – odefta
@@ Line 1: / Line 1: @@
 ====== Types of jars in java ======
-  - **Regular (or Non-Uber) JARs**: These JAR files contain only the .class files (compiled Java bytecode) of your application. \\They do not include the .class files for any libraries your application uses. This requires that all libraries used by your application are available on the classpath when your JAR is run.
+  - **Regular (or Non-Uber) JARs**: These JAR files contain only the .class files (compiled Java bytecode) of your application. They do not include the .class files for any libraries your application uses. This requires that all libraries used by your application are available on the classpath when your JAR is run.
   - **Thin JARs**: In a thin JAR, dependencies are not packaged inside the JAR. Instead, a lib directory is usually provided alongside the JAR, containing all necessary dependencies. The JAR file includes a Class-Path entry in the manifest file, which references the dependent JARs.
   - **Uber (or Fat) JARs**: These JARs contain not only the .class files for your application, but also the .class files for all libraries your application depends on. This creates a self-contained JAR that can be run without requiring any additional libraries on the classpath. This can be useful for distributing an application or for deploying it in a containerized environment, for example.