12 projects tagged "Apache 2.0"
FitNesse Maven Classpath Plugin is a Maven2 plugin that collects the dependencies of the entire project, including its sub-modules. After resolving the artifacts, it generates the classpath and inserts it into the Fitnesse test suites, thus solving the problem of maintaining the correct classpath in FitNesse.
jSmaTeP assists in the use of Java for processing import and export data by configuring a data structure rather than by programming it. The structure of the import data is specified in an XML file. jSmaTeP then generates a value object representing exactly one row or record in the import file based on a given XML data configuration. This means that if the import or export format changes, only the XML data configuration needs to be changed to match it.
The purpose of tomcat-plugin is to provide Java Web Developers with a tool to easily deploy their changes to a locally installed Tomcat. At the moment, the main benefits of such a plugin are that you can: change a Web resource (HTML, CSS, Javascript, etc. -- specified by a resources section) without having to build the entire project and then manually copy files around; build your module as usual and then have the produced jars copied to Tomcat's webapps/$myWebapp/WEB-INF/lib and have Tomcat restarted for you; build your module as usual and then have the produced WAR copied to Tomcat's webapps; start/stop/restart your Tomcat; clean Tomcat work, logs, temp, and webapps; and integrate it with Eclipse and IntelliJ Idea.
Naked Objects is an application development platform. It's called Naked Objects because all you need to develop are your domain objects; the Naked Objects platform automatically creates an object-oriented user interface (giving you the choice of different styles) and the underlying storage mechanism (again, giving you the choice as how to persist your objects).
The maven-buildmetadata-plugin is a Maven 2 plugin that helps you easily add build metadata to generated archive artifacts. When a product is running on an application server, this tool can tell you which version of which artifact is currently running on that server, which artifact maps to which source code version in the SCM repository, what configuration set (including profiles and environment variables) has been used to generate the artifact, on which machine was the artifact built, and when was the artifact built. The provided metadata include SCM information, build time, operating system, Java runtime, Maven execution information, build user, build host name, and build version.
Lattice is a Java build system with strong multi-module support. Build files are written not in XML, but in the Python language. The benefits are much better readability and powerful imperative build scripting. For multi-module projects, Lattice uses topological sorting to decide the correct order to build each module. Because a custom task is just a regular Python function, they can perform any type of work, including invoking other Java build systems such as Ant, Maven, or Ivy.
The Maven License Verifier Plugin is a Maven plugin that is intended to check the licenses of artifacts managed by Maven. This can be done during the build process, you can choose to let the build fail if an artifact with a wrong license is used. The licenses are categorized by a definition file that lists them with their different URLs and names. This can be different from project to project.