Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4770

New version of lockback-core is not compatibile with our slf4j-api version

    XMLWordPrintable

Details

    • RC1
    • CR2
    • Hide

      Run this test: org.jbpm.persistence.processinstance.ProcessInstanceResolverStrategyTest.testWithDatabaseAndStartProcess

      Show
      Run this test: org.jbpm.persistence.processinstance.ProcessInstanceResolverStrategyTest.testWithDatabaseAndStartProcess

    Description

      New version of logback core (RHBRMS-2766) causes failing several tests with NoClassDefFoundError, which makes this issue test blocker:

      java.lang.NoClassDefFoundError: org/slf4j/event/LoggingEvent
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.getDeclaredMethods0(Native Method)
	at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
	at java.lang.Class.privateGetPublicMethods(Class.java:2902)
	at java.lang.Class.getMethods(Class.java:1615)
	at org.drools.persistence.jpa.marshaller.JPAPlaceholderResolverStrategy.isEntity(JPAPlaceholderResolverStrategy.java:217)
	at org.drools.persistence.jpa.marshaller.JPAPlaceholderResolverStrategy.accept(JPAPlaceholderResolverStrategy.java:79)
	at org.drools.core.marshalling.impl.ObjectMarshallingStrategyStoreImpl.getStrategyObject(ObjectMarshallingStrategyStoreImpl.java:75)...

      Cause: Logback-classic version 1.1.4 and later require slf4j-api version 1.7.15 or later. [1]

      Note: After fixing this issue PR https://github.com/kiegroup/jbpm/pull/860 should be reverted.

      [1] https://www.slf4j.org/codes.html#log4j_version

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHBRMS-2838 New version of lockback-core is not compatibile with our slf4j-api version

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              mbiarnes@redhat.com Michael Biarnes Kiefer
              mcimbale@redhat.com Martin Cimbalek
              Martin Cimbalek Martin Cimbalek
              Martin Cimbalek Martin Cimbalek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: