Download JAR files tagged by define with all dependencies

XLcloud aims to define and demonstrate the principles of HPC as a Service (High Performance Computing) for all those applications that involve highly intensive calculations. XLcloud is designed as a collaborative tool that enables users to work together on highly sophisticated software in the Cloud, thus sidestepping the need for individuals to have to purchase expensive software on their own. XLcloud combines the expertise of companies and academics that are innovative in the field of high performance computer architectures and flow visualization HD/3D and video. While many Internet-based applications are now available on the Cloud, high-performance applications still face a number of technological obstacles before they are cloud ready. For example, high performance applications often need large capacity processing, lots of storage and huge network bandwidth, needs that are difficult to meet in today’s Cloud. In developing HPC as a Service (HaaS), XLcloud has identified the following high performance applications involving research and industrial innovation: * Research environments such as universities or technical institutes where high performance computing is a requirement, * Online game applications, * Online streaming video in real time, * Search engines in real time, * Online three-dimensional imaging for medical use.

InfoScope Library: Simplifying Privacy Policy Display with WebView The InfoScope Library is a versatile tool designed to enhance the seamless presentation of privacy policies through WebView integration. Privacy policies play a crucial role in maintaining transparency and trust between users and applications, and the InfoScope Library streamlines this process by offering a range of convenient features. At its core, the library provides the SimpleAutoWebView, a WebView component equipped with fundamental settings for optimal privacy policy display. This WebView component is tailored to effortlessly load and present privacy policy content to users, ensuring a smooth and user-friendly experience. To further enhance the functionality and customization options, the InfoScope Library includes two essential components: SimpleAutoWebViewClient and SimpleAutoWebChromeClient. These components enable developers to quickly establish and configure the basic WebView behavior and appearance. The SimpleAutoWebViewClient is designed to facilitate the interaction between the WebView and the application. It streamlines the process of handling various events, such as page loading, error handling, and navigation. With this component, developers can swiftly create a WebViewClient that aligns with their application's requirements, promoting a consistent and intuitive user journey. Complementing the WebView functionality, the SimpleAutoWebChromeClient focuses on managing the visual aspects of WebView content, including alert dialogs, JavaScript dialogs, and UI interactions. This component empowers developers to define the behavior and appearance of these elements, ensuring a polished and integrated presentation of the privacy policy content. In summary, the InfoScope Library offers a comprehensive toolkit for developers to seamlessly integrate privacy policy display using WebView. By providing the SimpleAutoWebView, SimpleAutoWebViewClient, and SimpleAutoWebChromeClient components, the library enables swift development and easy customization, fostering transparency and trust between users and applications. Embrace the power of the InfoScope Library to elevate your privacy policy presentation and enhance your user experience.

pact-jvm-consumer-specs2 ======================== ## Specs2 Bindings for the pact-jvm library ## Dependency In the root folder of your project in build.sbt add the line: ```scala libraryDependencies += "au.com.dius.pact.consumer" %% "specs2" % "4.0.1" ``` or if you are using Gradle: ```groovy dependencies { testCompile "au.com.dius.pact.consumer:specs2_2.13:4.0.1" } ``` __*Note:*__ `PactSpec` requires spec2 3.x. Also, for spray users there's an incompatibility between specs2 v3.x and spray. Follow these instructions to resolve that problem: https://groups.google.com/forum/#!msg/spray-user/2T6SBp4OJeI/AJlnJuAKPRsJ ## Usage To author a test, mix `PactSpec` into your spec First we define a service client called `ConsumerService`. In our example this is a simple wrapper for `dispatch`, an HTTP client. The source code can be found in the test folder alongside the `ExamplePactSpec`. Here is a simple example: ``` import au.com.dius.pact.consumer.PactSpec class ExamplePactSpec extends Specification with PactSpec { val consumer = "My Consumer" val provider = "My Provider" override def is = uponReceiving("a request for foo") .matching(path = "/foo") .willRespondWith(body = "{}") .withConsumerTest { providerConfig => Await.result(ConsumerService(providerConfig.url).simpleGet("/foo"), Duration(1000, MILLISECONDS)) must beEqualTo(200, Some("{}")) } } ``` This spec will be run along with the rest of your specs2 unit tests and will output your pact json to ``` /target/pacts/<Consumer>_<Provider>.json ``` # Forcing pact files to be overwritten (3.6.5+) By default, when the pact file is written, it will be merged with any existing pact file. To force the file to be overwritten, set the Java system property `pact.writer.overwrite` to `true`. # Test Analytics We are tracking anonymous analytics to gather important usage statistics like JVM version and operating system. To disable tracking, set the 'pact_do_not_track' system property or environment variable to 'true'.