IDE

Ant Chain API SDK

cn.com.antcloud.api : antcloud-api-provider-baasplus

Ant Chain API SDK For Java Copyright (c) 2020-present antgroup.com, https://www.antgroup.com

Last Version: 1.1.2

Release Date:

Ant Chain API SDK

cn.com.antcloud.api : antcloud-api-provider-bccr

Ant Chain API SDK For Java Copyright (c) 2020-present antgroup.com, https://www.antgroup.com

Last Version: 1.12.0

Release Date:

SpiderLib

cn.miw : spiderlib

爬取 html json jsonp的工具

Last Version: 0.0.2

Release Date:

SmartVideo-Android-SDK

com.videoengager : videoengager-sdk

The VideoEngager SDK for Android allows to integrate chat, voice, and video calling into your native Android mobile applications.

Last Version: 1.0.1

Release Date:

Last Version: 0.5.0

Release Date:

YC KMS provider for AWS Encryption SDK

com.yandex.cloud : kms-provider-awscrypto

Glue code to enable usage of Yandex Cloud KMS from AWS Encryption SDK

Last Version: 2.6

Release Date:

org.openide.windows

com.github.veithen.visualwas.thirdparty : org.openide.windows

Open Source implementation of the WebSphere SOAP JMX protocol

Last Version: 4.0.0

Release Date:

Last Version: 0.1.2

Release Date:

Last Version: 1.0.0.Alpha4

Release Date:

Last Version: 2.0.15

Release Date:

Calc Table (based) Data Provider - Examples

org.drakosha.tools.calctable : calctable-dataprovider-examples

Use case examples for the "Calc Table (based) Data Provider" (Java-Edition).

Last Version: 0.0.3

Release Date:

Last Version: 0.0.1

Release Date:

Last Version: 4.10.0

Release Date:

javafx-canvas

org.apidesign.canvas : javafx-canvas

Java.net - The Source for Java Technology Collaboration

Last Version: 0.5.2

Release Date:

OpenDJ Packages

org.openidentityplatform.opendj : opendj-packages

This module contains sub-modules which generates OEM OpenDJ version, deb and rpm OpenDJ packages.

Last Version: 4.5.0

Release Date:

Last Version: 0.1.2

Release Date:

Last Version: 4.0.0-incubator

Release Date:

Last Version: 0.3

Release Date:

Last Version: 5.13.0-m3

Release Date:

WSO2 Carbon - Identity Relying Party Feature Aggregator Module

org.wso2.carbon.identity : identity-relyingparty-feature

WSO2 is an open source application development software company focused on providing service-oriented architecture solutions for professional developers.

Last Version: 4.5.6

Release Date:

Agile Architecture Documentation System : Sequence diagram generator

io.github.Riduidel.agile-architecture-documentation-system : sequence-diagram-generator

Generates sequence diagrams for components in the containers opting in for it. Model elements in those sequence diagrams should also be indicated by containers.

Last Version: 0.1.0

Release Date:

WSO2 Carbon - Identity Gateway Feature

org.wso2.carbon.identity.gateway : org.wso2.carbon.identity.gateway.feature

WSO2 is an open source application development software company focused on providing service-oriented architecture solutions for professional developers.

Last Version: 0.1.8

Release Date:

Last Version: 0.1.0

Release Date:

Ant Chain API SDK

cn.com.antcloud.api : antcloud-api-provider-audit

Ant Chain API SDK For Java Copyright (c) 2020-present antgroup.com, https://www.antgroup.com

Last Version: 1.2.4

Release Date:

Last Version: 0.0.1

Release Date:

Last Version: 0.2.0

Release Date:

OpenIG Project

org.openidentityplatform.openig : openig-project

The Open Identity Gateway is a high-performance reverse proxy server with specialized session management and credential replay functionality.

Last Version: 5.0.11

Release Date:

Last Version: 1.0.1

Release Date:

Google Video Stitcher API Parent

com.google.cloud : google-cloud-video-stitcher-parent

Java idiomatic client for Google Cloud Platform services.

Last Version: 0.2.1

Release Date:

WSO2 Carbon - Functions Library Manager

org.wso2.carbon.identity.framework : functions-library-mgt

WSO2 is an open source application development software company focused on providing service-oriented architecture solutions for professional developers.

