IDE

JBox2d OSGI Wrapper

org.apidesign.bck2brwsr : jbox2d-osgi

Java.net - The Source for Java Technology Collaboration

Last Version: 0.19

Release Date: Apr 30, 2016

Configuration Editor

de.dentrassi.eclipse.neoscada.ide : org.eclipse.scada.configuration.world.editor

Last Version: 0.3.0

Release Date: Sep 23, 2016

WSO2 Carbon Identity - Outbound Authentication Feature Category

org.wso2.carbon.identity.feature.category : org.wso2.carbon.identity.outbound.authentication.category.feature

This feature contains outbound authentication related features.

Last Version: 1.0.18

Release Date: Aug 26, 2020

WSO2 Carbon - Provisioning Aggregator Module

org.wso2.carbon.identity.framework : provisioning

This is a Carbon bundle that represent the Provisioning Aggregator module.

Last Version: 5.20.324

Release Date: Mar 3, 2022

AEM Permission Management :: Parent

com.cognifide.cq : cqsm

AEM Permission Management - AEM based tool focused on streamlining the permission configuration

Last Version: 3.2.0

Release Date: Jun 4, 2019

Bonita - Identity Service

org.ow2.bonita : bonita-identity

The OW2 Consortium is an open source community committed to making available to everyone the best and most reliable middleware technology. OW2 mission is to develop open source code middleware and to foster a vibrant community and business ecosystem.

Last Version: 4.1.1

Release Date: May 15, 2009

IdentityConnectors

org.syncope.identityconnectors : identityconnectors

Identity Connectors

Last Version: 0.4.3

Release Date: May 6, 2011

Test data generator

com.presidentio : test-data-generator

Tools to generate data for testing

Last Version: 1.0.3

Release Date: Mar 26, 2015

product-identifier

com.mastercard.api : product-identifier

