Download JAR files tagged by within with all dependencies

Ganymed SSH-2 for Java is a library which implements the SSH-2 protocol in pure Java (tested on J2SE 1.4.2 and 5.0). It allows one to connect to SSH servers from within Java programs. It supports SSH sessions (remote command execution and shell access), local and remote port forwarding, local stream forwarding, X11 forwarding, SCP and SFTP. There are no dependencies on any JCE provider, as all crypto functionality is included. Originally, Ganymed SSH-2 for Java was developed for the Ganymed replication project at ETH Zurich (Switzerland). Downloads and more information about JSch may be found at http://www.cleondris.ch/opensource/ssh2/. This library is the provider bridge for SSHAPI.

FunctionExecutors 1. GeoWithinFunctionExecutor Input : (longitude double, latitude double, geoJSONGeometryFence string) OR (geoJSONGeometry string, geoJSONGeometryFence string) Output : true if (longitude, latitude) or geoJSONGeometry is within the geoJSONGeometryFence 2. GeoIntersectsFunctionExecutor Input : (longitude double, latitude double, geoJSONGeometryFence string) OR (geoJSONGeometry string, geoJSONGeometryFence string) Output : true if (longitude, latitude) or geoJSONGeometry intersects the geoJSONGeometryFence 3. GeoWithinDistanceFunctionExecutor Input : (longitude double, latitude double, geoJSONGeometryFence string, distance double) OR (geoJSONGeometry string, geoJSONGeometryFence string, distance double) Output : true if (longitude, latitude) or geoJSONGeometry is within distance of the geoJSONGeometryFence StreamProcessors 1. GeoCrossesStreamProcessor Input : (id string, longitude double, latitude double, geoJSONGeometryFence string) OR (id string, geoJSONGeometry string, geoJSONGeometryFence string) Output : an event with `crosses` additional attribute set to true when the object ((longitude, latitude) or geoJSONGeometry) crosses into geoJSONGeometryFence and an event with `crosses` additional attribute set to false when the object crosses out of the geoJSONGeometryFence 2. GeoStationaryStreamProcessor Input : (id string, longitude double, latitude double, geoJSONGeometryFence string, radius double) OR (id string, geoJSONGeometry string, geoJSONGeometryFence string, radius double) Output : when the object ((longitude, latitude) or geoJSONGeometry) starts being stationary within the radius an event with `stationary` additional attribute set to true. When the object starts to move out of the radius an event with `stationary` additional attribute set to false. 3. GeoProximityStreamProcessor Input : (id string, longitude double, latitude double, geoJSONGeometryFence string, radius double) OR (id string, geoJSONGeometry string, geoJSONGeometryFence string, radius double) Output : when two objects ((longitude, latitude) or geoJSONGeometry) starts being in close proximity within the radius an event with `inCloseProximity` additional attribute set to true. When the object starts to move out of the radius an event with `inCloseProximity` additional. attribute set to false. On each event, additional attributes `proximityWith` gives the id of the object that this object is in close proximity and `proximityId` is an id unique to the pair of objects

ISO 13616-1:2007 specifies the elements of an international bank account number (IBAN) used to facilitate the processing of data internationally in data interchange, in financial environments as well as within and between other industries. The IBAN is designed for automated processing, but can also be used conveniently in other media interchange when appropriate (e.g. paper document exchange, etc.). ISO 13616-1:2007 does not specify internal procedures, file organization techniques, storage media, languages, etc. to be used in its implementation, nor is it designed to facilitate the routing of messages within a network. It is applicable to the textual data which might be conveyed through a system (network). This project provides a general purpose ISO 13616-1:2007 compatible IBAN Java class.

