Download JAR files tagged by install with all dependencies

Easy to install library for adding dynamic display, control and configuration of java.util.logging to any swing based application. Useful for debugging apps in production situations; can interactively configure logging while an application is running including adding a handler to save logging output to a file. Changes made to an application's default/startup logging can be saved and automatically applied at startup. LogMan "single" library package for use in swing apps. The jar can be executed, "java -jar xxx", for a demo of the library. See com.raelity.logman.demo.Main for an example of adding the library to a swing app.

Use the Branch SDK (branch.io) to create and power the links that point back to your apps for all of these things and more. Branch makes it incredibly simple to create powerful deep links that can pass data across app install and open while handling all edge cases (using on desktop vs. mobile vs. already having the app installed, etc). Best of all, it is really simple to start using the links for your own app: only 2 lines of code to register the deep link router and one more line of code to create the links with custom data.

The AppOptics Java instrumentation agent jar file. This artifact provides a convenient way to download the agent jar from public Maven repository. Please take note that this should NOT be included as a part of the project dependencies. Rather, this artifact should be integrated into the build process by using extra step such as the "copy" goal of "maven-dependency-plugin". For more information, please refer to https://docs.appoptics.com/kb/apm_tracing/java/install/#getting-the-agent-jar

<p>Integrate the Mantis bugtracker system into netbeans</p> <p>Note for installation - to make the "Add patch" and "Checking" comment functions work correctly the mantis system has to configured correctly please check these options, if you encounter problems:</p> <ul> <li>source_control_notes_view_status (default private, integer value 10 -> public)</li> <li>source_control_set_resolution_to (integer value 80->resolved, 90->closed)</li> <li>source_control_set_status_to (20->fixed)</li> </ul> <p>If a self-signed SSL certificate or an invalid certificate need to be accepted, please install the module "SSL Certificate Exception".</p>

Bundle with a synchronous activator which will install OGEMA resources from XML (.ogx) or JSON (.ogj) files located in config/resources (default). This requires a running OGEMA framework when the bundle is started and enables the installation of basic resources before other applications are activated. Also adds a service for felix fileinstall that will install such resource files. Files installed through fileinstall will be reinstalled when they are updated or when a newer version of an installed file is found after a restart (using the file's last modification timestamp). Files installed from the configuration directory will only be reinstalled on a restart, if they have been changed.

jpm4j is Just another Package Manager for Java. It stills the envy of all Java developers of Ruby with their Gems, Perl with its cpan, and Python with its pips. jpm makes it very easy to deploy Java applications on a myriad of platforms. This program is the command line application that performs the front end of the https://www.jpm4j.org website. It provides full access to the repository index (i.e. jpm find osgi), it can be used to install, etc. Use jpm help to see all the commands.

GroupDocs.Total for Cloud is a suite of RESTful APIs that allows developers to seamlessly add powerful document collaboration functionality to their web/mobile applications or sites. With GroupDocs.Total, you can enable end users to view, collaboratively annotate, compare, convert, e-sign, assemble and securely share over 50 document and image types (including PDF and Microsoft Office) on the web, all without having to install any 3rd-party office software or browser plugins. With this SDK, you can easily customize and integrate GroupDocs’ document collaboration tools into your web or mobile Java application.

OpenCms-Module 'org.opencms.editors.fckeditor'. <p>This module adds the popular Open Source HTML editor "FCKeditor" to the OpenCms Workplace.</p> <p>Install this module if you want a WYSIWYG editor for Mozilla based browsers, Internet Explorer, Safari or Google Chrome. The version of FCKeditor is 2.6.5</p> <p><i>&copy; 2013 by Alkacon Software GmbH (http://www.alkacon.com).</i></p> OpenCms is a Content Management System that is based on Open Source Software. Complex Intranet and Internet websites can be quickly and cost-effectively created, maintained and managed.

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

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 Hibersap 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=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=path/to/sapjco3.jar (b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=sapjco3.jar