Java Core SDK for use with SDKs available on MasterCard Developer Zone (https://developer.mastercard.com)

Last Version: 1.0.0

Release Date: Apr 5, 2019

EOSIO SDK for Java: Android Keystore Signature Provider

one.block : eosioandroidkeystoresignatureprovider

This provider is intended to be used in conjunction with EOSIO SDK for Java as a provider plugin..

Last Version: 1.0.0

Release Date: Apr 26, 2021

lock-provider

com.inomera.telco.commons : lock-provider-hazelcast-4x

Distributed locks made easy

Last Version: 2.0.0

Release Date: Nov 24, 2021

org.openidentityplatform.openam.oauth

org.openidentityplatform.openam : oauth

Parent POM for Open Identity Platform Community projects. Provides default project build configuration.

Last Version: 14.6.6.1

Release Date: Jun 24, 2022

spring-session-appengine

org.hidetake : spring-session-appengine

Spring Session Integration for App Engine

Last Version: 0.9.0

Release Date: Oct 22, 2017

Provided dependencies maven-plugin

org.sonatype.plugins : provided-dependencies-maven-plugin

${project.name}

Last Version: 1.6

Release Date: Mar 4, 2013

org.opendaylight.yangide.core

org.opendaylight.yangide : org.opendaylight.yangide.core

OpenDaylight 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: Sep 8, 2016

redis-sidecar

com.redis : redis-sidecar-jdbc

Redis-Sidecar JDBC Driver

Last Version: 0.1.0

Release Date: May 24, 2022

CardReaderProvider-NFC-Android

de.gematik.ti : cardreader.provider.nfc

The CardReaderProvider-NFC-Android library provides functionality to use the NFC interface on Android devices.

Last Version: 1.1.2

Release Date: Jan 16, 2020

tencentcloud-sdk-java-iotvideoindustry

com.tencentcloudapi : tencentcloud-sdk-java-iotvideoindustry

Tencent Cloud Open API SDK for Java

Last Version: 3.1.538

Release Date: Jun 27, 2022

org.openidentityplatform.commons.selfservice.example

org.openidentityplatform.commons.selfservice : example

Some basic self service examples.

Last Version: 2.0.15

Release Date: May 31, 2022

Example JUnit4 Resource Provider

org.testifyproject.examples : example-junit-resourceprovider

Creates a new quickstart project that demonstractes ResourceProvider SPI contract implementation.

Last Version: 1.0.0

Release Date: Jan 4, 2018

pact-jvm-provider-maven_2.10

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

Maven plugin to verify a provider [version 2.1.9+] ================================================== Maven plugin for verifying pacts against a provider. The Maven plugin provides a `verify` goal which will verify all configured pacts against your provider. ## To Use It ### 1. Add the pact-jvm-provider-maven plugin to your `build` section of your pom file. ```xml <build> [...] <plugins> [...] <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> </plugin> [...] </plugins> [...] </build> ``` ### 2. Define the pacts between your consumers and providers You define all the providers and consumers within the configuration element of the maven plugin. ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <!-- You can define as many as you need, but each must have a unique name --> <serviceProvider> <name>provider1</name> <!-- All the provider properties are optional, and have sensible defaults (shown below) --> <protocol>http</protocol> <host>localhost</host> <port>8080</port> <path>/</path> <consumers> <!-- Again, you can define as many consumers for each provider as you need, but each must have a unique name --> <consumer> <name>consumer1</name> <!-- currently supports a file path using pactFile or a URL using pactUrl --> <pactFile>path/to/provider1-consumer1-pact.json</pactFile> </consumer> </consumers> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` ### 3. Execute `mvn pact:verify` You will have to have your provider running for this to pass. ## Verifying all pact files in a directory for a provider. [2.1.10+] You can specify a directory that contains pact files, and the Pact plugin will scan for all pact files that match that provider and define a consumer for each pact file in the directory. Consumer name is read from contents of pact file. ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <!-- You can define as many as you need, but each must have a unique name --> <serviceProvider> <name>provider1</name> <!-- All the provider properties are optional, and have sensible defaults (shown below) --> <protocol>http</protocol> <host>localhost</host> <port>8080</port> <path>/</path> <pactFileDirectory>path/to/pacts</pactFileDirectory> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` ## 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</insecure>` on the provider. ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <pactFileDirectory>path/to/pacts</pactFileDirectory> <insecure>true</insecure> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` ## Specifying a custom trust store [version 2.2.8+] For environments that are running their own certificate chains: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <pactFileDirectory>path/to/pacts</pactFileDirectory> <trustStore>relative/path/to/trustStore.jks</trustStore> <trustStorePassword>changeit</trustStorePassword> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` `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 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 Pact Maven plugin provides a request filter that can be set to a Groovy script on the provider that will be called before the request is made. This script will receive the HttpRequest bound to a variable named `request` prior to it being executed. ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <requestFilter> // This is a Groovy script that adds an Authorization header to each request request.addHeader('Authorization', 'oauth-token eyJhbGciOiJSUzI1NiIsIm...') </requestFilter> <consumers> <consumer> <name>consumer1</name> <pactFile>path/to/provider1-consumer1-pact.json</pactFile> </consumer> </consumers> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` __*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 [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: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <createClient> // This is a Groovy script that will enable the client to accept self-signed certificates import org.apache.http.ssl.SSLContextBuilder import org.apache.http.conn.ssl.NoopHostnameVerifier import org.apache.http.impl.client.HttpClients HttpClients.custom().setSSLHostnameVerifier(new NoopHostnameVerifier()) .setSslcontext(new SSLContextBuilder().loadTrustMaterial(null, { x509Certificates, s -> true }) .build()) .build() </createClient> <consumers> <consumer> <name>consumer1</name> <pactFile>path/to/provider1-consumer1-pact.json</pactFile> </consumer> </consumers> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` ## 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 properties can be specified with `-Dproperty=value` on the command line or in the configuration section: |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 in the configuration section: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <consumers> <consumer> <name>consumer1</name> <pactFile>path/to/provider1-consumer1-pact.json</pactFile> </consumer> </consumers> </serviceProvider> </serviceProviders> <configuration> <pact.showStacktrace>true</pact.showStacktrace> </configuration> </configuration> </plugin> ``` ## 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 stateChangeUsesBody 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. ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <stateChangeUrl>http://localhost:8080/tasks/pactStateChange</stateChangeUrl> <stateChangeUsesBody>false</stateChangeUsesBody> <!-- defaults to true --> <consumers> <consumer> <name>consumer1</name> <pactFile>path/to/provider1-consumer1-pact.json</pactFile> <stateChangeUrl>http://localhost:8080/tasks/pactStateChangeForConsumer1</stateChangeUrl> <stateChangeUsesBody>false</stateChangeUsesBody> <!-- defaults to true --> </consumer> </consumers> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` 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. As for normal requests (see Modifying the requests before they are sent), a state change request can be modified before it is sent. Set `stateChangeRequestFilter` to a Groovy script on the provider that will be called before the request is made. #### 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</stateChangeTeardown>` 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`. ## 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 plugin will query the pact broker for all consumers that have a pact with the provider based on its name. To use it, just configure the `pactBrokerUrl` or `pactBroker` value for the provider with the base URL to the pact broker. For example: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <stateChangeUrl>http://localhost:8080/tasks/pactStateChange</stateChangeUrl> <pactBrokerUrl>http://pact-broker:5000/</pactBrokerUrl> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` ### Verifying pacts from an authenticated pact broker [version 3.3.5+] If your pact broker requires authentication (basic authentication is only supported), you can configure the username and password to use by configuring the `authentication` element of the `pactBroker` element of your provider. For example: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <stateChangeUrl>http://localhost:8080/tasks/pactStateChange</stateChangeUrl> <pactBroker> <url>http://pactbroker:1234</url> <authentication> <username>test</username> <password>test</password> </authentication> </pactBroker> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` ### Verifying pacts from an pact broker that match particular tags [version 3.3.5+] If your pacts in your pact broker have been tagged, you can set the tags to fetch by configuring the `tags` element of the `pactBroker` element of your provider. For example: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>provider1</name> <stateChangeUrl>http://localhost:8080/tasks/pactStateChange</stateChangeUrl> <pactBroker> <url>http://pactbroker:1234</url> <tags> <tag>TEST</tag> <tag>DEV</tag> </tags> </pactBroker> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` This example will fetch and validate the pacts for the TEST and DEV tags. ## 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 `-Dpact.filter.consumers=consumer1,consumer2` to the command line or configuration section will only run the pact files for those consumers (consumer1 and consumer2). Adding `-Dpact.filter.description=a request for payment.*` will only run those interactions whose descriptions start with 'a request for payment'. `-Dpact.filter.providerState=.*payment` will match any interaction that has a provider state that ends with payment, and `-Dpact.filter.providerState=` will match any interaction that does not have a provider state. # Verifying a message provider [version 2.2.12+] The Maven 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 maven pom file: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>messageProvider</name> <verificationType>ANNOTATED_METHOD</verificationType> <!-- packagesToScan is optional, but leaving it out will result in the entire test classpath being scanned. Set it to the packages where your annotated test method can be found. --> <packagesToScan> <packageToScan>au.com.example.messageprovider.*</packageToScan> </packagesToScan> <consumers> <consumer> <name>consumer1</name> <pactFile>path/to/messageprovider-consumer1-pact.json</pactFile> </consumer> </consumers> </serviceProvider> </serviceProviders> </configuration> </plugin> ``` Now when the pact verify 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. ## Changing the class path that is scanned By default, the test classpath is scanned for annotated methods. You can override this by setting the `classpathElements` property: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <serviceProviders> <serviceProvider> <name>messageProvider</name> <verificationType>ANNOTATED_METHOD</verificationType> <consumers> <consumer> <name>consumer1</name> <pactFile>path/to/messageprovider-consumer1-pact.json</pactFile> </consumer> </consumers> </serviceProvider> </serviceProviders> <classpathElements> <classpathElement> build/classes/test </classpathElement> </classpathElements> </configuration> </plugin> ``` # Publishing pact files to a pact broker [version 3.2.0+] The pact maven plugin provides a `publish` mojo 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 POM that defines the directory where the pact files are and the URL to the pact broker. For example: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.8</version> <configuration> <pactDirectory>path/to/pact/files</pactDirectory> <!-- Defaults to ${project.basedir}/target/pacts --> <pactBrokerUrl>http://pactbroker:1234</pactBrokerUrl> <projectVersion>1.0.100</projectVersion> <!-- Defaults to 2.4.20 --> <trimSnapshot>true</trimSnapshot> <!-- Defaults to false --> </configuration> </plugin> ``` You can now execute `mvn pact:publish` to publish the pact files. _NOTE:_ The pact broker requires a version for all published pacts. The `publish` task will use the version of the project by default, but can be overwritten with the `projectVersion` property. Make sure you have set one otherwise the broker will reject the pact files. _NOTE_: By default, the pact broker has issues parsing `SNAPSHOT` versions. You can configure the publisher to automatically remove `-SNAPSHOT` from your version number by setting `trimSnapshot` to true. This setting does not modify non-snapshot versions. ## Publishing to an authenticated pact broker [version 3.3.9+] For an authenticated pact broker, you can pass in the credentials with the `pactBrokerUsername` and `pactBrokerPassword` properties. Currently it only supports basic authentication. For example: ```xml <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>3.3.9</version> <configuration> <pactBrokerUrl>http://pactbroker:1234</pactBrokerUrl> <pactBrokerUsername>USERNAME</pactBrokerUsername> <pactBrokerPassword>PASSWORD</pactBrokerPassword> </configuration> </plugin> ```

Last Version: 2.4.20

Release Date: Apr 14, 2018

Sling IDE Tools: FileVault Implementation Tests

org.apache.sling.ide : org.apache.sling.ide.impl-vlt-test

The Apache Software Foundation provides support for the Apache community of open-source software projects. The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. We consider ourselves not simply a group of projects sharing a server, but rather a community of developers and users.

Last Version: 1.0.0

Release Date: Jun 30, 2014

org.wso2.carbon.identity.api.server.oidc.scope.management

org.wso2.carbon.identity.server.api : org.wso2.carbon.identity.api.server.oidc.scope.management

Last Version: 1.1.3

Release Date: Feb 17, 2022

onos-providers-openflow-group

org.onosproject : onos-providers-openflow-group

Open Network Operating System Base Pom

Last Version: 1.8.9

Release Date: Jun 23, 2017

providers

io.github.qsy7.java.modules.encryption.modules.cli : providers

Last Version: 0.1.2

Release Date: Apr 8, 2022

Ride Utils

se.alipsa : rideutils

Java FX GUI utilities for use in Renjin applications e.g. Ride

Last Version: 1.8.4

Release Date: Mar 25, 2022

mq-provider-racket

com.kolibrifx.mq : mq-provider-racket

A message bus implementation backed by a custom Redis pub/sub client.

Last Version: 1.0.0

Release Date: Dec 7, 2017

zio-aws-kinesisvideo

io.github.vigoo : zio-aws-kinesisvideo_2.12

Low-level AWS wrapper for ZIO

Last Version: 4.17.104.1

Release Date: Jun 19, 2022

WSO2 Carbon CAS

org.wso2.carbon.extension.identity.authenticator.inbound.cas : identity-inbound-auth-cas

Last Version: 2.0.18

Release Date: Sep 23, 2021

jersey-fastinfoset-provider

com.jecklgamis : jersey-fastinfoset-provider

Jersey 2 FastInfoset Provider

Last Version: 1.0

Release Date: Feb 28, 2017

Eclipse NeoSCADA IDE (Incubation)

de.dentrassi.eclipse.neoscada.ide : org.eclipse.scada.ide

Last Version: 0.3.0

Release Date: Sep 23, 2016

WSO2 Carbon - Service Stubs - Aggregator Module

org.wso2.carbon.identity : carbon-service-stubs

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

Last Version: 5.5.0-m4

Release Date: Aug 5, 2016

Bck2Brwsr Maven Plugin

org.apidesign.bck2brwsr : bck2brwsr-maven-plugin

Java.net - The Source for Java Technology Collaboration

Last Version: 0.54

Release Date: Sep 12, 2021

zio-testcontainers

com.github.sideeffffect : zio-testcontainers_2.12

Last Version: 0.3.0

Release Date: Mar 6, 2022

WSO2 Carbon - Authenticator Feature Aggregator Module

org.wso2.carbon.identity : authenticator-features

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: Sep 3, 2015

bootstrapslider

org.openmole.scaladget : bootstrapslider_sjs1_2.12

Last Version: 1.3.7

Release Date: Jun 17, 2020

AEM Permission Management

com.cognifide.aem : apm-examples

AEM Permission Management is an AEM based tool focused on streamlining the permission configuration

Last Version: 4.3.1

Release Date: May 20, 2020

markscheider

org.zalando : markscheider_2.11

Last Version: 2.6.0

Release Date: Aug 22, 2017

videojs-playlist

org.webjars.npm : github-com-brightcove-videojs-playlist

WebJar for videojs-playlist

Last Version: 2.4.0

Release Date: Jun 29, 2016

nifi-ldap-iaa-providers-bundle

org.apache.nifi : nifi-ldap-iaa-providers-bundle

Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data.

Last Version: 1.16.3

Release Date: Jun 14, 2022

Apache JSTL for Android.

com.github.demidenko05 : a-apache-jstl

Adapted Apache JSTL for Android.

Last Version: 1.0.5

Release Date: Jan 31, 2018

Microsoft Bing VideoSearch SDK

com.microsoft.bing : bing-videosearch

This module contains the client library for Microsoft Bing VideoSearch APIs.

Last Version: 1.0.0

Release Date: Jan 11, 2021

providers-mychain

com.alipay.chainstack : providers-mychain

An all-in-one dapp development tool.

Last Version: 2.0.3-rc

Release Date: May 6, 2022

ng-click-outside

org.webjars.npm : ng-click-outside

WebJar for ng-click-outside

Last Version: 4.0.0

Release Date: Jan 21, 2019

deepsampler-provider

de.ppi : deepsampler-provider

This module is the base for implementing custom stub-provider.

Last Version: 2.1.0

Release Date: May 11, 2022

org.openidentityplatform.commons.authn-filter

org.openidentityplatform.commons : authn-filter

Open Identity Platform CommunityAuthentication and Authorization common filters

Last Version: 2.0.15

Release Date: May 31, 2022

Sling Installer Vault Package Install Hook

org.apache.sling : org.apache.sling.installer.provider.installhook

Can be used in packages to ensure installation of bundles/configs is triggered during package installation and is finished once the package manager returns (circumventing the asynchronicity of org.apache.sling.installer.provider.jcr)

Last Version: 1.1.0

Release Date: Dec 21, 2019

splitties-views-dsl-ide-preview

com.louiscad.splitties : splitties-views-dsl-ide-preview-android

A collection of light, general purpose Android libraries in Kotlin.

Last Version: 3.0.0

Release Date: Aug 20, 2021

contextprovider-servlet-parent

io.tracee.contextlogger.contextprovider : contextprovider-servlet-parent

Please refer to https://github.com/tracee/contextlogger.

Last Version: 0.11.0

Release Date: Nov 10, 2015

io.github.belgif.openapi:belgif-openapi-person-identifier

io.github.belgif.openapi : belgif-openapi-person-identifier

OpenAPI data types related to person identifiers

Last Version: 1.0.0

Release Date: Dec 9, 2020