anchor.diff:  .. Copy `optaplanner-core-${version}.jar` and all its direct and transitive dependency jars into that new directory. Use "mvn dependency:tree" on each optaplanner artifact to discover all dependencies.
   .. Create the file `module.xml` in that new directory. Give it this content:
   +
  -
   [source,xml,options="nowrap"]
   ----
   <?xml version="1.0" encoding="UTF-8"?>
  
positive.code: </jboss-deployment-structure>
  ----
  
  Because of JBoss Modules' `ClassLoader` magic, you'll likely need to provide the `ClassLoader` of your classes <<solverConfigurationByXML,during the SolverFactory creation>>,
  so it can find the classpath resources (such as the solver config, score DRL's and domain classes) in your jars.
  
  
  [[integrationWithOSGi]]
  
negative.code: The `optaplanner-core` jar includes OSGi metadata in its `MANIFEST.MF` file to function properly in an OSGi environment too.
  Furthermore, the maven artifact `kie-karaf-features` contains a `features.xml` file that supports the OSGi-feature ``optaplanner-engine``.
  
  Because of the OSGi's `ClassLoader` magic, provide the `ClassLoader` of your classes <<solverConfigurationByXML,during the SolverFactory creation>>,
  so it can find the classpath resources (such as the solver config, score DRL's and domain classes) in your jars.
  
  [NOTE]
  