Download JAR files tagged by environment with all dependencies

According to Docker best practices a Docker container should not be up if the process fails to load properly. Apache Tomcat deploys all the web applications loaded in its webapp folder. This is a resilient solution for web applications not influencing the application server. However, In a Docker environment according to best practice, the process should fail in case the web application failed to initialize properly. By adding the additional jar created by this project to Tomcat classpath and adding the new listener in the Tomcat conf/server.xml the user can make sure the Tomcat process fails in case there is an initialization exception in their web application which will cause the Tomcat used the tomcat container to abort in immediately indicate that there was an initialization error Abort tomcat when a webapp fails to deploy in Docker container Docker container best practice. Tomcat does not stop if a webapp fail to deploy and the container will continue to run. By adding this listener the tomcat will abort in case the Tomcat fails to deploy the webapp, And the container will not start. You will need to place the listener in Tomcat server.xml and set the Tomcat classpath to contain this jar

Maven plugin for small application config support. Allows you to define configuration for your application at one place and generate config files and java class. Configuration can be instantiate by var args, file config or environment variables or combination of all. ISSUES: -v potomkovi mam rucne psanou pomocnou property, ta se nesmi dostat do property descriptoru, pak je tam s klicem null -pokud reloadArgs byposition vrati null, vyhodit hned vyjimku - confDef = byOrder.get(iPos++); TODO: - boolean opts -- is/get -- option without value true - make def enum public - static instance to access from everywhere without pass an instance -static enum Def -more executions with different configuration has conflict in options and names

The Jeuron Application Platform is a lightweight framework to assemble software components intended to support multiple project and deployment scenarios while also providing an environment for testing and debugging. The platform is comprised of a set of packages which provide transport, messaging, configuration, and execution services designed to create a configurable, scalable, and distributed application environment. The low resource model permits the platform to be instantiated during each build cycle and to be deployed at all levels of the application hierarchy such as application servers, web servers, and mobile or wired workstations.

This module contains a classpath scanner, and bytecode reader. It is useful in any java runtime environment, and allows java code to parse bytecode into a meta structure of classes, annotations, methods and fields. This meta structure is used throughout xapi to allow us to extend java structures in a cross-platform compliant way (exposing services and service objects so you can hack support for whatever runtime you need). It is especially useful for fast runtime injection, and as an extensible structure during codegen (which exposes mutable interfaces for our meta structure)

snmpAdaptor4j is an adaptor for Java Management eXtensions (JMX) providing a simple access to MBeans via the SNMP protocol. Thus, this adapter you allow to connect most monitoring tools (like Nagios and Cacti) to your Java applications. For each MBean, an XML mapping file allows to establish the relationships between attributes and the MIB of the SNMP adapter. No additional code is necessary to integrate the MBeans in the SNMP protocol. This adapter can work in a multi-applications environment (such as application servers).

This module was created to fix issue DIRSHARED-91 where the embedded Felix instance inside the default LdapCodecService implementation was making it very problematic to deploy the ldap-codec inside an RCP (OSGi) environment and hence Apache Directory Studio could not use it. This module is most likely temporary and will disappear once we are fully OSGi enabled. This module is a plain old jar, not a bundle to avoid accidental reuse as an OSGi module because it contains the version of the LdapCodecService that embeds Felix to make controls and extended ops pluggable in the codec.

This plugin will support various tasks within the Weblogic 8.1, 9.x, 10.x and 12.x environment. This version starts to support weblogic 10 and 11. The mojo supports such tasks as deploy, undeploy,clientgen,servicegen, and appc are supported as well as many others. The plugin uses exposed API's that are subject to change but have been tested in 8.1 SP 4-6 and 9.0 - 9.2 MP3, 10.x. There are two versions of the plugin to support the two environments based on differences in the JDK. The 9.x version is currently being refactored to support the standard JSR supported deployment interface. The code used in the plugin has been contributed to the Cargo project however to date has not be integrated into the codebase. Please feel free to suggest improvements or help support this plugin effort.