The TraceView Java instrumentation agent. Contains the required jar, configuration file and native libraries for Windows and Linux. TraceView provides application performance monitoring for Java web apps through this agent. The files contained here allow for event tracking within your application to identify latency timings between your application layers. More options can be found here: http://docs.traceview.solarwinds.com/Instrumentation/java.html#configuring-instrumentation. For other information on our Java agent please visit http://docs.traceview.solarwinds.com/Instrumentation/java.html.

The AppNeta Java instrumentation agent. Contains the required jar, configuration file and native libraries for Windows and Linux. AppNeta provides application performance monitoring for Java web apps through this agent. The files contained here allow for event tracking within your application to identify latency timings between your application layers. More options can be found here: https://docs.appneta.com/java#configuring-instrumentation. For other information on our Java agent please visit https://docs.appneta.com/java.

iServe Integrated Engine provides a complete an integrated local version of iServe to be used within Java Applications. This module provides integrated programmatic access for the deployment and interaction with iServe engines. iServe is what we refer to as service warehouse which unifies service publication, analysis, and discovery through the use of lightweight semantics as well as advanced discovery and analytic capabilities. iServe provides the typical features of service registries and additional functionality that exploits service descriptions, service annotations and further data gathered and derived from the analysis of these descriptions, data crawled from the Web, periodic monitoring and user activities.

The Infinispan Spring Integration project provides Spring integration for Infinispan, a high performance distributed cache. Its primary features are * An implementation of org.springframework.cache.CacheManager, Spring's central caching abstraction, backed by Infinispan's EmbeddedCacheManager. To be used if your Spring-powered application and Infinispan are colocated, i.e. running within the same VM. * An implementation of org.springframework.cache.CacheManager backed by Infinispan's RemoteCacheManager. To bes used if your Spring-powered application accesses Infinispan remotely, i.e. over the network. * An implementation of org.springframework.cache.CacheManager backed by a CacheContainer reference. To be used if your Spring- powered application needs access to a CacheContainer defined outside the application (e.g. retrieved from JNDI) * Spring namespace support allowing shortcut definitions for all the components above In addition, Infinispan Spring Integration offers various FactoryBeans for facilitating creation of Infinispan core classes - Cache, CacheManager, ... - within a Spring context.

The Jenkins Maven Plugin allows to use the Jenkins CLI (command line interface) from within a Maven build. It allows the execution of any command supported by the CLI, see https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI for further information. Therefore, it downloads the current jenkins-cli.jar from ${project.ciManagement.url}/jnlpJars/jenkins-cli.jar and uses that artifact for interacting with the Jenkins server. The architecture of the Jenkins Maven Plugin follows the UNIX philosophy "do one thing and do it well": it does not provide any logic for specific tasks, for instance creating job configuration files. This can be done with another, more appropriate plugin and its result can then be specified as stdin to the Jenkins Maven Plugin.

An instance filter that collapses instances with a common grouping ID value into a single instance. Useful for converting transactional data into a format that Weka's association rule learners can handle. IMPORTANT: assumes that the incoming batch of instances has been sorted on the grouping attribute. The values of nominal attributes are converted to indicator attributes. These can be either binary (with f and t values) or unary with missing values used to indicate absence. The later is Weka's old market basket format, which is useful for Apriori. Numeric attributes can be aggregated within groups by computing the average, sum, minimum or maximum.

HermiT is reasoner for ontologies written using the Web Ontology Language (OWL). Given an OWL file, HermiT can determine whether or not the ontology is consistent, identify subsumption relationships between classes, and much more. This is the maven build of HermiT and is designed for people who wish to use HermiT from within the OWL API. It is now versioned in the main HermiT version repository, although not officially supported by the HermiT developers. The version number of this package is a composite of the HermiT version and an value representing releases of this packaged version. So, 1.3.7.1 is the first release of the mavenized version of HermiT based on the 1.3.7 release of HermiT. This package includes the Jautomata library (http://jautomata.sourceforge.net/), and builds with it directly. This library appears to be no longer under active development, and so a "fork" seems appropriate. No development is intended or anticipated on this code base.