Vaadin project error in "pom.xml"

Asked

Viewed 98 times

1

I created a Maven project and put the dependencies, I got the bug in the pom related to dependency Servlet .

<dependency>
   <groupId>javax.servlet</groupId>
   <artifactId>servlet-api</artifactId>
   <version>3.0.1</version>
   <scope>provided</scope>
</dependency>

I’m using Java 7, Tomcat 7 and Vaadin 7.3.4

java tomcat maven

1 answer

0


There is no version 3.0.1 yet, by looking at central repository, I believe you want the version 3.0-alpha-1.

Use addiction that way:

<dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>servlet-api</artifactId>
    <version>3.0-alpha-1</version>
    <scope>provided</scope>
</dependency>

  • Math good afternoon! You are correct, I changed and the pom passed

  • @Robson to orders. If this is the correct answer you can mark it as accepted, to indicate that your problem is solved. If you want to understand better see this link: How and why to accept an answer?

  • Dear Math I created a new project this time using the vaadin plugin in eclipse, when finishing I converted the project to Maven, at the end I noticed that it configured the dependency with version 3.0.1 of javax.Servlet-api

  • @Robson doesn’t quite understand where you’re going with this. Every time you create a new project, it automatically creates a dependency on 3.0.1 and gives the same error? Or are you reporting that you have successfully managed to use a version 3.0.1 dependency? Please clarify your question so that it is possible to help you.

  • This same I did a new project and converted to Maven and did not present the error in pom.xml as before, now I went back to my original project and back to the dependency what I changed was that I did not put provided and passed without problem.

  • @Robson It’s possible that when you used the Vaadin plugin it locally registered the 3.0.1 dependency, because it was definitely not downloaded from the central repository. I just created a project (without the Vaadin plugin as I don’t have it) and tried to add the dependency without the provided and it didn’t work, so it’s possible that his mistake was that actually the first time he couldn’t register the dependency correctly. At the information level, I could check the contents of the folder C:\Users\Seu Usuário\.m2\repository\javax\servlet\servlet-api\3.0.1 has some . jar?

Show 1 more comment

Browser other questions tagged java tomcat maven

You are not signed in. Login or sign up in order to post.