[DROOLS-7025] Move "efesto" inside "drools" repo

bom/efesto-bom/pom.xml

@@ -0,0 +1,121 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+  <modelVersion>4.0.0</modelVersion>
+  <parent>
+    <groupId>org.kie</groupId>
+    <artifactId>kie-core-bom</artifactId>
+    <version>8.24.0-SNAPSHOT</version>
+    <relativePath>../kie-core-bom/pom.xml</relativePath>
+  </parent>
+
+  <artifactId>efesto-bom</artifactId>
+  <packaging>pom</packaging>
+
+  <name>Efesto BOM (Bill Of Materials)</name>
+  <description>
+    Import this BOM in your dependencyManagement if you want to depend on Efesto framework.
+  </description>
+
+  <url>https://www.drools.org</url>
+
+  <scm>
+    <connection>scm:git:https://github.com/kiegroup/drools.git</connection>
+    <developerConnection>scm:git:git@github.com:kiegroup/drools.git</developerConnection>
+    <url>https://github.com/kiegroup/drools</url>
+  </scm>
+  <issueManagement>
+    <system>jira</system>
+    <url>https://issues.jboss.org/browse/DROOLS</url>
+  </issueManagement>
+  <developers>
+    <developer>
+      <name>All developers are listed on the team website</name>
+      <url>http://www.drools.org/community/team.html</url>
+    </developer>
+  </developers>
+  <contributors>
+    <contributor>
+      <name>All contributors are listed on the team website</name>
+      <url>http://www.drools.org/community/team.html</url>
+    </contributor>
+  </contributors>
+  <mailingLists>
+    <mailingList>
+      <name>setup</name>
+      <subscribe>https://groups.google.com/forum/#!forum/drools-setup</subscribe>
+      <unsubscribe>https://groups.google.com/forum/#!forum/drools-setup</unsubscribe>
+    </mailingList>
+    <mailingList>
+      <name>usage</name>
+      <subscribe>https://groups.google.com/forum/#!forum/drools-usage</subscribe>
+      <unsubscribe>https://groups.google.com/forum/#!forum/drools-usage</unsubscribe>
+    </mailingList>
+    <mailingList>
+      <name>development</name>
+      <subscribe>https://groups.google.com/forum/#!forum/drools-development</subscribe>
+      <unsubscribe>https://groups.google.com/forum/#!forum/drools-development</unsubscribe>
+    </mailingList>
+  </mailingLists>
+
+  <!-- IMPORTANT: Do not declare any build things here! Declare them in kie-user-bom-parent. -->
+  <build/>
+
+  <dependencyManagement>
+    <dependencies>
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-common-utils</artifactId>
+        <version>${project.version}</version>
+      </dependency>
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-common-api</artifactId>
+        <version>${project.version}</version>
+      </dependency>
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-compilation-manager-api</artifactId>
+        <version>${project.version}</version>
+      </dependency>
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-compilation-manager-core</artifactId>
+        <version>${project.version}</version>
+      </dependency>
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-runtime-manager-api</artifactId>
+        <version>${project.version}</version>
+      </dependency>
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-runtime-manager-core</artifactId>
+        <version>${project.version}</version>
+      </dependency>
+      <!-- ENGINES -->
+      <!-- External -->
+      <!-- Kie -->
+<!--      <dependency>-->
+<!--        <groupId>org.kie</groupId>-->
+<!--        <artifactId>kie-api</artifactId>-->
+<!--        <version>${project.version}</version>-->
+<!--      </dependency>-->
+<!--      <dependency>-->
+<!--        <groupId>org.kie</groupId>-->
+<!--        <artifactId>kie-memory-compiler</artifactId>-->
+<!--        <version>${project.version}</version>-->
+<!--      </dependency>-->
+      <!-- Logging -->
+      <!-- Test -->
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-runtime-manager-api</artifactId>
+        <version>${project.version}</version>
+        <classifier>tests</classifier>
+      </dependency>
+    </dependencies>
+  </dependencyManagement>
+
+</project>

bom/pom.xml

@@ -14,10 +14,11 @@
     <packaging>pom</packaging>
 
     <modules>
-        <module>kie-core-bom</module>
-        <module>drools-bom</module>
-        <module>kie-dmn-bom</module>
-        <module>kie-pmml-bom</module>
+      <module>kie-core-bom</module>
+      <module>drools-bom</module>
+      <module>efesto-bom</module>
+      <module>kie-dmn-bom</module>
+      <module>kie-pmml-bom</module>
     </modules>
 
 </project>

build-parent/pom.xml

@@ -1543,6 +1543,13 @@
         <type>pom</type>
         <scope>import</scope>
       </dependency>
+      <dependency>
+        <groupId>org.kie</groupId>
+        <artifactId>efesto-bom</artifactId>
+        <version>${project.version}</version>
+        <type>pom</type>
+        <scope>import</scope>
+      </dependency>
       <dependency>
         <groupId>org.kie</groupId>
         <artifactId>kie-dmn-bom</artifactId>

efesto/.gitignore

@@ -0,0 +1,2 @@
+!local/
+*.bak

efesto/README.md

@@ -0,0 +1,48 @@
+# Efesto
+-------------------------
+
+This module contains a rewriting of the `drools` framework, that is intended to be used to provide clear separation and composition for each compiler/runtime of the different engines that Drools project contains (Rules engine, DMN engine, PMML engine).
+The first step has been to include `efesto` as self-contained module inside `drools`.
+
+
+The main focus of this project is on:
+
+1. clear separation between "container" and "content" contexts; the "content" is represented by functionalities exposed
+   by the compile-time and runtime; the "context" is the environment in which such functionalities are invoked (
+   see [architectural choices](https://docs.google.com/document/d/1n9rKcMh0qnP7R4DUb3xqanFZcN0q7SL8aBRoAdQDSH0) for more
+   details)
+2. clear separation between compile-time and runtime
+3. uniform overall management of different models/engines
+
+Regarding the overall module organization/relationship, this project should follow the guidelines of the "Clean
+Architecture" principle.
+As per the design style, the microkernel-style will be featured, where each model/engine will represent a
+specific `plugin`.
+
+Each plugin should provide a `compilation` and a `runtime` component.
+
+The [documentation](./documentation) folder contains diagrams (PUML, Archimate), images, and other resources related to
+design/architectural choices.
+
+This effort can not be full-filled by a single person, since it involve decisions at every level and it will have an
+impact on the all `drools` codebase; everyone may be interested would be warmly welcomed for ideas, suggestions,
+criticism, contribution.
+
+
+ArchUnit
+========
+ArchUnit has been introduced to enforce (as much as possible) some general architectural and design guidelines.
+
+See [official documentation](https://www.archunit.org/userguide/html/000_Index.html) and [maven plugin information](https://github.com/societe-generale/arch-unit-maven-plugin) for further details.
+
+JDepend
+=======
+JDepend is a tool that traverses Java class file directories and generates design quality metrics for each Java package. JDepend allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to manage package dependencies effectively.
+See [official documentation](http://clarkware.com/software/JDepend.html">http://clarkware.com/software/JDepend.html)
+for details.
+
+
+
+
+
+