Download JAR files tagged by scenario with all dependencies

ShareTrace focuses on providing technical solutions for app promotion. Carry parameters to install the app, accurately track the source of app installation, achieve no fill-in invitation code, distinguish promotion channels and other common app Promotion Scenario. Make app promotion more efficient at a low cost.

The Cucumber Slices Plugin is designed to parse Cucumber feature files with 1 or more scenarios into many feature files, each with 1 scenario per feature file. Each parsed feature file is associated with a Cucumber runner file that is generated at runtime. The Cucumber runner files can be executed in parallel using Maven's Surefire or Failsafe Plugin.

Plugin to simplify the process of ingesting workflow documents into Rice. At the moment, this plugin is still very much in beta. It works correctly when ingesting Kuali OLE workflow documents into a MySQL database using Rice 1.0.3.3. Usage outside of that specific scenario is untested.

AI pipeline module include pipelines connecting the OAP kernel and any 3rd party AI and/or algorithm server. The kernel would call the pipeline in the specific context/scenario with well formatted telemetry data, and expect the remote to respond with the result of the AI/algorithm as quick as possible, but in async way in case of large size of data or lower performance behavior of the remote.

Simulation for Heterogeneous and Autonomic NetworkS (SHANKS). SHANKS is a framework to simulate different network scenarios in order to add autonomic capabilities using MASON simulation framework. To achieve this goal, a multi-agent system (MAS) is used to handle possible situations in the scenario. These agents are able to analyse environment data, perform inference and self-healing actions, etc.

There are two ways to use OSGi in server-side[1]. In Carbon, what we have done is, embedding an OSGi framework inside a servlet container. So BridgeServlet delegates all the request from the servlet container to the HttpServiceServlet registered by the http.bridge bundle. This is required only when Carbon is running inside a webapp. There is a possibility to embed an HTTP server(ex. jetty) inside equinox and start a server with all our carbon bundles. This is same as running carbon inside spring DM server. For this scenario, we do not need org.wso2.carbon.http.bridge bundles and the org.wso2.carbon.bridge extension bundle. 1. http://eclipse.org/equinox/server/http_quickstart.php

HotSpot learns a set of rules (displayed in a tree-like structure) that maximize/minimize a target variable/value of interest. With a nominal target, one might want to look for segments of the data where there is a high probability of a minority value occuring (given the constraint of a minimum support). For a numeric target, one might be interested in finding segments where this is higher on average than in the whole data set. For example, in a health insurance scenario, find which health insurance groups are at the highest risk (have the highest claim ratio), or, which groups have the highest average insurance payout.

This ApplicationProperties Java package provides a fast and easily configurable application.properties loader that mimics some key features of the Spring Boot application.properties loader. This package allows for multi-level overloading of properties based on a basename and optional suffix by searching the classpath, optional configurable file paths along with the JNDI server container context. The class [ApplicationPropertiesConfig](src/main/java/com/lyders/application-properties/ApplicationPropertiesConfig.java) controls the features of the overloading of properties such as the base name of the properties file, an optional suffix that allows for the loading of environment-specific or scenario-specific property files as needed. The following features are supported: * Names of properties files can be customized * Locations of properties files can be customized. The following path types are supported: * class path * file system paths * JNDI environment naming context (e.g., Servlet/JSP running under Tomcat) * Environment-specific property files can override the values in default properties files via a "suffix"

BEhavioural Agents Simple Testing Tool - BEAST Tool The aim of this project is the development of a system which allows Behavior Driven Development (BDD) in Multi-Agent Systems (MAS), to make testing practices more accessible and intuitive to everybody. In one hand, in order to let tests be writable by newcomers and experts alike, system must allow the redaction of tests in plain text, because client does not need to have knowledge of our code. This plain text will be traduced to software later. The definition of test will be realized with the terminology Given-When-Then, which allows trace an easy guide of the behavior of a given scenario when something happened. In the other hand, due to the complexity of MAS, making unit testing of an agent that needs the interaction with others is almost impossible until the whole system is finished. This implies to leave testing issues to the end of the project, generating big troubles in case of malfunction. Consequently, its necessary to carry out a tool to allow the creation of mock agents and to perform tests during the whole development process. Therefore another objective of our systems is to include a mocking tool which permits testing continuously. Definitively, our tool allows the testing of any MAS in the development process, increasing its modularity and decreasing its elaboration and testing cost. These tests will be written in plain text so that anyone would be able to understand them. For further reading, a paper published in ITMAS2012 workshop can be found in: http://scholar.google.es/citations?view_op=view_citation&hl=es&user=mT3KgXUAAAAJ&citation_for_view=mT3KgXUAAAAJ:Tyk-4Ss8FVUC