Can't compile vaadin widgetset using gradle and V-Leaflet
I have a spring-vaadin project using vaadin addons and a gradle configuration.
Adding V-Leaflet to my project worked the first time, but later it broke and the widgetset never compiled again. The compilation fails reporting it can't find jackson:
:vaadinPluginVersionCheck SKIPPED
:compileJava
:vaadinUpdateWidgetset
:processResources UP-TO-DATE
:classes
:vaadinClassPathJar UP-TO-DATE
:vaadinCompile
Errors in 'org/vaadin/addon/leaflet/shared/Point.java'
Line 37: JsonValue cannot be resolved to a type
Line 3: The import com.fasterxml cannot be resolved
Aborting compile due to errors in some input files
FAILED
Here is the relevant section in the gradle dependencies section:
compile 'com.fasterxml.jackson.core:jackson-core:2.9.7'
compile 'com.fasterxml.jackson.core:jackson-annotations:2.9.7'
vaadinCompile 'org.peimari:g-leaflet:+' //For v-leaflet
compile 'org.vaadin.addon:v-leaflet:+' //For map fields
I have already tried using vaadinCompile, compile and implementation for all of them.
gradle build.gradle vaadin vaadin8 vaadin4spring
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
add a comment |
I have a spring-vaadin project using vaadin addons and a gradle configuration.
Adding V-Leaflet to my project worked the first time, but later it broke and the widgetset never compiled again. The compilation fails reporting it can't find jackson:
:vaadinPluginVersionCheck SKIPPED
:compileJava
:vaadinUpdateWidgetset
:processResources UP-TO-DATE
:classes
:vaadinClassPathJar UP-TO-DATE
:vaadinCompile
Errors in 'org/vaadin/addon/leaflet/shared/Point.java'
Line 37: JsonValue cannot be resolved to a type
Line 3: The import com.fasterxml cannot be resolved
Aborting compile due to errors in some input files
FAILED
Here is the relevant section in the gradle dependencies section:
compile 'com.fasterxml.jackson.core:jackson-core:2.9.7'
compile 'com.fasterxml.jackson.core:jackson-annotations:2.9.7'
vaadinCompile 'org.peimari:g-leaflet:+' //For v-leaflet
compile 'org.vaadin.addon:v-leaflet:+' //For map fields
I have already tried using vaadinCompile, compile and implementation for all of them.
gradle build.gradle vaadin vaadin8 vaadin4spring
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
One possibility is that you have two different versions of Jackson in your class path, and hence class loader cannot determine which JsonValue to use. Typically I am checking the dependency tree in this kind of case and excluding the unwanted transitive dependency, see discuss.gradle.org/t/…
– Tatu Lund
Nov 25 '18 at 8:04
I have tested that but there is no conflict with the available jackson. The vaading gradle plugin developer tried to help me also, with: Have you tried adding the addon on the vaadidnCompile classpath? So it would look like this. // Add addon + its transitive dependencies to GWT compile classpath vaadinCompile 'org.vaadin.addon:v-leaflet:+' // Add addon + its transitive dependencies to Java compile classpath compile 'org.vaadin.addon:v-leaflet:+' But it didn't work.
– Lucas Montenegro Carvalhaes
Nov 29 '18 at 21:16
add a comment |
I have a spring-vaadin project using vaadin addons and a gradle configuration.
Adding V-Leaflet to my project worked the first time, but later it broke and the widgetset never compiled again. The compilation fails reporting it can't find jackson:
:vaadinPluginVersionCheck SKIPPED
:compileJava
:vaadinUpdateWidgetset
:processResources UP-TO-DATE
:classes
:vaadinClassPathJar UP-TO-DATE
:vaadinCompile
Errors in 'org/vaadin/addon/leaflet/shared/Point.java'
Line 37: JsonValue cannot be resolved to a type
Line 3: The import com.fasterxml cannot be resolved
Aborting compile due to errors in some input files
FAILED
Here is the relevant section in the gradle dependencies section:
compile 'com.fasterxml.jackson.core:jackson-core:2.9.7'
compile 'com.fasterxml.jackson.core:jackson-annotations:2.9.7'
vaadinCompile 'org.peimari:g-leaflet:+' //For v-leaflet
compile 'org.vaadin.addon:v-leaflet:+' //For map fields
I have already tried using vaadinCompile, compile and implementation for all of them.
gradle build.gradle vaadin vaadin8 vaadin4spring
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
I have a spring-vaadin project using vaadin addons and a gradle configuration.
Adding V-Leaflet to my project worked the first time, but later it broke and the widgetset never compiled again. The compilation fails reporting it can't find jackson:
:vaadinPluginVersionCheck SKIPPED
:compileJava
:vaadinUpdateWidgetset
:processResources UP-TO-DATE
:classes
:vaadinClassPathJar UP-TO-DATE
:vaadinCompile
Errors in 'org/vaadin/addon/leaflet/shared/Point.java'
Line 37: JsonValue cannot be resolved to a type
Line 3: The import com.fasterxml cannot be resolved
Aborting compile due to errors in some input files
FAILED
Here is the relevant section in the gradle dependencies section:
compile 'com.fasterxml.jackson.core:jackson-core:2.9.7'
compile 'com.fasterxml.jackson.core:jackson-annotations:2.9.7'
vaadinCompile 'org.peimari:g-leaflet:+' //For v-leaflet
compile 'org.vaadin.addon:v-leaflet:+' //For map fields
I have already tried using vaadinCompile, compile and implementation for all of them.
gradle build.gradle vaadin vaadin8 vaadin4spring
gradle build.gradle vaadin vaadin8 vaadin4spring
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
asked Nov 20 '18 at 20:54
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
120110
One possibility is that you have two different versions of Jackson in your class path, and hence class loader cannot determine which JsonValue to use. Typically I am checking the dependency tree in this kind of case and excluding the unwanted transitive dependency, see discuss.gradle.org/t/…
– Tatu Lund
Nov 25 '18 at 8:04
I have tested that but there is no conflict with the available jackson. The vaading gradle plugin developer tried to help me also, with: Have you tried adding the addon on the vaadidnCompile classpath? So it would look like this. // Add addon + its transitive dependencies to GWT compile classpath vaadinCompile 'org.vaadin.addon:v-leaflet:+' // Add addon + its transitive dependencies to Java compile classpath compile 'org.vaadin.addon:v-leaflet:+' But it didn't work.
– Lucas Montenegro Carvalhaes
Nov 29 '18 at 21:16
add a comment |
One possibility is that you have two different versions of Jackson in your class path, and hence class loader cannot determine which JsonValue to use. Typically I am checking the dependency tree in this kind of case and excluding the unwanted transitive dependency, see discuss.gradle.org/t/…
– Tatu Lund
Nov 25 '18 at 8:04
I have tested that but there is no conflict with the available jackson. The vaading gradle plugin developer tried to help me also, with: Have you tried adding the addon on the vaadidnCompile classpath? So it would look like this. // Add addon + its transitive dependencies to GWT compile classpath vaadinCompile 'org.vaadin.addon:v-leaflet:+' // Add addon + its transitive dependencies to Java compile classpath compile 'org.vaadin.addon:v-leaflet:+' But it didn't work.
– Lucas Montenegro Carvalhaes
Nov 29 '18 at 21:16
One possibility is that you have two different versions of Jackson in your class path, and hence class loader cannot determine which JsonValue to use. Typically I am checking the dependency tree in this kind of case and excluding the unwanted transitive dependency, see discuss.gradle.org/t/…
– Tatu Lund
Nov 25 '18 at 8:04
One possibility is that you have two different versions of Jackson in your class path, and hence class loader cannot determine which JsonValue to use. Typically I am checking the dependency tree in this kind of case and excluding the unwanted transitive dependency, see discuss.gradle.org/t/…
– Tatu Lund
Nov 25 '18 at 8:04
I have tested that but there is no conflict with the available jackson. The vaading gradle plugin developer tried to help me also, with: Have you tried adding the addon on the vaadidnCompile classpath? So it would look like this. // Add addon + its transitive dependencies to GWT compile classpath vaadinCompile 'org.vaadin.addon:v-leaflet:+' // Add addon + its transitive dependencies to Java compile classpath compile 'org.vaadin.addon:v-leaflet:+' But it didn't work.
– Lucas Montenegro Carvalhaes
Nov 29 '18 at 21:16
I have tested that but there is no conflict with the available jackson. The vaading gradle plugin developer tried to help me also, with: Have you tried adding the addon on the vaadidnCompile classpath? So it would look like this. // Add addon + its transitive dependencies to GWT compile classpath vaadinCompile 'org.vaadin.addon:v-leaflet:+' // Add addon + its transitive dependencies to Java compile classpath compile 'org.vaadin.addon:v-leaflet:+' But it didn't work.
– Lucas Montenegro Carvalhaes
Nov 29 '18 at 21:16
add a comment |
1 Answer
1
active
oldest
votes
I have solved this.
I don't know exactly what happened but I solved it by updating everything and removing direct access to transitive dependencies within vaaddin compile.
The final gradle script is:
vaadinCompile 'org.vaadin.addon:v-leaflet:2.0.9'
compile 'org.vaadin.addon:v-leaflet:2.0.9'
Only adding the vaadinCompile part solved the issue for the jar and running from gradle, but I had to add the compile directive also, so that eclipse could find v-leaflet classes on the classpath.
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401376%2fcant-compile-vaadin-widgetset-using-gradle-and-v-leaflet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have solved this.
I don't know exactly what happened but I solved it by updating everything and removing direct access to transitive dependencies within vaaddin compile.
The final gradle script is:
vaadinCompile 'org.vaadin.addon:v-leaflet:2.0.9'
compile 'org.vaadin.addon:v-leaflet:2.0.9'
Only adding the vaadinCompile part solved the issue for the jar and running from gradle, but I had to add the compile directive also, so that eclipse could find v-leaflet classes on the classpath.
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
add a comment |
I have solved this.
I don't know exactly what happened but I solved it by updating everything and removing direct access to transitive dependencies within vaaddin compile.
The final gradle script is:
vaadinCompile 'org.vaadin.addon:v-leaflet:2.0.9'
compile 'org.vaadin.addon:v-leaflet:2.0.9'
Only adding the vaadinCompile part solved the issue for the jar and running from gradle, but I had to add the compile directive also, so that eclipse could find v-leaflet classes on the classpath.
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
add a comment |
I have solved this.
I don't know exactly what happened but I solved it by updating everything and removing direct access to transitive dependencies within vaaddin compile.
The final gradle script is:
vaadinCompile 'org.vaadin.addon:v-leaflet:2.0.9'
compile 'org.vaadin.addon:v-leaflet:2.0.9'
Only adding the vaadinCompile part solved the issue for the jar and running from gradle, but I had to add the compile directive also, so that eclipse could find v-leaflet classes on the classpath.
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
I have solved this.
I don't know exactly what happened but I solved it by updating everything and removing direct access to transitive dependencies within vaaddin compile.
The final gradle script is:
vaadinCompile 'org.vaadin.addon:v-leaflet:2.0.9'
compile 'org.vaadin.addon:v-leaflet:2.0.9'
Only adding the vaadinCompile part solved the issue for the jar and running from gradle, but I had to add the compile directive also, so that eclipse could find v-leaflet classes on the classpath.
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
answered Dec 18 '18 at 17:30
Lucas Montenegro CarvalhaesLucas Montenegro Carvalhaes
120110
120110
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401376%2fcant-compile-vaadin-widgetset-using-gradle-and-v-leaflet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
One possibility is that you have two different versions of Jackson in your class path, and hence class loader cannot determine which JsonValue to use. Typically I am checking the dependency tree in this kind of case and excluding the unwanted transitive dependency, see discuss.gradle.org/t/…
– Tatu Lund
Nov 25 '18 at 8:04
I have tested that but there is no conflict with the available jackson. The vaading gradle plugin developer tried to help me also, with: Have you tried adding the addon on the vaadidnCompile classpath? So it would look like this. // Add addon + its transitive dependencies to GWT compile classpath vaadinCompile 'org.vaadin.addon:v-leaflet:+' // Add addon + its transitive dependencies to Java compile classpath compile 'org.vaadin.addon:v-leaflet:+' But it didn't work.
– Lucas Montenegro Carvalhaes
Nov 29 '18 at 21:16