JarCastingIDE
Ant Chain API SDK
cn.com.antcloud.api : antcloud-api-provider-accAnt Chain API SDK For Java Copyright (c) 2020-present antgroup.com, https://www.antgroup.com
Last Version: 1.1.51
Release Date:Last Version: 1.0.0
Release Date:angular-pageslide-directive
org.webjars.bower : angular-pageslide-directiveWebJar for angular-pageslide-directive
Last Version: 2.0.1
Release Date:
WSO2 Carbon Openid module
org.wso2.carbon.identity.inbound.auth.openid : identity-inbound-auth-openidWSO2 is an open source application development software company focused on providing service-oriented architecture solutions for professional developers.
Last Version: 5.7.0
Release Date:
WSO2 Carbon - XACML Mediation Feature
org.wso2.carbon.mediation : org.wso2.carbon.identity.xacml.mediator.featureThis feature contains the bundles required for XACML Mediation functionality
Last Version: 4.7.122
Release Date:
Identity Provisioning Connector SCIM Server Feature
org.wso2.carbon.identity.outbound.provisioning.scim : org.wso2.carbon.identity.provisioning.connector.scim.server.featureThis feature contains the core bundles required for SPML Identity Provisioning Connector
Last Version: 5.3.0
Release Date:selenium-video-node
com.aimmac23 : selenium-video-nodeSelenium Grid plugin that records videos of running tests
Last Version: 2.9
Release Date:
Last Version: 2.1.4
Release Date:
Last Version: 1.8.0
Release Date:
pact-jvm-provider-gradle_2.10
au.com.dius : pact-jvm-provider-gradle_2.10pact-jvm-provider-gradle ======================== Gradle plugin for verifying pacts against a provider. The Gradle plugin creates a task `pactVerify` to your build which will verify all configured pacts against your provider. ## To Use It ### For Gradle versions prior to 2.1 #### 1.1. Add the pact-jvm-provider-gradle jar file to your build script class path: ```groovy buildscript { repositories { mavenCentral() } dependencies { classpath 'au.com.dius:pact-jvm-provider-gradle_2.10:3.2.4' } } ``` #### 1.2. Apply the pact plugin ```groovy apply plugin: 'au.com.dius.pact' ``` ### For Gradle versions 2.1+ ```groovy plugins { id "au.com.dius.pact" version "3.2.4" } ``` ### 2. Define the pacts between your consumers and providers ```groovy pact { serviceProviders { // 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 = '/' // Again, you can define as many consumers for each provider as you need, but each must have a unique name hasPactWith('consumer1') { // currently supports a file path using file() or a URL using url() pactFile = file('path/to/provider1-consumer1-pact.json') } // Or if you have many pact files in a directory hasPactsWith('manyConsumers') { // Will define a consumer for each pact file in the directory. // Consumer name is read from contents of pact file pactFileLocation = file('path/to/pacts') } } } } ``` ### 3. Execute `gradle pactVerify` ## Specifying the provider hostname at runtime If you need to calculate the provider hostname at runtime, you can give a closure as the provider host. ```groovy pact { serviceProviders { provider1 { host = { lookupHostName() } hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') } } } } ``` _Since version 3.3.2+/2.4.17+_ you can also give a closure as the provider port. ## Specifying the pact file or URL at runtime [versions 3.2.7/2.4.9+] If you need to calculate the pact file or URL at runtime, you can give a Closure as the provider host. ```groovy pact { serviceProviders { provider1 { host = 'localhost' hasPactWith('consumer1') { pactFile = { lookupPactFile() } } } } } ``` ## Starting and shutting down your provider If you need to start-up or shutdown your provider, you can define a start and terminate task for each provider. You could use the jetty tasks here if you provider is built as a WAR file. ```groovy // This will be called before the provider task task('startTheApp') << { // start up your provider here } // This will be called after the provider task task('killTheApp') << { // kill your provider here } pact { serviceProviders { provider1 { startProviderTask = startTheApp terminateProviderTask = killTheApp hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') } } } } ``` Following typical Gradle behaviour, you can set the provider task properties to the actual tasks, or to the task names as a string (for the case when they haven't been defined yet). ## Preventing the chaining of provider verify task to `pactVerify` [version 3.4.1+] Normally a gradle task named `pactVerify_${provider.name}` is created and added as a task dependency for `pactVerify`. You can disable this dependency on a provider by setting `isDependencyForPactVerify` to `false` (defaults to `true`). ```groovy pact { serviceProviders { provider1 { isDependencyForPactVerify = false hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') } } } } ``` To run this task, you would then have to explicitly name it as in ```gradle pactVerify_provider1```, a normal ```gradle pactVerify``` would skip it. This can be useful when you want to define two providers, one with `startProviderTask`/`terminateProviderTask` and as second without, so you can manually start your provider (to debug it from your IDE, for example) but still want a `pactVerify` to run normally from your CI build. ## Enabling insecure SSL [version 2.2.8+] 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. ```groovy pact { serviceProviders { provider1 { insecure = true // allow SSL with a self-signed cert hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') } } } } ``` ## Specifying a custom trust store [version 2.2.8+] For environments that are running their own certificate chains: ```groovy pact { serviceProviders { provider1 { trustStore = new File('relative/path/to/trustStore.jks') trustStorePassword = 'changeit' hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') } } } } ``` `trustStore` is either relative to the current working (build) directory. `trustStorePassword` defaults to `changeit`. NOTE: The hostname will still be verified against the certificate. ## Modifying the HTTP Client Used [version 2.2.4+] 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 closure assigned to createClient on the provider that returns a CloseableHttpClient. For example: ```groovy pact { serviceProviders { provider1 { createClient = { provider -> // This will enable the client to accept self-signed certificates HttpClients.custom().setSSLHostnameVerifier(new NoopHostnameVerifier()) .setSslcontext(new SSLContextBuilder().loadTrustMaterial(null, { x509Certificates, s -> true }) .build()) .build() } hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') } } } } ``` ## Modifying the requests before they are sent **NOTE on breaking change: Version 2.1.8+ uses Apache HttpClient instead of HttpBuilder so the closure will receive a HttpRequest object instead of a request Map.** 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 Pact Gradle plugin provides a request filter that can be set to a closure on the provider that will be called before the request is made. This closure will receive the HttpRequest prior to it being executed. ```groovy pact { serviceProviders { provider1 { requestFilter = { req -> // Add an authorization header to each request req.addHeader('Authorization', 'OAUTH eyJhbGciOiJSUzI1NiIsImN0eSI6ImFw...') } hasPactWith('consumer1') { pactFile = 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! ## 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. ## Project Properties The following project properties can be specified with `-Pproperty=value` 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| ## Provider States For a description of what provider states are, see the pact documentations: http://docs.pact.io/documentation/provider_states.html ### Using a state change URL 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. As for normal requests, a request filter (`stateChangeRequestFilter`) can also be set to manipulate the request before it is sent. ```groovy pact { serviceProviders { provider1 { hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') stateChangeUrl = url('http://localhost:8001/tasks/pactStateChange') stateChangeUsesBody = false // defaults to true stateChangeRequestFilter = { req -> // Add an authorization header to each request req.addHeader('Authorization', 'OAUTH eyJhbGciOiJSUzI1NiIsImN0eSI6ImFw...') } } // or hasPactsWith('consumers') { pactFileLocation = file('path/to/pacts') stateChangeUrl = url('http://localhost:8001/tasks/pactStateChange') stateChangeUsesBody = false // defaults to true } } } } ``` If the `stateChangeUsesBody` 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. #### Teardown calls for state changes [version 3.2.5/2.4.7+] You can enable teardown state change calls by setting the property `stateChangeTeardown = true` on the provider. This will add an `action` parameter to the state change call. The setup call before the test will receive `action=setup`, and then a teardown call will be made afterwards to the state change URL with `action=teardown`. ### Using a Closure [version 2.2.2+] You can set a closure to be called before each verification with a defined provider state. The closure will be called with the state description from the pact file. ```groovy pact { serviceProviders { provider1 { hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') // Load a fixture file based on the provider state and then setup some database // data. Does not require a state change request so returns false stateChange = { providerState -> def fixture = loadFixtuerForProviderState(providerState) setupDatabase(fixture) } } } } } ``` #### Teardown calls for state changes [version 3.2.5/2.4.7+] You can enable teardown state change calls by setting the property `stateChangeTeardown = true` on the provider. This will add an `action` parameter to the state change closure call. The setup call before the test will receive `setup`, as the second parameter, and then a teardown call will be made afterwards with `teardown` as the second parameter. ```groovy pact { serviceProviders { provider1 { hasPactWith('consumer1') { pactFile = file('path/to/provider1-consumer1-pact.json') // Load a fixture file based on the provider state and then setup some database // data. Does not require a state change request so returns false stateChange = { providerState, action -> if (action == 'setup') { def fixture = loadFixtuerForProviderState(providerState) setupDatabase(fixture) } else { cleanupDatabase() } false } } } } } ``` ## Filtering the interactions that are verified You can filter the interactions that are run using three project properties: `pact.filter.consumers`, `pact.filter.description` and `pact.filter.providerState`. Adding `-Ppact.filter.consumers=consumer1,consumer2` to the command line will only run the pact files for those consumers (consumer1 and consumer2). Adding `-Ppact.filter.description=a request for payment.*` will only run those interactions whose descriptions start with 'a request for payment'. `-Ppact.filter.providerState=.*payment` will match any interaction that has a provider state that ends with payment, and `-Ppact.filter.providerState=` will match any interaction that does not have a provider state. ## Verifying pact files from a pact broker [version 3.1.1+/2.3.1+] You can setup your build to validate against the pacts stored in a pact broker. The pact gradle plugin will query the pact broker for all consumers that have a pact with the provider based on its name. For example: ```groovy pact { serviceProviders { provider1 { hasPactsFromPactBroker('http://pact-broker:5000/') } } } ``` This will verify all pacts found in the pact broker where the provider name is 'provider1'. If you need to set any values on the consumers from the pact broker, you can add a Closure to configure them. ```groovy pact { serviceProviders { provider1 { hasPactsFromPactBroker('http://pact-broker:5000/') { consumer -> stateChange = { providerState -> /* state change code here */ true } } } } } ``` **NOTE: Currently the pacts are fetched from the broker during the configuration phase of the build. This means that if the broker is not available, you will not be able to run any Gradle tasks.** This should be fixed in a forth coming release. In the mean time, to only load the pacts when running the validate task, you can do something like: ```groovy pact { serviceProviders { provider1 { // Only load the pacts from the broker if the start tasks from the command line include pactVerify if ('pactVerify' in gradle.startParameter.taskNames) { hasPactsFromPactBroker('http://pact-broker:5000/') { consumer -> stateChange = { providerState -> /* state change code here */ true } } } } } } ``` ### Using an authenticated Pact Broker You can add the authentication details for the Pact Broker like so: ```groovy pact { serviceProviders { provider1 { hasPactsFromPactBroker('http://pact-broker:5000/', authentication: ['Basic', pactBrokerUser, pactBrokerPassword]) } } } ``` `pactBrokerUser` and `pactBrokerPassword` can be defined in the gradle properties. ## Verifying pact files from a S3 bucket [version 3.3.2+/2.4.17+] Pact files stored in an S3 bucket can be verified by using an S3 URL to the pact file. I.e., ```groovy pact { serviceProviders { provider1 { hasPactWith('consumer1') { pactFile = 's3://bucketname/path/to/provider1-consumer1-pact.json' } } } } ``` **NOTE:** you can't use the `url` function with S3 URLs, as the URL and URI classes from the Java SDK don't support URLs with the s3 scheme. # Publishing pact files to a pact broker [version 2.2.7+] The pact gradle plugin provides a `pactPublish` task that can publish all pact files in a directory to a pact broker. To use it, you need to add a publish configuration to the pact configuration that defines the directory where the pact files are and the URL to the pact broker. For example: ```groovy pact { publish { pactDirectory = '/pact/dir' // defaults to $buildDir/pacts pactBrokerUrl = 'http://pactbroker:1234' } } ``` _NOTE:_ The pact broker requires a version for all published pacts. The `pactPublish` task will use the version of the gradle project by default. Make sure you have set one otherwise the broker will reject the pact files. _Version 3.2.2/2.4.3+_ you can override the version in the publish block. ## Publishing to an authenticated pact broker To publish to a broker protected by basic auth, include the username/password in the `pactBrokerUrl`. For example: ```groovy pact { publish { pactBrokerUrl = 'https://username:[email protected]' } } ``` ### [version 3.3.9+] You can add the username and password as properties since version 3.3.9+ ```groovy pact { publish { pactBrokerUrl = 'https://mypactbroker.com' pactBrokerUsername = 'username' pactBrokerPassword = 'password' } } ``` # Verifying a message provider [version 2.2.12+] The Gradle plugin has been updated to allow invoking test methods that can return the message contents from a message producer. To use it, set the way to invoke the verification to `ANNOTATED_METHOD`. This will allow the pact verification task to scan for test methods that return the message contents. Add something like the following to your gradle build file: ```groovy pact { serviceProviders { messageProvider { verificationType = 'ANNOTATED_METHOD' packagesToScan = ['au.com.example.messageprovider.*'] // This is optional, but leaving it out will result in the entire // test classpath being scanned hasPactWith('messageConsumer') { pactFile = url('url/to/messagepact.json') } } } } ``` Now when the `pactVerify` task is run, will look for methods annotated with `@PactVerifyProvider` in the test classpath that have a matching description to what is in the pact file. ```groovy class ConfirmationKafkaMessageBuilderTest { @PactVerifyProvider('an order confirmation message') String verifyMessageForOrder() { Order order = new Order() order.setId(10000004) order.setExchange('ASX') order.setSecurityCode('CBA') order.setPrice(BigDecimal.TEN) order.setUnits(15) order.setGst(new BigDecimal('15.0')) odrer.setFees(BigDecimal.TEN) def message = new ConfirmationKafkaMessageBuilder() .withOrder(order) .build() JsonOutput.toJson(message) } } ``` It will then validate that the returned contents matches the contents for the message in the pact file. ## Publishing to the Gradle Community Portal To publish the plugin to the community portal: $ ./gradlew :pact-jvm-provider-gradle_2.11:publishPlugins # Verification Reports [versions 3.2.7/2.4.9+] The default behaviour is to display the verification being done to the console, and pass or fail the build via the normal Gradle mechanism. From versions 3.2.7/2.4.9+, additional reports can be generated from the verification. ## Enabling additional reports The verification reports can be controlled by adding a reports section to the pact configuration in the gradle build file. For example: ```groovy pact { reports { defaultReports() // adds the standard console output markdown // report in markdown format json // report in json format } } ``` Any report files will be written to "build/reports/pact". ## Additional Reports The following report types are available in addition to console output (which is enabled by default): `markdown`, `json`.
Last Version: 2.4.20
Release Date:
Last Version: 0.2.0
Release Date:
Last Version: 0.12.3
Release Date:Sonar Integration for Eclipse (documentation)
org.codehaus.sonar-ide.eclipse : org.sonar.ide.eclipse.helpSonar-IDE aims to integrate Sonar into standard IDEs.
Last Version: 0.2.0
Release Date:
Last Version: 1.5.0
Release Date:OAuth 2.0 Custom JWT Token Issuer
org.wso2.samples.is : org.wso2.carbon.identity.extensions.jwt.token.issuerWSO2 Identity Server Samples
Last Version: 4.4.0
Release Date:Last Version: 1.1.0-RC3
Release Date:Bundle-Name (Incubation)
de.dentrassi.eclipse.neoscada.ide : org.eclipse.scada.configuration.ui.projectLast Version: 0.3.0
Release Date:
WSO2 Carbon OAuth data publisher module
org.wso2.carbon.identity.data.publisher.oauth : identity-data-publisher-oauthOauth data publisher
Last Version: 1.4.0
Release Date:Last Version: 1.0.8
Release Date:
Last Version: 0.1.0
Release Date:org.opendaylight.yangide.update-site
org.opendaylight.yangide : org.opendaylight.yangide.update-siteOpenDaylight is leading the transformation to Open Software Defined Networking (SDN). For more information, please see https://www.opendaylight.org
Last Version: 1.1.1
Release Date:
Last Version: 3.0.0
Release Date:
jclouds ElasticHosts Peer1 Toronto provider
org.jclouds.provider : elastichosts-tor-pElasticHosts implementation targeted to Peer1 Toronto
Last Version: 1.6.0
Release Date:Launchers
org.apidesign.bck2brwsr : launcher-pomJava.net - The Source for Java Technology Collaboration
Last Version: 0.54
Release Date:Last Version: 0.16.4-beta
Release Date:Last Version: 0.0.5
Release Date:Tascalate Async/Await - SchedulerResolver / Provided
net.tascalate.async : net.tascalate.async.resolver.providedAsync / Await asynchronous programming model for Java 1.8 - 17+ similar to the functionality available in C# 5. The implementation is based on continuations for Java (see tascalate-javaflow).
Last Version: 1.2.2
Release Date:
Last Version: 1.0.2
Release Date:
WSO2 Carbon - Claim Management Feature Aggregator Module
org.wso2.carbon.identity.framework : claim-mgt-featureWSO2 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: 0.2.3
Release Date:Last Version: 0.5.4
Release Date:Curity Kotlin Authentication Action Archetype
io.curity : identityserver.plugins.archetypes.kotlin-authentication-actionAn archetype that generates the Kotlin source code necessary to create an authentication action plug-in.
Last Version: 2.5.0
Release Date:Faktor-IPS Runtime - EJB Client for Productdataprovider
org.faktorips : faktorips-runtime-productdataprovider-ejbclientEJB Client for Productdataprovider for Faktor-IPS
Last Version: 22.6.0-rfinal
Release Date:jclouds ElasticHosts Amsterdam provider
org.apache.jclouds.provider : elastichosts-ams-eElasticHosts implementation targeted to Amsterdam
Last Version: 2.5.0
Release Date:
Last Version: 0.6.2
Release Date:
play2-oauth2-provider
com.nulab-inc : play2-oauth2-provider_2.10Support scala-oauth2-core library on Playframework Scala
Last Version: 0.16.1
Release Date:
WSO2 Carbon - Identity Provisioning Feature
org.wso2.carbon.identity.framework : provisioning-featureWSO2 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:
WSO2 Carbon Extensions - Crypto Provider HSM
org.wso2.carbon.crypto : carbon-crypto-provider-hsmWSO2 is an open source application development software company focused on providing service-oriented architecture solutions for professional developers.
Last Version: 1.0.3
Release Date:Last Version: 1.1.1
Release Date:
springtainer-elasticsearch
com.avides.springboot.springtainer : springtainer-elasticsearchElasticsearch test-container
Last Version: 1.3.0
Release Date:Last Version: 2.2.0
Release Date:
jclouds Bluelock vCloud Enterprise provider
org.jclouds.provider : bluelock-vcloud-vcenterprisevCloud implementation targeted to Bluelock vCloud Enterprise
Last Version: 1.1.1
Release Date:
Last Version: 2.0.1
Release Date:
org.openidentityplatform.commons.doc-maven-plugin
org.openidentityplatform.commons : doc-maven-pluginCommon machinery for generating core documentation from DocBook XML sources
Last Version: 2.0.15
Release Date:Last Version: 1.0.1
Release Date:
WSO2 Carbon - Identity Token2 Feature
org.wso2.carbon.extension.identity.authenticator : org.wso2.carbon.extension.identity.authenticator.token2.featureThis feature contains extension feature for Token2
Last Version: 1.0.0
Release Date:browser - plugins - discover - providers
io.github.qsy7.java.modules.browser.plugins.discover : providersLast Version: 0.1.0
Release Date:
WSO2 Carbon - Identity Event Module
org.wso2.carbon.identity.framework : identity-eventWSO2 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:
customprovider
org.glassfish.jsonp : customproviderJakarta JSON Processing defines a Java(R) based framework for parsing, generating, transforming, and querying JSON documents.
Last Version: 2.0.0-RC3
Release Date:
OJB :: organization-identification-results-search-service-intermediary :: intermediary
org.ojbc.bundles.intermediaries : organization-identification-results-search-service-intermediaryA component of the OJBC
Last Version: 1.0.2
Release Date: