Download JAR files tagged by required with all dependencies

Box is an add-on framework for Java EE applications that performs asynchronous gathering of source data with subsequent processing or transformation of that data into output JSON documents and exposing those documents through a web API. Box excels at maintaining existing documents including keeping them up-to-date in real time and deleting them when required. Box supports aggregating data from multiple sources as well as splitting data into multiple documents. How documents are processed is left up to each application. The web api makes the documents available by ID or by harvesting all documents. Harvests can be filtered using facets and documents can be pared down by requesting only needed fields.

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.

A set of reflection utilities and miscellaneous utilities related to working with classes and their fields with no dependencies which is compatible with java 1.5 and generics. The package was originally created by Aaron Zeckoski for the Sakai Project and Generic DAO project but was repackaged to make it distributable by request. It is used in the RSF framework (http://www2.caret.cam.ac.uk/rsfwiki/) and the EntityBroker among other things. Note about the BeanUtils provided dependency: BeanUtils is not required if you are not using it in your project. Note about the Hibernate provided dependency: Hibernate is not required if you are not using it in your project.

What is jparsec? Jparsec is a recursive-desent parser combinator framework written for Java. It constructs parsers in native Java language only. Why yet another parser framework? Jparsec stands out for its combinator nature. It is no parser generator like YACC or ANTLR. No extra grammar file is required. Grammar is written in native Java /C# language, which also means you can utilize all the utilities in the Java/.Net community to get your parser fancy. What does "jparsec" stand for? Jparsec is an implementation of Haskell Parsec on the Java platform. Feature highlights. operator precendence grammar. accurate error location and customizable error message. rich set of pre-defined reusable combinator functions. declarative API that resembles BNF. [email protected] [email protected]

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

R can use RJava or jsr223 to communicate with java. R also has a class system called R6. If you want to use a java library with native rJava or jsr223 in R there is potentially a lot of glue code needed, and R library specific packaging configuration required. However if you don't mind writing an R-centric API in Java you can generate all of this glue code using a few java annotations and the normal javadoc annotations. This plugin aims to provide an annotation processor that writes that glue code and creates a fairly transparent connection between Java code and R code, with a minimum of hard work. The focus of this is streamlining the creation of R libraries by Java developers, rather than allowing access to arbitrary Java code from R. The ultimate aim of this plugin to allow java developers to provide simple APIs for their libraries, package their library using Maven, push it to github and for that to become seamlessly available as an R library, with a minimal amount of fuss. A focus is on trying to produce CI ready libraries tested with Github workflows and ready for CRAN submission.

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