Skip to content

Tag: pom.xml

Vaadin object is not an instance of declaring class

I’m trying to call a method in class named (DataActions) to the dashboard view so the grid can be able to receive the objects given after the method execution, but still no luck solving this error (java.lang.IllegalArgumentException: object is not an instance of declaring class). -Class (DataSession) is the class responsible for opening the database session. -Class (DataActions) is the

Maven error Cannot access defaults field of Properties

I use the newest version of Java -> 16. When I run mvn clean, I am getting Could not initialize class org.apache.maven.plugin.war.util.WebappStructureSerializer error. I read that adding maven-war-plugin can be a solution, but it didn’t work for me. When I run mvn install, the following error occurs: Error injecting constructor, java.lang.ExceptionInInitializerError: Cannot access defaults field of Properties at org.apache.maven.plugin.war.WarMojo.(Unknown Source)

SLF4J: Class path contains multiple SLF4J bindings warning

I’ve seen in other questions that usually the solution to this warning is to exclude slf4j from the dependency that causes this conflict, but I can’t spot the problem in my project. I run mvn dependency:tree command and this is the output: Answer You can solve the issue by adding the following exclusion in the dependencies (of pom.xml) that caused