Download JAR files tagged by have with all dependencies

[](https://drone.io/bitbucket.org/tidalwave/tidalwave-superpom-src/latest) The super POM for all Tidalwave projects. It is not designed for being used by others, as it contains some corporate-specific configurations, but its ancestor [TheseFooolishThings SuperPOM](http://bitbucket.org/tidalwave/thesefoolishthings-superpom-src) has been designed to be reusable. Please have a look at it. This super POM adds to its ancestor: + some Tidalwave variables that refers to the issue tracker, continuous integration system, etc...; + the definitions of versions of a number of commonly used libraries and their dependency management: * [AspectJ](https://www.eclipse.org/aspectj) * [Hamcrest Matchers](http://hamcrest.org/JavaHamcrest) * [JSR 330](https://github.com/google/guice/wiki/JSR330) * [Jakarta XML Binding (JAXB)](https://eclipse-ee4j.github.io/jaxb-ri/) * [Spotbugs annotations](https://spotbugs.readthedocs.io) * [JUnit](https://junit.org/junit5) * [Logback](http://logback.qos.ch) * [Lombok](https://projectlombok.org) * [SLF4J](slf4j.org) * [Spring 5](https://spring.io/projects/spring-framework) * [TestNG](https://testng.org) + the definition for Tidalwave 3rd party repository (stuff that is not available on Maven Central); + a profile for using the [TheseFoolishThings](http://tidalwave.it/projects/thesefoolishthings) Event Bus (```it.tidalwave-spring-messagebus-v1```); + profiles for the [Mycila License plugin](https://github.com/mycila/license-maven-plugin); + configuration of the UMLGraphDoc maven plugin; + the configuration for the TheseFoolishThings TestNG listener (which provides enhanced test logging); + definitions of some custom javadoc tags; + a blacklist for some old artifacts; + some other minor customisations.

Jadex Rules is a small lightweight rule engine, which currently employs the well-known Rete algorithm for highly efficient rule matching. Jadex rules is therefore similar to other rule engines like JESS and Drools. Despite the similarities there are also important differences between these systems: * Jadex Rules is very small and intended to be used as component of other software. Even though rules can be specified in a Java dialect as well as (a small variation of) the CLIPS language its primary usage is on the API level. Jadex Rules is currently the core component of the Jadex BDI reasoning engine. * Jadex Rules cleanly separates between state and rule representation. This allows the state implementation as well as the matcher to be flexibly exchanged. Some experiments have e.g. been conducted with a Jena representation. Regarding the matcher, it is planned to support also the Treat algorithm, which has a lower memory footprint than Rete. * Jadex Rules pays close attention to rule debugging. The state as well as the rete engine can be observed at runtime. The rule debugger provides functionalities to execute a rule program stepwise and also use rule breakpoints to stop the execution at those points.

Java Prolog Interface (JPI) is an Application Provider Interface (API) for interaction between Java and Prolog programming languages. Is a bidirectional interface that communicate Java applications with Prolog program or database and Prolog procedures with Java class and methods. JPI is an abstraction layer over concrete prolog drivers over Prolog Engines. This API define all mechanism to interact with any Prolog Engine and maintain the application independent to a specific underlying engine. JPI have several connectors to open source prolog engines like SWI, YAP, XSB native engines and tuProlog, jTrolog, jLog Java based prolog engines. JPI study all related Java-Prolog integration libraries and take the betters features from each solution with the propose to achieve a common integration interface. The last feature allows switch the under laying Prolog Engine driver and the application code still be the same. JPI run over any Java Virtual Machine that support Java SE 5 or above. The project was tested over HotSpot, Open J9 and JRockit Virtual Machines over Operating Systems like Windows (7,8,10), Linux (Debian, Ubuntu) and Mac OS X. Can be deployed on Servlets Containers like Jetty, Tomcat or Glassfish Application Server. JPI can be include in any Java Project using the commonest Java Integration Development Enviroment (IDE) like Eclipse, Netbeans, IntelijIDEA and so on. JPI is developed and maintained by Prolobjectlink Project an open source initiative for build logic based applications using Prolog like fundamental Logic Programming Language in the persistence layer and application programming.