Buildr is a build system for Java applications in Ruby Maven compatible * A simple way to specify projects, and build large projects out of smaller sub-projects. * Pre-canned tasks that require the least amount of configuration, keeping the build script DRY and simple. * Compiling, copying and filtering resources, JUnit/TestNG test cases, APT source code generation, Javadoc etc * A dependency mechanism that only builds what has changed since the last release. * A drop-in replacement for Maven 2.0, Buildr uses the same file layout, artifact specifications, local and remote repositories. * All your Ant tasks belong to us! Anything you can do with Ant, you can do with Buildr. * No overhead for building “plugins” or configuration. Just write new tasks or functions. * Buildr is Ruby all the way down. No one-off task is too demanding when you write code using variables, functions and objects. * Simple to upgrade to new versions. * fast
Apache Maven ist mehr als nur ein Build-Tool. Richtig eingesetzt kann es helfen, Projekte zu managen und die Entwicklung zu unterstützen. Dieser Artikel erklärt das optimale Vorgehen.
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.
Summary Eclipse offers the possibility to build plug-ins automatically outside the Eclipse IDE, which is called "headless build". Eclipse itself is built headless and since Eclipse is an assembly of plug-ins, this feature is also available for any other p
At Cape Clear we use PDEBuild, controlled by CruiseControl driven Ant scripts to build our Eclipse features. As Oisín Hurley pointed out recently it has got a steep learning curve but once it is up and running it allows development teams to contribute to