Double elemental.json dependencies on the classpath #4569
Labels
Milestone
Comments
pekam
added a commit
that referenced
this issue
Sep 11, 2018
This was referenced Sep 11, 2018
pekam
added a commit
that referenced
this issue
Sep 12, 2018
* Exclude duplicate gwt-elemental dependency Fixes #4569 * Remove the other exclude which is now redundant it was coming transitively from gwt-elemental * Revert changes in the test caused by the dependency Seems that the exclusion for validation API didn't work in the first place, which is why these changes to the test were made the same time the dependency was updated: #4416 Now the validation API is correctly excluded so the error messages are back to original.
|
Symptoms fixed by excluding the dependency. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When starting an application using
1.1-SNAPSHOT, warnings are logged for variouselemental.jsonclasses being found from two different locations on the classpath:com/vaadin/external/gwt/gwt-elemental/2.8.2.vaadin1/gwt-elemental-2.8.2.vaadin1.jarandcom/google/gwt/gwt-elemental/2.8.2/gwt-elemental-2.8.2.jar. This happens because our own2.8.2.vaadin1version has the original as a regular dependency in itspom.xml.The text was updated successfully, but these errors were encountered: