Download JAR files tagged by tool with all dependencies

This tool allows setting the version number of a specified dependency in a given Maven pom.xml file. All original comments and formatting will be kept. Usage example: mvn com.soerensen.maven.plugins:version-edit-plugin:1.0.1:setDependencyVersion -DpomFile="pom.xml" -Dgavtc="commons-io:commons-io:4.8.0" mvn com.soerensen.maven.plugins:version-edit-plugin:0.0.1:setPropertyDependencyVersion -DpropertyFile="test.property" -Dkey="junit_junit" -Dvalue="24.0.0" gavtc -> groupId:artifactId:version:type*:classifier* * optional Extra property: - noBackupFile (default:false), used to ignore the creation of a backup file.

Tool used to analyze a set of classes and determine on what other classes they directly or indirectly depend. Typically this tool is used to compute the necessary and sufficient set of classes to include in a JAR file, for use in the class path of a client or service, or for use in the codebase of a client or service. The tool starts with a set of "root" classes and recursively computes a dependency graph, finding all of the classes referenced directly by the root classes, finding all of the classes referenced in turn by those classes, and so on, until no new classes are found or until classes that are not of interest are found. The normal output of the tool is a list of all of the classes in the dependency graph. The output from this command can be used as input to the jar tool, to create a JAR file containing precisely those classes.

This is a handy tool many developers already use to create better interaction models for their custom Alexa skills. The tool introduces an easy to read grammar for generating hundreds and thousands of variant sample utterances and slot values with just a few written lines. The resulting JSON file can be used to upload the model to your Alexa skill right away either via your web browser into Alexa skill builder interface or with help of SMAPI.

This Tool provides the means to monitor the performance of Spring Batch applications without the need to manipulate the respective code basis. Through Listeners and AOP it evaluates the throughput of a monitored Job and writes the result to a simble database-schema (a file-based H2 by default). It measures the performance of Job, Step, Chunk, Reader/Processor/Writer/Tasklet down to indivdual Items. Installation/Usage: 1. Add the springBatchPerformanceMonitoring-dependency to your POM 2. Add the de.viadee.spring.batch.infrastructure.Configurator.class to your Spring-Application-Context (via @Import on your Configuration) 3. Run the Job 4. By default the monitoring result is written to project-folder/target/database/monitoringDB.mv.db

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

Bond is a small library that can be used to spy values and mock functions during tests. Spying is a replacement for writing the assertEquals in your test, which are tedious to write and even more tedious to update whem your test setup or code inevitably changes. With Bond, you separate what is being verified, e.g., the variable named output, from what value it should have. This way you can quickly spy several variables, even have structured values such as lists or dictionaries, and these values are saved into an observation log that is saved for future reference. If the test observations are different you have the option to interact with a console or visual tool to see what has changed, and whether the reference set of observations need to be updated.

The HTTP server module (ks-server-http) implements the Web API of the KnowledgeStore, which includes the two CRUD and SPARQL endpoints. The CRUD Endpoint supports the retrieval and manipulation of semi-structured data about resource, mention, entity and axiom records (encoded in RDF, possibly using JSONLD), and the upload / download of resource representation. The SPARQL Endpoint supports SPARQL SELECT, CONSTRUCT, DESCRIBE and ASK queries according to the W3C SPARQL protocol. The two endpoints are implemented on top of a component implementing the KnowledgeStore Java API (the Store interface), which can be either the the KnowledgeStore frontend (ks-frontend) or the Java Client. The implementation of the module is based on the Jetty Web sever (run in embedded mode) and the Jersey JAX-RS implementation. Reference documentation of the Web API is automatically generated using the Enunciate tool.

Customizable cruft-free Scala archetype. Options: -sourceFolders: [all-in-src-java, scala-only, both-split-src]. DEFAULT: all-in-src-java. --all-in-src-java: Scala and Java code are both in src/main/java (same for test). Plays nicely with IDEs. --scala-only: only src/main/scala set up, and set as source folder. --both-split-src: both src/main/java and src/main/scala. Can play merry havock with IDEs, so not the default. -testLibrary: [scalatest, specs2, scalacheck-only, junit-only]. DEFAULT: scalatest. --scalatest: adds Scalatest AND Scalacheck AND JUnit for most of your testing needs. --specs2: adds specs2 AND Scalacheck AND JUnit. --scalacheck-junit: adds Scalacheck AND JUnit. --junit-only: adds JUnit ONLY. -scalaVersion: 2.10.x+. DEFAULT: 2.11.2. *The Scala tool version is generated automatically. *Some Scala versions may not be compatible with selected test library versions. Adjust as necessary.