Download JAR files tagged by writer with all dependencies
jmxtrans-output from group org.jmxtrans (version 272)
This module groups all different output writers.
Different output writers have different dependencies. To ensure that those dependencies do not leak to other
output writer, or that we can limit to number of dependencies at runtime, output writers are split into
separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the
AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to
Graphite, there should be no need to have the AWS SDK in your classpath at runtime.
Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are
based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output
writers to a specific module, we can ensure this has minimal impact.
Group: org.jmxtrans Artifact: jmxtrans-output
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact jmxtrans-output
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
jmxtrans-output-kafka from group org.jmxtrans (version 272)
4 downloads
Artifact jmxtrans-output-kafka
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 5
Dependencies guava, kafka-clients, jmxtrans-core, jmxtrans-utils, slf4j-api,
There are maybe transitive dependencies!
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 5
Dependencies guava, kafka-clients, jmxtrans-core, jmxtrans-utils, slf4j-api,
There are maybe transitive dependencies!
jmxtrans-output-gelf from group org.jmxtrans (version 272)
0 downloads
Artifact jmxtrans-output-gelf
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies commons-lang, gelfclient, jmxtrans-core, jmxtrans-output-core,
There are maybe transitive dependencies!
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies commons-lang, gelfclient, jmxtrans-core, jmxtrans-output-core,
There are maybe transitive dependencies!
jmxtrans-output-elastic from group org.jmxtrans (version 272)
Group: org.jmxtrans Artifact: jmxtrans-output-elastic
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact jmxtrans-output-elastic
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 5
Dependencies guava, jest, jmxtrans-core, jmxtrans-utils, slf4j-api,
There are maybe transitive dependencies!
Group org.jmxtrans
Version 272
Last update 30. March 2021
Organization not specified
URL Not specified
License not specified
Dependencies amount 5
Dependencies guava, jest, jmxtrans-core, jmxtrans-utils, slf4j-api,
There are maybe transitive dependencies!
springBatchPerformanceMonitoring from group de.viadee (version 1.0.2)
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
0 downloads
Artifact springBatchPerformanceMonitoring
Group de.viadee
Version 1.0.2
Last update 10. July 2017
Organization viadee Unternehmensberatung GmbH
URL https://java.viadee.de/spring-batch-monitoring/
License FreeBSD License
Dependencies amount 16
Dependencies spring-batch-core, spring-batch-infrastructure, spring-beans, spring-core, spring-context, spring-tx, spring-jdbc, spring-test, spring-aop, aspectjrt, aspectjweaver, log4j, junit, mockito-core, h2, tomcat-dbcp,
There are maybe transitive dependencies!
Group de.viadee
Version 1.0.2
Last update 10. July 2017
Organization viadee Unternehmensberatung GmbH
URL https://java.viadee.de/spring-batch-monitoring/
License FreeBSD License
Dependencies amount 16
Dependencies spring-batch-core, spring-batch-infrastructure, spring-beans, spring-core, spring-context, spring-tx, spring-jdbc, spring-test, spring-aop, aspectjrt, aspectjweaver, log4j, junit, mockito-core, h2, tomcat-dbcp,
There are maybe transitive dependencies!
SEWOL from group de.uni.freiburg.iig.telematik (version 1.0.2)
SEWOL provides support for the handling of workflow traces. Specifically it allows to specify the shape and content of process traces in terms of entries representing the execution of a specific workflow activity. SEWOL also allows to write these traces on disk as a log file with the help of a special file writer for process logs. Currently it supports plain text, Petrify, MXML and XES log file types. In order to specify security-related context information, SEWOL provides access control models such as access control lists (ACL) and role-based access control models (RBAC). All types of models can be conveniently edited with the help of appropriate dialogs.
Group: de.uni.freiburg.iig.telematik Artifact: SEWOL
Show all versions Show documentation Show source
Show all versions Show documentation Show source
34 downloads
Artifact SEWOL
Group de.uni.freiburg.iig.telematik
Version 1.0.2
Last update 22. January 2016
Organization Institute of Computer Science and Social Studies, Department of Telematics
URL https://github.com/iig-uni-freiburg/SEWOL
License bsd_3
Dependencies amount 6
Dependencies TOVAL, JAGAL, guava, jung-graph-impl, jung-visualization, xstream,
There are maybe transitive dependencies!
Group de.uni.freiburg.iig.telematik
Version 1.0.2
Last update 22. January 2016
Organization Institute of Computer Science and Social Studies, Department of Telematics
URL https://github.com/iig-uni-freiburg/SEWOL
License bsd_3
Dependencies amount 6
Dependencies TOVAL, JAGAL, guava, jung-graph-impl, jung-visualization, xstream,
There are maybe transitive dependencies!
JSONXML from group com.ssg.tools (version 2.0b)
JSONXML project is library used to parse/format tree-like object structures in most popular text formats: XML and JSON.
For parsing it accepts "java.io.Reader" and return java object.
For formatting it accepts java object and "java.io.Writer".
Object is generally structure that contains Map and/or List elements.
Map is ordered set of named items. List is set of unnamed items.
Reflection may be used to convert objects into set of maps/lists and vice versa.
JSON parser is implemented explicitly.
XML parser is based on SAX parser and applies only certain rules for result.
Library is designed to allow various entry points for variable decisions depending on end use needs.
1. Formats - formats are used to enable locale-specific parsing/formatting of numbers and dates.
2. ReflectiveBuilder - enables reflection. Default implementation uses getters/setters only.
3. ObjectsRegistry - used to keep track of parsed or formatted objects and allow
resolvable references in formatted (text) form.
Artifact JSONXML
Group com.ssg.tools
Version 2.0b
Last update 25. October 2011
Organization not specified
URL http://sourceforge.net/projects/jsonxml
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.ssg.tools
Version 2.0b
Last update 25. October 2011
Organization not specified
URL http://sourceforge.net/projects/jsonxml
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
pact-jvm-consumer-specs2_2.12 from group au.com.dius (version 4.0.10)
pact-jvm-consumer-specs2
========================
## Specs2 Bindings for the pact-jvm library
## Dependency
In the root folder of your project in build.sbt add the line:
```scala
libraryDependencies += "au.com.dius" %% "pact-jvm-consumer-specs2" % "3.2.11"
```
or if you are using Gradle:
```groovy
dependencies {
testCompile "au.com.dius:pact-jvm-consumer-specs2_2.11:3.2.11"
}
```
__*Note:*__ `PactSpec` requires spec2 3.x. Also, for spray users there's an incompatibility between specs2 v3.x and spray.
Follow these instructions to resolve that problem: https://groups.google.com/forum/#!msg/spray-user/2T6SBp4OJeI/AJlnJuAKPRsJ
## Usage
To author a test, mix `PactSpec` into your spec
First we define a service client called `ConsumerService`. In our example this is a simple wrapper for `dispatch`, an HTTP client. The source code can be found in the test folder alongside the `ExamplePactSpec`.
Here is a simple example:
```
import au.com.dius.pact.consumer.PactSpec
class ExamplePactSpec extends Specification with PactSpec {
val consumer = "My Consumer"
val provider = "My Provider"
override def is = uponReceiving("a request for foo")
.matching(path = "/foo")
.willRespondWith(body = "{}")
.withConsumerTest { providerConfig =>
Await.result(ConsumerService(providerConfig.url).simpleGet("/foo"), Duration(1000, MILLISECONDS)) must beEqualTo(200, Some("{}"))
}
}
```
This spec will be run along with the rest of your specs2 unit tests and will output your pact json to
```
/target/pacts/<Consumer>_<Provider>.json
```
# Forcing pact files to be overwritten (3.6.5+)
By default, when the pact file is written, it will be merged with any existing pact file. To force the file to be
overwritten, set the Java system property `pact.writer.overwrite` to `true`.
Group: au.com.dius Artifact: pact-jvm-consumer-specs2_2.12
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact pact-jvm-consumer-specs2_2.12
Group au.com.dius
Version 4.0.10
Last update 18. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies pact-jvm-consumer, json, specs2-core_2.12, async-http-client, scala-java8-compat_2.12,
There are maybe transitive dependencies!
Group au.com.dius
Version 4.0.10
Last update 18. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies pact-jvm-consumer, json, specs2-core_2.12, async-http-client, scala-java8-compat_2.12,
There are maybe transitive dependencies!
specs2_2.13 from group au.com.dius.pact.consumer (version 4.2.21)
pact-jvm-consumer-specs2
========================
## Specs2 Bindings for the pact-jvm library
## Dependency
In the root folder of your project in build.sbt add the line:
```scala
libraryDependencies += "au.com.dius.pact.consumer" %% "specs2" % "4.0.1"
```
or if you are using Gradle:
```groovy
dependencies {
testCompile "au.com.dius.pact.consumer:specs2_2.13:4.0.1"
}
```
__*Note:*__ `PactSpec` requires spec2 3.x. Also, for spray users there's an incompatibility between specs2 v3.x and spray.
Follow these instructions to resolve that problem: https://groups.google.com/forum/#!msg/spray-user/2T6SBp4OJeI/AJlnJuAKPRsJ
## Usage
To author a test, mix `PactSpec` into your spec
First we define a service client called `ConsumerService`. In our example this is a simple wrapper for `dispatch`, an HTTP client. The source code can be found in the test folder alongside the `ExamplePactSpec`.
Here is a simple example:
```
import au.com.dius.pact.consumer.PactSpec
class ExamplePactSpec extends Specification with PactSpec {
val consumer = "My Consumer"
val provider = "My Provider"
override def is = uponReceiving("a request for foo")
.matching(path = "/foo")
.willRespondWith(body = "{}")
.withConsumerTest { providerConfig =>
Await.result(ConsumerService(providerConfig.url).simpleGet("/foo"), Duration(1000, MILLISECONDS)) must beEqualTo(200, Some("{}"))
}
}
```
This spec will be run along with the rest of your specs2 unit tests and will output your pact json to
```
/target/pacts/<Consumer>_<Provider>.json
```
# Forcing pact files to be overwritten (3.6.5+)
By default, when the pact file is written, it will be merged with any existing pact file. To force the file to be
overwritten, set the Java system property `pact.writer.overwrite` to `true`.
# Test Analytics
We are tracking anonymous analytics to gather important usage statistics like JVM version
and operating system. To disable tracking, set the 'pact_do_not_track' system property or environment
variable to 'true'.
Group: au.com.dius.pact.consumer Artifact: specs2_2.13
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact specs2_2.13
Group au.com.dius.pact.consumer
Version 4.2.21
Last update 13. May 2022
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies consumer, json, specs2-core_2.13, async-http-client, scala-java8-compat_2.13,
There are maybe transitive dependencies!
Group au.com.dius.pact.consumer
Version 4.2.21
Last update 13. May 2022
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies consumer, json, specs2-core_2.13, async-http-client, scala-java8-compat_2.13,
There are maybe transitive dependencies!
pact-jvm-consumer-junit5_2.12 from group au.com.dius (version 3.6.15)
pact-jvm-consumer-junit5
========================
JUnit 5 support for Pact consumer tests
## Dependency
The library is available on maven central using:
* group-id = `au.com.dius`
* artifact-id = `pact-jvm-consumer-junit5_2.12`
* version-id = `3.6.x`
## Usage
### 1. Add the Pact consumer test extension to the test class.
To write Pact consumer tests with JUnit 5, you need to add `@ExtendWith(PactConsumerTestExt)` to your test class. This
replaces the `PactRunner` used for JUnit 4 tests. The rest of the test follows a similar pattern as for JUnit 4 tests.
```java
@ExtendWith(PactConsumerTestExt.class)
class ExampleJavaConsumerPactTest {
```
### 2. create a method annotated with `@Pact` that returns the interactions for the test
For each test (as with JUnit 4), you need to define a method annotated with the `@Pact` annotation that returns the
interactions for the test.
```java
@Pact(provider="ArticlesProvider", consumer="test_consumer")
public RequestResponsePact createPact(PactDslWithProvider builder) {
return builder
.given("test state")
.uponReceiving("ExampleJavaConsumerPactTest test interaction")
.path("/articles.json")
.method("GET")
.willRespondWith()
.status(200)
.body("{\"responsetest\": true}")
.toPact();
}
```
### 3. Link the mock server with the interactions for the test with `@PactTestFor`
Then the final step is to use the `@PactTestFor` annotation to tell the Pact extension how to setup the Pact test. You
can either put this annotation on the test class, or on the test method. For examples see
[ArticlesTest](src/test/java/au/com/dius/pact/consumer/junit5/ArticlesTest.java) and
[MultiTest](src/test/groovy/au/com/dius/pact/consumer/junit5/MultiTest.groovy).
The `@PactTestFor` annotation allows you to control the mock server in the same way as the JUnit 4 `PactProviderRule`. It
allows you to set the hostname to bind to (default is `localhost`) and the port (default is to use a random port). You
can also set the Pact specification version to use (default is V3).
```java
@ExtendWith(PactConsumerTestExt.class)
@PactTestFor(providerName = "ArticlesProvider")
public class ExampleJavaConsumerPactTest {
```
**NOTE on the hostname**: The mock server runs in the same JVM as the test, so the only valid values for hostname are:
| hostname | result |
| -------- | ------ |
| `localhost` | binds to the address that localhost points to (normally the loopback adapter) |
| `127.0.0.1` or `::1` | binds to the loopback adapter |
| host name | binds to the default interface that the host machines DNS name resolves to |
| `0.0.0.0` or `::` | binds to the all interfaces on the host machine |
#### Matching the interactions by provider name
If you set the `providerName` on the `@PactTestFor` annotation, then the first method with a `@Pact` annotation with the
same provider name will be used. See [ArticlesTest](src/test/java/au/com/dius/pact/consumer/junit5/ArticlesTest.java) for
an example.
#### Matching the interactions by method name
If you set the `pactMethod` on the `@PactTestFor` annotation, then the method with the provided name will be used (it still
needs a `@Pact` annotation). See [MultiTest](src/test/groovy/au/com/dius/pact/consumer/junit5/MultiTest.groovy) for an example.
### Injecting the mock server into the test
You can get the mock server injected into the test method by adding a `MockServer` parameter to the test method.
```java
@Test
void test(MockServer mockServer) throws IOException {
HttpResponse httpResponse = Request.Get(mockServer.getUrl() + "/articles.json").execute().returnResponse();
assertThat(httpResponse.getStatusLine().getStatusCode(), is(equalTo(200)));
}
```
This helps with getting the base URL of the mock server, especially when a random port is used.
## Changing the directory pact files are written to
By default, pact files are written to `target/pacts` (or `build/pacts` if you use Gradle), but this can be overwritten with the `pact.rootDir` system property.
This property needs to be set on the test JVM as most build tools will fork a new JVM to run the tests.
For Gradle, add this to your build.gradle:
```groovy
test {
systemProperties['pact.rootDir'] = "$buildDir/custom-pacts-directory"
}
```
For maven, use the systemPropertyVariables configuration:
```xml
<project>
[...]
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.18</version>
<configuration>
<systemPropertyVariables>
<pact.rootDir>some/other/directory</pact.rootDir>
<buildDirectory>${project.build.directory}</buildDirectory>
[...]
</systemPropertyVariables>
</configuration>
</plugin>
</plugins>
</build>
[...]
</project>
```
For SBT:
```scala
fork in Test := true,
javaOptions in Test := Seq("-Dpact.rootDir=some/other/directory")
```
### Using `@PactFolder` annotation [3.6.2+]
You can override the directory the pacts are written in a test by adding the `@PactFolder` annotation to the test
class.
## Forcing pact files to be overwritten (3.6.5+)
By default, when the pact file is written, it will be merged with any existing pact file. To force the file to be
overwritten, set the Java system property `pact.writer.overwrite` to `true`.
## Unsupported
The current implementation does not support tests with multiple providers. This will be added in a later release.
# Having values injected from provider state callbacks (3.6.11+)
You can have values from the provider state callbacks be injected into most places (paths, query parameters, headers,
bodies, etc.). This works by using the V3 spec generators with provider state callbacks that return values. One example
of where this would be useful is API calls that require an ID which would be auto-generated by the database on the
provider side, so there is no way to know what the ID would be beforehand.
The following DSL methods all you to set an expression that will be parsed with the values returned from the provider states:
For JSON bodies, use `valueFromProviderState`.<br/>
For headers, use `headerFromProviderState`.<br/>
For query parameters, use `queryParameterFromProviderState`.<br/>
For paths, use `pathFromProviderState`.
For example, assume that an API call is made to get the details of a user by ID. A provider state can be defined that
specifies that the user must be exist, but the ID will be created when the user is created. So we can then define an
expression for the path where the ID will be replaced with the value returned from the provider state callback.
```java
.pathFromProviderState("/api/users/${id}", "/api/users/100")
```
You can also just use the key instead of an expression:
```java
.valueFromProviderState('userId', 'userId', 100) // will look value using userId as the key
```
Group: au.com.dius Artifact: pact-jvm-consumer-junit5_2.12
Show all versions Show documentation Show source
Show all versions Show documentation Show source
3 downloads
Artifact pact-jvm-consumer-junit5_2.12
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 2
Dependencies pact-jvm-consumer_2.12, junit-jupiter-api,
There are maybe transitive dependencies!
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 2
Dependencies pact-jvm-consumer_2.12, junit-jupiter-api,
There are maybe transitive dependencies!
Page 31 from 32 (items total 317)