Download JAR files tagged by rules with all dependencies

The ServiceMix Drools component provides JBI integration to the Drools Rules Engine. It can be used to deploy a rules set that will implement a router or an actual service. A router will mostly act as a transparent proxy between the consumer and the target service provider mad will mostly be implemented by the jbi.route(uri) method below. This method creates a new exchange identical to the one received by the component and will send it to the specified destination. You can also send back a Fault if needed. A router can also be implemented by using directly the JBI Apis (available with the jbi helper) by using the provided client.

An implementation of a RIpple-DOwn Rule learner. It generates a default rule first and then the exceptions for the default rule with the least (weighted) error rate. Then it generates the "best" exceptions for each exception and iterates until pure. Thus it performs a tree-like expansion of exceptions.The exceptions are a set of rules that predict classes other than the default. IREP is used to generate the exceptions. For more information about Ripple-Down Rules, see: Brian R. Gaines, Paul Compton (1995). Induction of Ripple-Down Rules Applied to Modeling Large Databases. J. Intell. Inf. Syst. 5(3):211-228.

Lazy Bayesian Rules Classifier. The naive Bayesian classifier provides a simple and effective approach to classifier learning, but its attribute independence assumption is often violated in the real world. Lazy Bayesian Rules selectively relaxes the independence assumption, achieving lower error rates over a range of learning tasks. LBR defers processing to classification time, making it a highly efficient and accurate classification algorithm when small numbers of objects are to be classified. For more information, see: Zijian Zheng, G. Webb (2000). Lazy Learning of Bayesian Rules. Machine Learning. 4(1):53-84.

Kanbanery (https://kanbanery.com) is a simple but powerful Agile project management system, to be precise it focuses around the idea of Kanban, a somewhat near idea to SCRUM but with less strict rules. The heart of each Kanban flow is the Kanban board, IceBox and Archive - there are all easy accessible via this API. Janbanery wraps around the RESTful API delivered by Kanbanery while adding some more features like mass operations or filtering of results. In the end, it's very easy and pleasant to implement your own Kanbanery client be it on the desktop, mobile (android) or as for example Gradle / SBT script to take full advantage of kanbanery's features.

Kanbanery (https://kanbanery.com) is a simple but powerful Agile project management system, to be precise it focuses around the idea of Kanban, a somewhat near idea to SCRUM but with less strict rules. The heart of each Kanban flow is the Kanban board, IceBox and Archive - there are all easy accessible via this API. Janbanery wraps around the RESTful API delivered by Kanbanery while adding some more features like mass operations or filtering of results. In the end, it's very easy and pleasant to implement your own Kanbanery client be it on the desktop, mobile (android) or as for example Gradle / SBT script to take full advantage of kanbanery's features.

This repository contains various third party sources required by the main retepTools repository. The reason for this is when they are only available in SNAPSHOT format and we require a release version to enable us to run a release. Although not ideal, this is sometimes necessary if some critical bug needs to be fixed. Currently this contains docbkx-tools. Rules for this repository: * Projects must follow the same licensing as the main project :- BSD, Apache2 etc but not GPL, LGPL etc * groupId's must be within the uk.org.retep.third-party namespace - and not the projects original namespace (so we don't have version conflicts) * Must be disabled/removed once those projects become stable

JBoss Rules provides an open source and standards-based business rules engine that enables easy business policy access, change and management. JBoss Rules is a fast and highly efficient rules engine that makes it easy for a business analyst or auditor to view your business rules as encoded in your IT application infrastructure to verify that the encoded rules indeed implement the documented business policies. JBoss Rules also supports a variety of language and decision table inputs, making it easy to quickly modify your business policies to respond to opportunities and competitive threats.

JBoss Rules provides an open source and standards-based business rules engine that enables easy business policy access, change and management. JBoss Rules is a fast and highly efficient rules engine that makes it easy for a business analyst or auditor to view your business rules as encoded in your IT application infrastructure to verify that the encoded rules indeed implement the documented business policies. JBoss Rules also supports a variety of language and decision table inputs, making it easy to quickly modify your business policies to respond to opportunities and competitive threats.

How many classes does it take to make a cache? 60? 80? You might think so if you look at the other caches on the market. Ashkay is a streamlined, simple cache that in many ways is more powerful than the other mainstream caches. Ashkay is a strategy based caching tool. In most cases, you might be using a configuration file to tell the cache what rules it should obey. Or, you might just be setting properties on the cache. I have never liked this model as it limits me, the user of the cache to strategies the developer decided were important. Instead, Ashkay lets you choose the strategy(ies) to use when caching certain objects. Of course, a few of the most handy strategies are pre-packaged, but implementing a new one is a simple as can be. Ashkay is a fork of <a href="http://xot.sf.net">xot</a> caching code. Made more sense on its own.