Download JAR files tagged by junit with all dependencies

BPEL has become the defacto standard language for composing Web services. However, as every other programming language developers can introduce defects into the code that can lead to undesired consequences when the software is rolled out at the client-side. Therefore, all software development methodologies include testing as one of the important activities. For nearly every programming language, a unit testing framework exists, for example JUnit for Java. These testing frameworks allow developers to easily test small chunks of the code that they have written. Until recently, BPEL lacked such support. However, BPELUnit was developed for closing this gap.

"Tests with Parameters" allows you to simply add parameters to your JUnit test methods. TwiP calls such methods with all possible combinations of their parameters... or at least some reasonable subset of commonly failing values in the case of Integers, etc. You can further reduce these values with an assume expression in an annotation, e.g. ">= 0". Alternatively you can specify a static method or field to provide the values for your test method(s), if you want to test with other than the default values. By using TwiP you change the semantics of your tests from existence to for-all quantifiers, i.e. you specify "all ravens are black" instead of "Abraxas is black", "Toni is black", etc. This moves your tests closer to an executable specification, so TwiP is a very nice addition to BDD.

A library for settings and parameterization of objects. Key features are support for data types, help for settings and parameters, annotations for ease of use. Settings and parameters both are Clonable and Serializable. More features for settings such as parsing a settingsfile, being observable, readonliness, caching etc. are available. The library contains javacc generated parsers for syntax support for properties, multi valued properties, parameterized objects and multi valued parameters.

All Gwt jre emulation code goes in this module, as well as any gwt-compiler overrides. xapi-gwt-api.jar must come before gwt-dev.jar on your compile classpath. A plugin is being built to automatically adjust maven runtime dependencies, but users of ant or IDEs will need to ensure the super jar comes before gwt-dev. We will petition gwt to accept our mods, but, until then, if you want bleeding edge features, you gotta do bleeding edge configuration. Code that ties directly into other modules, like java.lang.reflect for the reflection submodule, have their super-source here, and generators or other implementations in their own modules. This is to maintain consistency in what is or isn't whitelisted in XApi GWT. Some modules, like appengine, provide dependency-specific super-source in their own packages. This module is for jre, junit and core XApi services.

Randoop is an automatic unit test generator for Java. It automatically creates unit tests for your classes, in JUnit format. Randoop generates unit tests using feedback-directed random test generation. In a nutshell, this technique randomly, but smartly, generates sequences of methods and constructor invocations for the classes under test, and uses the sequences to create tests. Randoop executes the sequences it creates, using the results of the execution to create assertions that capture the behavior or your program and that catch bugs. Randoop has created tests that find previously unkwon errors even in widely-used libraries including Sun and IBM's JDKs. A .NET version of Randoop, used internally at Microsoft, has been used successfully by a team of test engineers to find errors in a core .NET component that has been heavily tested for years. Randoop's combination of randomized test generation and test execution results in a highly effective test generation technique.

[](https://drone.io/bitbucket.org/tidalwave/tidalwave-superpom-src/latest) The super POM for all Tidalwave projects. It is not designed for being used by others, as it contains some corporate-specific configurations, but its ancestor [TheseFooolishThings SuperPOM](http://bitbucket.org/tidalwave/thesefoolishthings-superpom-src) has been designed to be reusable. Please have a look at it. This super POM adds to its ancestor: + some Tidalwave variables that refers to the issue tracker, continuous integration system, etc...; + the definitions of versions of a number of commonly used libraries and their dependency management: * [AspectJ](https://www.eclipse.org/aspectj) * [Hamcrest Matchers](http://hamcrest.org/JavaHamcrest) * [JSR 330](https://github.com/google/guice/wiki/JSR330) * [Jakarta XML Binding (JAXB)](https://eclipse-ee4j.github.io/jaxb-ri/) * [Spotbugs annotations](https://spotbugs.readthedocs.io) * [JUnit](https://junit.org/junit5) * [Logback](http://logback.qos.ch) * [Lombok](https://projectlombok.org) * [SLF4J](slf4j.org) * [Spring 5](https://spring.io/projects/spring-framework) * [TestNG](https://testng.org) + the definition for Tidalwave 3rd party repository (stuff that is not available on Maven Central); + a profile for using the [TheseFoolishThings](http://tidalwave.it/projects/thesefoolishthings) Event Bus (```it.tidalwave-spring-messagebus-v1```); + profiles for the [Mycila License plugin](https://github.com/mycila/license-maven-plugin); + configuration of the UMLGraphDoc maven plugin; + the configuration for the TheseFoolishThings TestNG listener (which provides enhanced test logging); + definitions of some custom javadoc tags; + a blacklist for some old artifacts; + some other minor customisations.