Download JAR files tagged by fail with all dependencies

This project is meant to simplyfy the usage of the excelent Configuration Admin and MetaType services for Felix OSGi. The bundle will create a service that allows other bundles to register an annotated interface. The ManagedProperties service will then create all the Metatype information, as well as ensuring that objects are cast to their right types. ManagedProperties also has a feature called Filters. A Filter is used to create an object, say a File, directly from a primitive Configuration Admin type. It can also contain logic, to allow the configuration to fail if, for example, a File doesn't exist.

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

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

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 component may be plugged into standard compile plugin of maven to compile JavaFX ( http://javafx.com/) sources. The component assumes that JavaFX SDK 1.2+ is installed on the machine were built process is run. Environment variable JFX_HOME should point to JavaFX installation directory (typically /usr/share/javafx-sdk1.2 for Linux machines). Version 0.3 is current one and is stable. Version 0.2 has deffect and compiles only basic code samples in all other cases it simply fail.