Hazelcast 3.5 Freemarker dependency

[mo...@pjm.co.at]

Hello!

I just upgraded to Hazelcast 3.5.

It now has a new maven dependency. Freemarker.

This triggers the Spring Boot autoconfiguration feature of a couple of my web apps and services.

They complain about the missing template directory and terminate.

Why is this dependency needed? Can I safely exclude it?

Sure I could disable the Freemarker auto configuration feature of Spring Boot but I think this is an ugly solution.

Regards

Ralph

Commercial Register No.: FN 278800 a / Commercial Register Court: Landesgericht für Zivilrechtsachen Graz-Firmenbuch / Head Office: Graz

The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication by error, please notify us immediately by responding to this email and then delete it from your system.

[Jaromir Hamala]

Hello Ralph,

thank you for reporting this. May I kindly ask you to open a GitHub issue for this? Freemarker is needed during compile time to generate messages for a new client protocol, but it should not be propagated as a transitive dependency. In mean time you can explicitly exclude Freemarker using Maven. See this: http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-project-dependencies.html#pom-relationships-sect-conflict 

It's still ugly, but it keeps your project clean. 

Cheers,

Jaromir

[Enes Akar]

Yes, we will fix this by setting its scope to provided in nearest patch release.

Thanks for reporting.

 

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at http://groups.google.com/group/hazelcast.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/1c421fc6-8418-49ec-9b5c-352054f41fae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[timv...@gmail.com]

I noticed this too. I also notice 3.5 pulls in the following dependencies:

net.sourceforge.findbugs:annotations:jar:1.3.2:compile

com.hazelcast:hazelcast-code-generator:jar:3.5:compile

^^ These two look like test or build dependencies that somehow leaked into the runtime deps (?)

com.eclipsesource.minimal-json:minimal-json:jar:0.9.2:compile

^^ Not sure about this one. Is it needed at runtime.

Now a lot of projects are building as "fatjars" it's quite important to keep size of dependencies down otherwise size of fatjar balloons.

I also notice that the 3.5 hazelcast jar is over 2MB bigger than than the 3.4 version... 

[Noctarius]

Hey Tim,

Yes this is already fixed for 3.5.1. Those are pure build time dependencies (minimal-json is shaded in and the generator is an annotation processor for the  new client protocol), you can just exclude them in maven / gradle to remove them.

Chris

To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/acf98d7c-61a5-49c7-b2b1-eb963d252e09%40googlegroups.com.