New Guava Dependency Vaadin-CDI breaks TomEE deployment ?

Flow
1

Hello,

I am using the vaadin-cdi 1.0-snapshot in a project, and today, the deployment under tomee 1.6.0.2 via tomee:run broke with symtoms simmilar to what is deiscussed described here:

http://stackoverflow.com/questions/22157408/how-to-resolve-api-type-java-util-set-is-not-found-with-the-qualifiers-error

After searching for some while, I discovered:
https://github.com/vaadin/cdi/commits/master?author=hesara&path[]=vaadin-cdi&path[]
=pom.xml

That Henri Sara added guava 15 to the non-testing dependencies earlier today.

  • vaadin-cdi still is on Vaadin 7.2.5 and not 7.2.6
  • Vaadin 7.2.x is depending on guava 16.0.1.vaadin1, while the changes today make vaadin-cdi depend on guava 15.0 in addition to that.
  • Excluding guava from Vaadin CDI in the POM breaks vaadin CDI:
    exception sending context initialized event to listener instance of class com.vaadin.cdi.internal.ContextDeployer
    java.lang.NoClassDefFoundError: com/google/common/base/CaseFormat
    at com.vaadin.cdi.internal.Conventions.deriveMappingForUI(Conventions.java:47)

Is there a way to reference a specific older snapshot release in the POM of my application?

So at this point I am just suspecting that at this point this change on the vaadin-cdi broke things, Can anybody verify this? For me this broke three individual web-applications I am developing based on vaadin-cdi. And yes, I know it is a snapshot release and shall be considered appropriately.

Thank you.

Best regards,
Dominic

2

Just a comment, the alpha2 seems to work fine. So maybe consider this feedback to current developments.

Anyway, I really like the CDI plugin!

Dominic

3

Guava version 16.0.1.vaadin1 is a rebased version in a different package than the standard guava, so it should not interfere in any way with other Guava versions. It is there primarily for internal use by Vaadin, and thus the CDI add-on does not use it.

The class Conventions in Vaadin CDI now depends on a standard Guava version. Created
ticket #14461
 to upgrade also this dependency to 16.0.1 for compatibility with Apache OpenWebBeans.

4

Hello, Henri.

Thank you for looking into this. Currently I am running the cdi beta2 and I switched to wildfly. According to the ticket, the issue appears to be resolved. Thanks for the reply and update!

Dominic