Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2016.8
    • Component/s: None
    • Labels:
      None

      Description

      slf4j binding uses the class loader to find it's binding. If the logging fraction is present the binding should be org.jboss.logmanager:slf4j-jboss-logmanager which is present the modules directory of the archive. However if the the module requesting the binding is located in the m2repo/org/wildfly/swarm/*-modules path it likely only has the org.slf4j module dependency and for some reason the paths don't include the binding.

      The logging-modules.jar does seem to include the correct module.xml so I'm not sure how the resolution of modules works. Maybe there is an issue because the org.slf4j and org.slf4j.impl dependencies are circular dependencies.

      logging-modules module.xml
      <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
      <module xmlns="urn:jboss:module:1.3" name="org.slf4j">
      <resources>
          <artifact name="org.slf4j:slf4j-api:1.7.7.jbossorg-1"/>
        </resources>
        <dependencies>
          <module name="org.slf4j.impl"/>
        </dependencies>
      </module>
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jamezp James Perkins
                Reporter:
                jamezp James Perkins
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: