Cloud Tools is a set of tools for deploying, managing and testing Java EE applications on Amazon's Elastic Computing Cloud (EC2) and VMware environments. There are three main parts to Cloud Tools:
* EC2Deploy - the core framework. This framework manages virtual instances (e.g. EC2), configures MySQL, Tomcat, Terracotta and Apache and deploys the application. See this blog entry for an overview.
* Maven and Grails plugins that use EC2Deploy to deploy an application
* Amazon Machine Images (AMIs) that are configured to run Tomcat and work with EC2Deploy. See list of installed software.
sbt is a simple build tool for Scala projects that aims to do the basics well. It requires Java 1.5 or later.
Features
* Fairly fast, unintrusive, and easy to set up for simple projects
* Configuration is done in Scala
* The default source directory layout is the same as maven's so you can always switch to maven should you need/want to
* Regardless of what sources you have added, changed, or removed, sbt should (in theory) recompile the right sources using information extracted from compilation with a compiler plugin
* Supports ScalaCheck, specs, and ScalaTest.
* Can generate documentation with scaladoc
* Packages jars (classes, sources, or api docs)
* Can start the Scala interpreter with the right classpath (dependencies and compiled classes)
* Multiple project/subproject support
* Parallel task execution, including parallel test execution
* Dependency management support: basic inline declarations, configuration with Maven (partial support) or Ivy, or manual management.
Calm stands for…
Seascape Calm Weather
Seascape Calm Weather
…Calm Application Lifecycle Management, which stands for Calm Application Lifecycle Management Application Lifecycle Management … ehm just kidding ;)
Calm is an early implementation of main ALM use cases on an Open Source and collaborative framework based on Apache Maven.
What exactly is Maven Calm
Maven Calm is not just a Corporate POM. It’s a cross-corporate POM which provides lifecycle-oriented configuration for your Maven Plugins; the best way to start is having a look at the presentation! In short, your Project or Corporate POM should look like this to inherit all the ALM oriented behaviors.
Impala allows you to divide a large Spring-based application into a hierarchy of modules. These modules can be dynamically added, updated or removed.
Because Impala-based applications are genuinely modular, they are much easier to maintain than vanilla Spring applications.
Impala radically boosts productivity of Spring application development. This is enabled by the dynamic module loading capability, the seamless integration with Eclipse, and the efficient mechanisms for running Spring integration tests, both individually and within suites. When writing applications you only rarely need to restart your JVM, allowing your application changes to be reflected almost instantly. No long restart waits required!
Impala also features a build system, based on ANT, and dependency management capabilities, which you can optionally use.
For up to date news on development of Impala, see the project blog.
Impala is developed under the Apache Licence, Version 2.
This article show you how you can fix bugs for maven-plugins (eclipse setup for hacking the code, debugging etc.) with a concrete project: maven-eclipse-plugin. Lets start …
Pax Construct provides a Swiss Army® knife for OSGi that helps you rapidly create, build, manage and deploy many types of OSGi bundles. The core functionality is provided by a flexible Maven2 plugin that enhances and streamlines the Maven build process for OSGi, along with intelligent archetypes that adapt according to your needs.
Unix and Windows scripts are available to further reduce the need to remember (and type) long command strings. These scripts come with basic help text and can bootstrap themselves from an empty system.
You can use Pax Construct to create a simple first bundle in less than a minute, all the way up to managing a Spring Dynamic Modules for OSGiTM system.
This plugin for Maven 2 is based on the BND tool from Peter Kriens. The way BND works is by treating your project as a big collection of classes (e.g., project code, dependencies, and the class path). The way you create a bundle with BND is to tell it the content of the bundle's JAR file as a subset of the available classes. This plugin wraps BND to make it work specifically with the Maven 2 project structure and to provide it with reasonable default behavior for Maven 2 projects.
Since the 1.4.0 release, this plugin also aims to automate OBR (OSGi Bundle Repository) management. It helps manage a local OBR for your local Maven repository, and also supports remote OBRs for bundle distribution. The plug-in automatically computes bundle capabilities and requirements, using a combination of Bindex and Maven metadata.
SpringSource Application Platform is a completely module-based Java application server that is designed to run enterprise Java applications and Spring-powered applications with a new degree of flexibility and reliability. The SpringSource Application Platform is based on the new SpringSource Dynamic Module Kernel™ (dm-Kernel). The dm-Kernel provides a module-based backbone for the server, which also harnesses the power of Spring, Apache Tomcat and OSGi-based technologies
This page will try to explain one particular process that can be used to version your projects, as a developer. While the process covered here will use one example of how to accomplish effective versioning, the concepts can be used anywhere.
Maven Archetypes for Web Applications
This page contains maven archetypes to help you quickly and easily get started on a web project that uses the jetty plugin. Each archetype allows you to generate a template for your project based on the included sample web application. (This supposes that maven 2.x is already installed in your system)