Download JAR files tagged by users with all dependencies

The JXTA Shell is a sample application that demonstrates key concepts of JXTA JXSE. The JXTA Shell enables users to interact with the JXTA platform through a command-line interpreter. Much like the UNIX® shell, the JXTA Shell is useful for accessing and managing core platform objects (peers, groups, pipes), debugging communications problems, checking the status of peers and/or peer groups, and communicating with other JXTA services and applications. As in UNIX®, the JXTA shell allows users to "pipe" shell commands together connecting commands "on-the-fly." Pipes in Project JXTA are useful for collecting information at one peer and perhaps processing the command at another.

A NSGA-II implementation using Java. This implementation of NSGA-II algorithm is in pure reference to the original published paper. This is not an effort to convert the originally implemented C code in Java. The original C code by the authors has not be referred to while writing this implementation. This is a fully customizable implementation of the NSGA-II algorithm, made as generic as possible. This documentation assumes you have basic understanding of the NSGA-II algorithm. Apart from the core concepts of the algorithm, everything else in this package can be implemented as per the user's choice and plugged into the algorithm dynamically. Since NSGA-II is more like a set of protocols to follow as an algorithm rather than a concrete implementation of every aspect, this package has been re-written from scratch keeping complete customizability in mind. Apart from the core concepts of the algorithm, everything is considered to be a plugin external to the algorithm that can be implemented by the user and dynamically plugged into the algorithm during runtime as needed. This opens up the possibility of the package to be used simply as a PoC or be converted into something much more complex according to the users needs.

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 a value representing the OWLAPI release it is compatible with. Note that the group id for the upstream HermiT is com.hermit-reasoner, while this fork is released under net.sourceforge.owlapi. This fork exists to allow HermiT users to use newer OWLAPI versions than the ones supported by the original HermiT codebase. 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.

relay-jdbc allows a JDBC connection to be relayed through an intermediate relay server: it is both a JDBC driver (client) and a JDBC relay server. It is a fork of https://github.com/AugeoSoftware/VJDBC project, where Aleksei Yu. Semenov has implemented a number of brilliant improvements of the orignal VJDBC project hosted on http://vjdbc.sourceforge.net Original Developers were: Hunter Payne ([email protected]) and Michael Link ([email protected]). For all pre-existing code, credits go to the original respective author. This product brings the original VJDBC concept further and (apart from code quality improvements and bug fixes) implements complete separation of the underlying transport mechanism, introducing support for connecting directly through a SSH pipe, where the relay server interacts with the client through standard I/O pipes. The re-designed transport architecture supports easy development of new transport implementations, allowing this JDBC relay to be quickly adapted to a variety of exotic environments.

The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system. It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java to SAP System as well as SAP System to Java calls. - All SAP Connectors are licensed without additional license fees as part of the respective solution or component license. However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems / SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed. - The redistribution of any connector is not allowed. - All SAP users accessing application functionality through the relevant connector are required to be licensed under a respective solution or component license. To use the SAP JCo with the jco-jar project, you need to either install the SAP JCo jar downloaded from SAP to your local Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b): (a) mvn install:install-file -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar (b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar

Luzzu is a Quality Assessment Framework for Linked Open Datasets. It is a generic framework based on the Dataset Quality Ontology (daQ), allowing users to define their own quality metrics. Luzzu is an integrated platform that: - assesses Linked Data quality using a library of generic and user-provided domain specific quality metrics in a scalable manner; - provides queryable quality metadata on the assessed datasets; - assembles detailed quality reports on assessed datasets. Furthermore, the infrastructure: - scales for the assessment of big datasets; - can be easily extended by the users by creating their custom and domain-specific pluggable metrics, either by employing a novel declarative quality metric specification language or conventional imperative plugins; - employs a comprehensive ontology framework for representing and exchanging all quality related information in the assessment workflow; - implements quality-driven dataset ranking algorithms facilitating use-case driven discovery and retrieval.