Vaadin 8 includes activation-1.1.jar but our pom.xml includes javax.activat

Vaadin 6 / 7 / 8
1

We are on Vaadin 8.8.0.

It appears that Vaadin 8’s pom.xml causes activation-1.1.jar to be included in WEB-INF/lib, but we need javax.activation-1.2.0.jar (for PNG support in sending emails) so our pom.xml includes it along with our javax.mail-1.6.2.jar:

<dependency>
	<groupId>com.sun.activation</groupId>
	<artifactId>javax.activation</artifactId>
	<version>1.2.0</version>
</dependency>
<dependency>
	<groupId>com.sun.mail</groupId>
	<artifactId>javax.mail</artifactId>
	<version>1.6.2</version>
</dependency>

Is there a way to block Vaadin’s inclusion of the older 1.1 activation JAR? I presume it’s okay to use the more current one.

2

Adding this to my pom.xml seems to keep the Vaadin 1.1 version from being in WEB-INF/lib so the 1.2 can be used instead:

<dependency>
	<groupId>javax.activation</groupId>
	<artifactId>activation</artifactId>
	<version>1.1</version>
	<scope>provided</scope>
</dependency>