Download JAR files tagged by loader with all dependencies

HTTP Loader is a simple project that uses okhttp (http://square.github.io/okhttp/), GSON (http://square.github.io/okhttp/) and Loaders (https://developer.android.com/reference/android/content/Loader.html) to make safe and lifecycling respectful HTTP requests.

RequireJS is a JavaScript file and module loader. It is optimized for in-browser use, but it can be used in other JavaScript environments, like Rhino and Node. Using a modular script loader like RequireJS will improve the speed and quality of your code.

Maven Runtime allows introspection of Maven project metadata at runtime. Basic artifact information or full Maven project metadata can be obtained for all projects within a given class loader, optionally sorted into dependency order, and also for a given class within a project.

This module generates an XML scheme file for the MINA Spring configuration namespace. This XSD is referenced by Spring configuration files using MINA components to have a much less verbose configuration. When used with the XBean application context loader the same old Spring ApplictionContext is generated from this more intuitive and terse configuration file.

composite REST app - this represents the baseline version that the Connect-Java repository uses for building microservice based REST apps. As they are all Jersey based, there is no real need for Spring or Guice. They always include Tracing, Prometheus, Health checks, Application Lifecycle, easy config injection, Bathe for application start with Service Loader initializers. We are focused on using JIB for Docker generation.

The class loader to load classes, native libraries and resources from the top JAR and from JARs inside the top JAR. The top JAR very often is referred as an executable, standalone or uber JAR. The class loader looks through the hierarchy of JARs and allows nested JARs. The class loader delegates class loading to the parent class loader and successfully loads classes, native libraries and resources when it works not in a JAR environment. Taken from http://www.jdotsoft.com/JarClassLoader.php, see there for more information.

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"

This is an endorsed version of the original Deployment Client for Oracle GlassFish Open Source Edition. The purpose of the endorsement is to provide a shaded JAR which has the OSGI meta data removed because it causes the original Deployment Client to fail when used within a module running within a GlassFish container due to some class loader configuration conflicts between the container and the deployed module. This issue has been reported to the GlassFish project at https://java.net/jira/browse/GLASSFISH-20856 . It is hoped that it can get fixed so that this workaround project can get deprecated soon.

This module creates two things: (1) a text file that contains a list of GAV coordinates needed for the 2nd stage boot loader (2) jar files mentioned above, in the Maven repository directory layout. Using Maven repository directory layout, as opposed to more simpler "flat directory with full of jars", allow us to share the jar files between fallback bees-driver dependencies and boot2, which saves disk space a lot. We do this in a separate module outside boot2, so that the list includes the bees-boot2 jar itself.

Tool used to generate the preferred class information for downloadable JAR files in the form of a META-INF/PREFERRED.LIST required for use by the {@link net.jini.loader.pref.PreferredClassLoader}. The list is generated by examining the dependencies of classes contained within a target JAR file and zero or more additional supporting JAR files. Through various command-line options, a set of "root" classes are identified as belonging to a public API. These root classes provide the starting point for recursively computing a dependency graph, finding all of the classes referenced in the public API of the root classes, finding all of the classes referenced in turn by the public API of those classes, and so on, until no new classes are found. The results of the dependency analysis are combined with the preferred list information in the additional supporting JAR files to compute a preferred list having the smallest number of entries that describes the preferred state of the classes and resources contained in all of the JAR files. The output of the tool is a new version of the target JAR file containing the generated preferred list, and/or a copy of the list printed to System.out.