Download JAR files tagged by deployment with all dependencies

The Glassfish Maven Plugin is a Maven2 plugin allowing management of Glassfish domains and component deployments from within the Maven build lifecycle. It encapsulates domain configuration and deployment attributes within the build configuration for a more rapid development integration loop and simplified management of continuous integration testing of components destined for deployment within the Glassfish V2 and later JavaEE containers.

Responsible for deploying additional artifacts such as schemas and release distributions to MuleForge. Using this plugin ensures consistency of hosted files. Users should use the Mule Maven archetypes to generate POM.xml files for thier project. These POMs will be configured with the standard MuleForge plugins and will comply to the MuleForge rules for build and deployment.

This archetype is creating a full Sling Project composed of a OSGi Bundle and a Content Package which can be deployed to the Sling using specific profiles. It also contains two shadow folders that provide example code / files which are not part of the default build but can be easily copied into the active modules. If the project was created with the **optionAll** property set to **y** (yes) then an **All** package is created with acts as the single deployment unit of all bundles and packages in that project. Otherwise the **ui.apps** package is the deployment unit.

PLSA.R is an Open Source Java Server + API for high demand, low latency requirements. There are no static references, no file reads, access to static fields per request. Everything is either cached and or instantiated on the fly. PLSA.R runs via one command so there are no .war files to deploy, no additional plugins to install it is a simple yet powerful alternative to container deployment environments. PLSA.R even boasts a little dependency injection for data logic. www.plsar.net

This module provides access to the set of utility classes required to interact with an instance of an AppWorks Gateway from an AppWorks Service. It covers AppWorks dedicated service deployment API, which is a limited subset of the full AppWorks admin API. We currently provide the facility for services to listen to service life-cycle events such as 'service installed', 'service upgraded' and 'service uninstalled'. We also provide the facility for centralised configuration setting management. As AppWorks services are edited from the AppWork Gateway administration console, we provide the ability to respond to updates made here, and also expose creation and update end points for these settings.

Adds deployment support for akka-http applications in kubernetes. The facilities are: 1) promotheus statistics export and collection for akka http routes. The library collects http result codes, timings, and requests in flight. It additionally optionally exposes some basic akka statistics. 2) Graceful shutdown, health and readiness functions. These routes are provided at a low level to they can be used by both the routing DSL and special case implementations. 3) Access log collection. These functions can be freely composed to (e.g.) exclude health check routes from statistics and access log, or include them, depending on the requirements and standards of the user

jmockring - Java test MOCKing tool for spRING. A test harness tool for projects using the following technology stack: - Java 6+ - Spring 3.1 or greater as a DI/Deployment container - JUnit 4 and Mockito for testing - Jetty/Servlet API 3.0 for web app (war) deployment - for testing only Main features: 1) Partial Spring context deployment with automatic bean mocking for unavailable beans 2) Bootstrapping embedded Jetty server via JUnit runners 3) Configurable web application contexts 4) Automatic injection of Spring beans and mocks in JUnit tests via Java5 annotations

iServe Integrated Engine provides a complete an integrated local version of iServe to be used within Java Applications. This module provides integrated programmatic access for the deployment and interaction with iServe engines. iServe is what we refer to as service warehouse which unifies service publication, analysis, and discovery through the use of lightweight semantics as well as advanced discovery and analytic capabilities. iServe provides the typical features of service registries and additional functionality that exploits service descriptions, service annotations and further data gathered and derived from the analysis of these descriptions, data crawled from the Web, periodic monitoring and user activities.

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.