A required class was missing while executing org.mortbay.jetty:jetty-maven-plugin

-
When I was running the command
mvn jetty:run
I got the message

[ERROR] Failed to execute goal org.mortbay.jetty:jetty-maven-plugin:8.1.1.v20120215:run (default-cli) on project CabShareService: Execution default-cli of goal
org.mortbay.jetty:jetty-maven-plugin:8.1.1.v20120215:run failed: A required class was missing while executing org.mortbay.jetty:jetty-maven-plugin:8.1.1.v201202
15:run: org/slf4j/impl/StaticLoggerBinder
My Jetty settings were


    org.mortbay.jetty
    jetty-maven-plugin
    8.1.1.v20120215
    
     
      com.jolbox
      bonecp
      0.7.1.RELEASE
     
    
    
     
      /${project.artifactId}
     
     src/test/resources/jetty.xml
     true
     10
     ${project.artifactId}-stop
     9999
 The reason of the error was that the slf4j implementation was not defined.
Tried setting the Logback as the one of the better implementation (detailed post ) .

Added the following dependency in the jetty dependencies section.


  ch.qos.logback
  logback-classic
  0.9.29

This produced the following error


[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
Exception in thread "Thread-1" java.lang.NoSuchMethodError: org.slf4j.helpers.MessageFormatter.arrayFormat(Ljava/lang/String;[Ljava/lang/Object;)Lorg/slf4j/help
ers/FormattingTuple;
        at org.eclipse.jetty.util.log.JettyAwareLogger.log(JettyAwareLogger.java:613)
        at org.eclipse.jetty.util.log.JettyAwareLogger.debug(JettyAwareLogger.java:200)
        at org.eclipse.jetty.util.log.Slf4jLog.debug(Slf4jLog.java:94)
        at org.eclipse.jetty.util.thread.ShutdownThread.run(ShutdownThread.java:125)

So it was obvious that all is not well. Some reading along will hit and trial reached to following jetty plugin configuration which removed the errors



org.mortbay.jetty
jetty-maven-plugin
8.1.1.v20120215



com.jolbox
bonecp
0.7.1.RELEASE



ch.qos.logback
logback-classic
1.0.0


org.slf4j
slf4j-api
1.6.1





logback.configurationFile

./src/test/resources/logback.xml



/${project.artifactId}

src/test/resources/jetty.xml
true
10
${project.artifactId}-stop
9999


 If you notice we have separated the Logback  configuration from the pom file. Below is a sample logback.xml file details.




class="ch.qos.logback.core.rolling.RollingFileAppender">
logFile.log


logFile.%d{yyyy-MM-dd}.log


%-4relative [%thread] %-5level %logger{35} - %msg%n













Comments

Post a Comment

Popular posts from this blog

Hibernate: a different object with the same identifier value was already associated with the session

-
People working with Hibernate might be familiar with the below error. org.springframework.orm.hibernate3.HibernateSystemException: a different object with the same identifier value was already associated with the session: nested exception is org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session This exception is generated when we try to load an instance object in session which has been already loaded by hibernate. Easier said than done. Hibernate considers two persistent entities identical if the two rows of the table can be said identical. Above error could be generated in many ways and there may be various solutions on net like using session merge etc to get away with the problem. I will discuss here the reason for me getting this problem and the way I resolved it. Below is the code which generated the exception for me. Following is the method which caused the exception @Transactional(propagation=Propagation....
Read more

BeanDefinitionStoreException: Failed to parse configuration class: Could not find class [javax.jms.ConnectionFactory]

-
If you are creating a Spring Boot application and see the following error stack . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.2.0.RELEASE) 2020-06-27 19:30:32.786 INFO 35224 --- [ main] SchoolApplication : Starting SchoolApplication on LTUS76179 with PID 35224 (C:\personal\eclipse-workspace\apievolution\target\classes started by 381548 in C:\personal\eclipse-workspace\apievolution) 2020-06-27 19:30:32.796 INFO 35224 --- [ main] SchoolApplication : No active profile set, falling back to default profiles: default 2020-06-27 19:30:32.964 WARN 35224 --- [ main] ionWarningsApplicationContextInitializer : ** WARNING ** : Your ApplicationContext is unli...
Read more

org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]

-
This Exception during the maven build in an hibernate based project could come due to various reasons. Primarily one should look into the complete stack trace. The further exception usually do give clue of the actual problem. I my case, the stack trace revealed the below issue Exception in thread "main" org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer] at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:110) at org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:135) at org.hibernate.tuple.entity.EntityEntityModeToTuplizerMapping. (EntityEntityModeToTuplizerMapping.java:80) at org.hibernate.tuple.entity.EntityMetamodel. (EntityMetamodel.java:323) at org.hibernate.persister.entity.AbstractEntityPersister. (AbstractEntityPersister.java:456) at org.hibernate.persister.entity.SingleTableEntityPersister. (SingleT...
Read more