Last Version: 5.20.324

Release Date:

Last Version: 6.0.0.Beta2

Release Date:

Last Version: 1.7.10

Release Date:

Last Version: 1.021

Release Date:

pact-jvm-provider-lein_2.10

au.com.dius : pact-jvm-provider-lein_2.10

# Leiningen plugin to verify a provider [version 2.2.14+, 3.0.3+] Leiningen plugin for verifying pacts against a provider. The plugin provides a `pact-verify` task which will verify all configured pacts against your provider. ## To Use It ### 1. Add the plugin to your project plugins, preferably in it's own profile. ```clojure :profiles { :pact { :plugins [[au.com.dius/pact-jvm-provider-lein_2.11 "3.0.3" :exclusions [commons-logging]]] :dependencies [[ch.qos.logback/logback-core "1.1.3"] [ch.qos.logback/logback-classic "1.1.3"] [org.apache.httpcomponents/httpclient "4.4.1"]] }}} ``` ### 2. Define the pacts between your consumers and providers You define all the providers and consumers within the `:pact` configuration element of your project. ```clojure :pact { :service-providers { ; You can define as many as you need, but each must have a unique name :provider1 { ; All the provider properties are optional, and have sensible defaults (shown below) :protocol "http" :host "localhost" :port 8080 :path "/" :has-pact-with { ; Again, you can define as many consumers for each provider as you need, but each must have a unique name :consumer1 { ; pact file can be either a path or an URL :pact-file "path/to/provider1-consumer1-pact.json" } } } } } ``` ### 3. Execute `lein with-profile pact pact-verify` You will have to have your provider running for this to pass. ## Enabling insecure SSL For providers that are running on SSL with self-signed certificates, you need to enable insecure SSL mode by setting `:insecure true` on the provider. ```clojure :pact { :service-providers { :provider1 { :protocol "https" :host "localhost" :port 8443 :insecure true :has-pact-with { :consumer1 { :pact-file "path/to/provider1-consumer1-pact.json" } } } } } ``` ## Specifying a custom trust store For environments that are running their own certificate chains: ```clojure :pact { :service-providers { :provider1 { :protocol "https" :host "localhost" :port 8443 :trust-store "relative/path/to/trustStore.jks" :trust-store-password "changeme" :has-pact-with { :consumer1 { :pact-file "path/to/provider1-consumer1-pact.json" } } } } } ``` `:trust-store` is relative to the current working (build) directory. `:trust-store-password` defaults to `changeit`. NOTE: The hostname will still be verified against the certificate. ## Modifying the requests before they are sent Sometimes you may need to add things to the requests that can't be persisted in a pact file. Examples of these would be authentication tokens, which have a small life span. The Leiningen plugin provides a request filter that can be set to an anonymous function on the provider that will be called before the request is made. This function will receive the HttpRequest object as a parameter. ```clojure :pact { :service-providers { :provider1 { ; function that adds an Authorization header to each request :request-filter #(.addHeader % "Authorization" "oauth-token eyJhbGciOiJSUzI1NiIsIm...") :has-pact-with { :consumer1 { :pact-file "path/to/provider1-consumer1-pact.json" } } } } } ``` __*Important Note:*__ You should only use this feature for things that can not be persisted in the pact file. By modifying the request, you are potentially modifying the contract from the consumer tests! ## Modifying the HTTP Client Used The default HTTP client is used for all requests to providers (created with a call to `HttpClients.createDefault()`). This can be changed by specifying a function assigned to `:create-client` on the provider that returns a `CloseableHttpClient`. The function will receive the provider info as a parameter. ## Turning off URL decoding of the paths in the pact file [version 3.3.3+] By default the paths loaded from the pact file will be decoded before the request is sent to the provider. To turn this behaviour off, set the system property `pact.verifier.disableUrlPathDecoding` to `true`. __*Important Note:*__ If you turn off the url path decoding, you need to ensure that the paths in the pact files are correctly encoded. The verifier will not be able to make a request with an invalid encoded path. ## Plugin Properties The following plugin options can be specified on the command line: |Property|Description| |--------|-----------| |:pact.showStacktrace|This turns on stacktrace printing for each request. It can help with diagnosing network errors| |:pact.showFullDiff|This turns on displaying the full diff of the expected versus actual bodies [version 3.3.6+]| |:pact.filter.consumers|Comma seperated list of consumer names to verify| |:pact.filter.description|Only verify interactions whose description match the provided regular expression| |:pact.filter.providerState|Only verify interactions whose provider state match the provided regular expression. An empty string matches interactions that have no state| Example, to run verification only for a particular consumer: ``` $ lein with-profile pact pact-verify :pact.filter.consumers=consumer2 ``` ## Provider States For each provider you can specify a state change URL to use to switch the state of the provider. This URL will receive the `providerState` description from the pact file before each interaction via a POST. The `:state-change-uses-body` controls if the state is passed in the request body or as a query parameter. These values can be set at the provider level, or for a specific consumer. Consumer values take precedent if both are given. ```clojure :pact { :service-providers { :provider1 { :state-change-url "http://localhost:8080/tasks/pactStateChange" :state-change-uses-body false ; defaults to true :has-pact-with { :consumer1 { :pact-file "path/to/provider1-consumer1-pact.json" } } } } } ``` If the `:state-change-uses-body` is not specified, or is set to true, then the provider state description will be sent as JSON in the body of the request. If it is set to false, it will passed as a query parameter. As for normal requests (see Modifying the requests before they are sent), a state change request can be modified before it is sent. Set `:state-change-request-filter` to an anonymous function on the provider that will be called before the request is made. ## Filtering the interactions that are verified You can filter the interactions that are run using three properties: `:pact.filter.consumers`, `:pact.filter.description` and `:pact.filter.providerState`. Adding `:pact.filter.consumers=consumer1,consumer2` to the command line will only run the pact files for those consumers (consumer1 and consumer2). Adding `:pact.filter.description=a request for payment.*` will only run those interactions whose descriptions start with 'a request for payment'. `:pact.filter.providerState=.*payment` will match any interaction that has a provider state that ends with payment, and `:pact.filter.providerState=` will match any interaction that does not have a provider state. ## Starting and shutting down your provider For the pact verification to run, the provider needs to be running. Leiningen provides a `do` task that can chain tasks together. So, by creating a `start-app` and `terminate-app` alias, you could so something like: $ lein with-profile pact do start-app, pact-verify, terminate-app However, if the pact verification fails the build will abort without running the `terminate-app` task. To have the start and terminate tasks always run regardless of the state of the verification, you can assign them to `:start-provider-task` and `:terminate-provider-task` on the provider. ```clojure :aliases {"start-app" ^{:doc "Starts the app"} ["tasks to start app ..."] ; insert tasks to start the app here "terminate-app" ^{:doc "Kills the app"} ["tasks to terminate app ..."] ; insert tasks to stop the app here } :pact { :service-providers { :provider1 { :start-provider-task "start-app" :terminate-provider-task "terminate-app" :has-pact-with { :consumer1 { :pact-file "path/to/provider1-consumer1-pact.json" } } } } } ``` Then you can just run: $ lein with-profile pact pact-verify and the `start-app` and `terminate-app` tasks will run before and after the provider verification. ## Specifying the provider hostname at runtime [3.0.4+] If you need to calculate the provider hostname at runtime (for instance it is run as a new docker container or AWS instance), you can give an anonymous function as the provider host that returns the host name. The function will receive the provider information as a parameter. ```clojure :pact { :service-providers { :provider1 { :host #(calculate-host-name %) :has-pact-with { :consumer1 { :pact-file "path/to/provider1-consumer1-pact.json" } } } } } ```

Last Version: 2.4.20

Release Date:

IdentityXClientSDK

com.identityx : IdentityXClientSDK

Client SDK for IdentityX Rest Services

Last Version: 5.3.0.5

Release Date:

slidertooltip

com.diogobernardino.williamchart : tooltip-slider

Williamchart plugin to show a vertical slider tooltip.

Last Version: 3.11.0

Release Date:

huawei

com.rover12421.AndroidHideApi : huawei

Android Hidden API / huawei

Last Version: 1.4

Release Date:

Lokki

fi.evident.lokki : lokki

A simple localization library for Java

Last Version: 0.1.1

Release Date:

Last Version: 6.1.6

Release Date:

ec4j-ide-support

org.ec4j.core : ec4j-ide-support

EditorConfig validation and completion

Last Version: 0.3.0

Release Date: