Download JAR files tagged by expression with all dependencies
net.sourceforge.reb4j.scala from group net.sourceforge.reb4j (version 2.1.0)
The purpose of reb4j is to provide a pure Java wrapper around
the regular expression syntax provided by the JRE's
java.util.regex.Pattern class in order to facilitate programmatic
construction of regular expressions while taking advantage of
compile-time syntax checking. This sub-project contains the
Scala implementation of reb4j.
Group: net.sourceforge.reb4j Artifact: net.sourceforge.reb4j.scala
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact net.sourceforge.reb4j.scala
Group net.sourceforge.reb4j
Version 2.1.0
Last update 03. February 2013
Organization not specified
URL Not specified
License not specified
Dependencies amount 3
Dependencies junit, scala-library, scalatest_2.10,
There are maybe transitive dependencies!
Group net.sourceforge.reb4j
Version 2.1.0
Last update 03. February 2013
Organization not specified
URL Not specified
License not specified
Dependencies amount 3
Dependencies junit, scala-library, scalatest_2.10,
There are maybe transitive dependencies!
net.sourceforge.reb4j from group net.sourceforge.reb4j (version 2.1.0)
The purpose of reb4j is to provide a pure Java wrapper around
the regular expression syntax provided by the JRE's
java.util.regex.Pattern class in order to facilitate programmatic
construction of regular expressions while taking advantage of
compile-time syntax checking. This sub-project contains the
Java implementation of reb4j.
Group: net.sourceforge.reb4j Artifact: net.sourceforge.reb4j
Show all versions Show documentation Show source
Show all versions Show documentation Show source
8 downloads
Artifact net.sourceforge.reb4j
Group net.sourceforge.reb4j
Version 2.1.0
Last update 03. February 2013
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies junit, functionaljava,
There are maybe transitive dependencies!
Group net.sourceforge.reb4j
Version 2.1.0
Last update 03. February 2013
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies junit, functionaljava,
There are maybe transitive dependencies!
jmcnet-libCommun from group com.googlecode.jmcnet (version 1.8)
This project aim's to provide J2EE reusable components :
- flex integration : FlexAcegiLoginCommand, ServiceLoggerPresentation, SpringFactory,
- FOP formatter : FopFormatter,
- Spring and Acegi for JUnit : SpringBaseTestCase, AcegiBaseTestCase,
- Servlet : RedirectDisconnectedSessionFilter,
- utilit classes : ConvertCharset, CriptoUtilit, FileData, FormatUtilit, Time, TimeHHMM, TimeHHMMSS,
- Expression parser et evaluator : see jmcnet.libcommun.utilit.evaluator,
- Mail utilit : see jmcnet.libcommun.utilit.mail
Artifact jmcnet-libCommun
Group com.googlecode.jmcnet
Version 1.8
Last update 06. April 2010
Organization not specified
URL http://code.google.com/p/jmcnet/
License The JMCNet LibCommun Project
Dependencies amount 1
Dependencies utils,
There are maybe transitive dependencies!
Group com.googlecode.jmcnet
Version 1.8
Last update 06. April 2010
Organization not specified
URL http://code.google.com/p/jmcnet/
License The JMCNet LibCommun Project
Dependencies amount 1
Dependencies utils,
There are maybe transitive dependencies!
MathParser.org-mXparser from group org.mariuszgromada.math (version 6.0.0)
mXparser is a super easy, rich, fast and highly flexible math expression parser library (parser and evaluator of mathematical expressions / formulas provided as plain text / string). Software delivers easy to use API for JAVA, Android and C# .NET/MONO (Common Language Specification compliant: F#, Visual Basic, C++/CLI). *** If you find the software useful donation or purchase is something you might consider: https://mathparser.org/donate/ *** Online store: https://payhip.com/INFIMA *** Scalar Scientific Calculator, Charts and Scripts, Scalar Lite: https://play.google.com/store/apps/details?id=org.mathparser.scalar.lite *** Scalar Pro: https://play.google.com/store/apps/details?id=org.mathparser.scalar.pro *** ScalarMath.org: https://scalarmath.org/ *** MathSpace.pl: https://mathspace.pl/ ***
Group: org.mariuszgromada.math Artifact: MathParser.org-mXparser
Show all versions Show documentation Show source
Show all versions Show documentation Show source
209 downloads
Artifact MathParser.org-mXparser
Group org.mariuszgromada.math
Version 6.0.0
Last update 19. May 2024
Organization MathParser.org
URL https://mathparser.org/
License DUAL LICENSE
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.mariuszgromada.math
Version 6.0.0
Last update 19. May 2024
Organization MathParser.org
URL https://mathparser.org/
License DUAL LICENSE
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
gt-main from group io.oss84.geotools (version 24.2-oss84-1)
The main module contains the GeoTools public interfaces that are used by
other GeoTools modules (and GeoTools applications). Where possible we make
use industry standard terms as provided by OGC and ISO standards.
The formal GeoTools public api consists of gt-metadata, jts and the gt-main module.
The main module contains the default implementations that are available provided
to other GeoTools modules using our factory system. Factories are obtained from
an appropriate FactoryFinder, giving applications a chance configure the factory
used using the Factory Hints facilities.
FilterFactory ff = CommonFactoryFinder.getFilterFactory();
Expression expr = ff.add( expression1, expression2 );
If you find yourself using implementation specific classes chances are you doing it wrong:
Expression expr = new AddImpl( expression1, expressiom2 );
0 downloads
Artifact gt-main
Group io.oss84.geotools
Version 24.2-oss84-1
Last update 21. February 2021
Organization not specified
URL Not specified
License Lesser General Public License (LGPL)
Dependencies amount 4
Dependencies gt-referencing, jts-core, commons-text, jackson-core,
There are maybe transitive dependencies!
Group io.oss84.geotools
Version 24.2-oss84-1
Last update 21. February 2021
Organization not specified
URL Not specified
License Lesser General Public License (LGPL)
Dependencies amount 4
Dependencies gt-referencing, jts-core, commons-text, jackson-core,
There are maybe transitive dependencies!
jet from group edu.nyu (version 1.9.0)
Information extraction is the process of identifying specified classes of entities, relations, and events in natural language text – creating structured data from unstructured input. JET, the Java Extraction Toolkit, developed at New York University over the past fifteen years, provides a rich set of tools for research and education in information extraction from English text. These include standard language processing tools such as a tokenizer, sentence segmenter, part-of-speech tagger, name tagger, regular-expression pattern matcher, and dependency parser. Also provided are relation and event extractors based on the specifications of the U.S. Government's ACE [Automatic Content Extraction] program. The program is provided under an Apache 2.0 license.
0 downloads
Artifact jet
Group edu.nyu
Version 1.9.0
Last update 21. June 2016
Organization New York University
URL http://cs.nyu.edu/grishman/jet/jet.html
License Apache License, Version 2.0
Dependencies amount 13
Dependencies opennlp-maxent, jyaml, trove4j, jwnl, commons-logging, joda-time, pnuts, mallet, mallet.fst, slf4j-api, slf4j-simple, fanseparser, junit,
There are maybe transitive dependencies!
Group edu.nyu
Version 1.9.0
Last update 21. June 2016
Organization New York University
URL http://cs.nyu.edu/grishman/jet/jet.html
License Apache License, Version 2.0
Dependencies amount 13
Dependencies opennlp-maxent, jyaml, trove4j, jwnl, commons-logging, joda-time, pnuts, mallet, mallet.fst, slf4j-api, slf4j-simple, fanseparser, junit,
There are maybe transitive dependencies!
twip from group net.sf.twip (version 3.3)
"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.
Artifact twip
Group net.sf.twip
Version 3.3
Last update 31. March 2011
Organization not specified
URL http://twip.sourceforge.net/
License Apache 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group net.sf.twip
Version 3.3
Last update 31. March 2011
Organization not specified
URL http://twip.sourceforge.net/
License Apache 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
struts-el from group struts (version 1.2.9)
This subproject is an extension of the Struts tag library. Each JSP custom tag
in this library is a subclass of an associated tag in the Struts tag library.
One difference is that this tag library does not use "rtexprvalues", it uses
the expression evaluation engine in the Jakarta Taglibs implementation of the
JSP Standard Tag Library (version 1.0) to evaluate attribute values.
In addition, some of the Struts tags were not ported to this library, as it was
determined that their functionality was entirely supplied by the JSTL. These
particular Struts tags, and the reason for their non-porting will be described
in the documentation for this library.
In order to fully understand the correct utilization of this library, you must
understand the use and operation of the Struts tag library, and the use and
operation of the JavaServer Pages Standard Tag Library (hereafter called the
"JSTL"), along with the expression language (sometimes called the "EL") used
for evaluating attribute values.
Artifact struts-el
Group struts
Version 1.2.9
Last update 23. March 2006
Organization not specified
URL http://jakarta.apache.org/
License not specified
Dependencies amount 4
Dependencies standard, jstl, struts, commons-logging,
There are maybe transitive dependencies!
Group struts
Version 1.2.9
Last update 23. March 2006
Organization not specified
URL http://jakarta.apache.org/
License not specified
Dependencies amount 4
Dependencies standard, jstl, struts, commons-logging,
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!
pact-jvm-consumer-junit5 from group au.com.dius (version 4.0.10)
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`
* version-id = `4.0.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
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
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact pact-jvm-consumer-junit5
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 2
Dependencies junit-jupiter-api, pact-jvm-consumer,
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 2
Dependencies junit-jupiter-api, pact-jvm-consumer,
There are maybe transitive dependencies!
Page 78 from 3 (items total 808)