After running my Vaadin 8 (compatibility mode for V7) application in Eclipse+Tomcat, I noted the following JARs are included, but I’d like to confirm if any of these can safely be ignored on a deployment server.
-
activation-1.1.jar - Is this Vaadin 8 standard or perhaps auto-maven-included from this entry (I need javax.activation to work with javax.mail). I suspect it’s not my POM dependency because it’s 1.1 and I’m using 1.2:
<dependency>
<groupId>javax.activation</groupId>
<artifactId>javax.activation-api</artifactId>
<version>1.2.0</version>
</dependency>
(or perhaps I should be using this instead?)
<dependency>
<groupId>com.sun.activation</groupId>
<artifactId>javax.activation</artifactId>
<version>1.2.0</version>
</dependency>
-
atmosphere-runtime-2.4.30.vaadin1.jar
-
commons-codec-1.10.jar
-
commons-collections4-4.1.jar
-
flute-1.3.0.gg2.jar
-
gentyref-1.2.0.vaadin1.jar
-
gwt-elemental-2.8.2.jar
-
gwt-user-2.8.2.jar
-
jsinterop-annotations-1.0.2-sources.jar
-
jsinterop-annotations-1.0.2.jar
-
jsoup-1.11.2.jar
-
sac-1.3.jar
-
vaadin-client-8.7.2.jar
-
vaadin-compatibility-client-8.7.2.jar
-
vaadin-compatibility-client-compiled-8.7.2.jar
-
vaadin-compatibility-server-8.7.2.jar
-
vaadin-compatibility-shared-8.7.2.jar
-
vaadin-compatibility-themes-8.7.2.jar
-
vaadin-push-8.7.2.jar
-
vaadin-sass-compiler-0.9.13.jar
-
vaadin-server-8.7.2.jar
-
vaadin-shared-8.7.2.jar
-
vaadin-slf4j-jdk14-1.6.1.jar
-
validation-api-1.0.0.GA-sources.jar
-
validation-api-1.0.0.GA.jar
When I ran Vaadin 7, I only had to include
- atmosphere-runtime-2.2.13.vaadin1.jar
- flute-1.3.0.gg2.jar
- jsoup-1.8.3.jar
- sac-1.3.jar
- vaadin-push-7.7.16.jar
- vaadin-sass-compiler-0.9.13.jar
- vaadin-server-7.7.16.jar
- vaadin-shared-7.7.16.jar
- vaadin-slf4j-jdk14-1.6.1.jar
- vaadin-themes-7.7.16.jar
I just looked at the WAR file created, and it includes a lot more JARs than in the Vaadin 7 days. Can I confirm if any of these are only for development needs, or must they all be included in the WAR for production deployments? I have removed the JARs that are present due to my needing them.
-rwxrwxrwx 0 0 0 0 Nov 1 2018 WEB-INF/lib/atmosphere-runtime-2.4.30.vaadin1.jar
-rwxrwxrwx 0 0 0 0 Nov 1 2018 WEB-INF/lib/commons-codec-1.10.jar
-rwxrwxrwx 0 0 0 0 Apr 1 13:41 WEB-INF/lib/commons-collections4-4.1.jar
-rwxrwxrwx 0 0 0 0 Apr 12 2017 WEB-INF/lib/flute-1.3.0.gg2.jar
-rwxrwxrwx 0 0 0 0 Nov 1 2018 WEB-INF/lib/gentyref-1.2.0.vaadin1.jar
-rwxrwxrwx 0 0 0 0 Jan 27 2018 WEB-INF/lib/gwt-elemental-2.8.2.jar
-rwxrwxrwx 0 0 0 0 Nov 1 2018 WEB-INF/lib/gwt-user-2.8.2.jar
-rwxrwxrwx 0 0 0 0 Nov 1 2018 WEB-INF/lib/jsinterop-annotations-1.0.2.jar
-rwxrwxrwx 0 0 0 0 Nov 1 2018 WEB-INF/lib/jsinterop-annotations-1.0.2-sources.jar
-rwxrwxrwx 0 0 0 0 Nov 1 2018 WEB-INF/lib/jsoup-1.11.2.jar
-rwxrwxrwx 0 0 0 0 Apr 12 2017 WEB-INF/lib/sac-1.3.jar
-rwxrwxrwx 0 0 0 0 Apr 3 14:55 WEB-INF/lib/vaadin-client-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 3 15:16 WEB-INF/lib/vaadin-compatibility-client-compiled-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 3 14:59 WEB-INF/lib/vaadin-compatibility-server-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 3 14:59 WEB-INF/lib/vaadin-compatibility-shared-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 3 14:55 WEB-INF/lib/vaadin-push-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 12 2017 WEB-INF/lib/vaadin-sass-compiler-0.9.13.jar
-rwxrwxrwx 0 0 0 0 Apr 3 14:54 WEB-INF/lib/vaadin-shared-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 3 14:54 WEB-INF/lib/vaadin-server-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Jan 27 2018 WEB-INF/lib/vaadin-slf4j-jdk14-1.6.1.jar
-rwxrwxrwx 0 0 0 0 Apr 3 14:55 WEB-INF/lib/vaadin-themes-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 12 2017 WEB-INF/lib/validation-api-1.0.0.GA.jar
-rwxrwxrwx 0 0 0 0 Apr 3 15:00 WEB-INF/lib/vaadin-compatibility-client-8.7.2.jar
-rwxrwxrwx 0 0 0 0 Apr 12 2017 WEB-INF/lib/validation-api-1.0.0.GA-sources.jar
Thanks for any help as I try to trim down the release size if at all possible.