Download JAR files tagged by folder with all dependencies

OpenCms-Module 'org.opencms.welcome'. <p>This module contains the OpenCms welcome page and release notes.</p> <p>Install this module as a simple demonstration for the template capabilities of OpenCms 8.5.</p> <p><strong>Note:</strong> Deleting this module will remove the "/release" folder and all pages there.</p> <p><i>(c) 2013 by Alkacon Software GmbH (http://www.alkacon.com).</i></p> OpenCms is a Content Management System that is based on Open Source Software. Complex Intranet and Internet websites can be quickly and cost-effectively created, maintained and managed.

This project produces the Mojo that can build a proper release.xml for the SQuirreLSQL update site, given a directory where the updated jar artifacts are located. This plugin accepts a directory in it's configuration and expects to find three sub-directories there : core, plugins and i18n. It then categorizes the artifacts found in those directories accordingly in the final release.xml file, that is generated in the specified folder.

<p>Sometimes while programming in NetBeans you want to explore a particular file that you are editing on the file system browser, or maybe launch a command in a terminal to do something with it.</p> <p>This plugins brings to your NetBeans six action, three of them always available and three of them available when the selected node has a file assiociated with it.<br/> In particular:<p><p><em>When the selection has a valid file</em></p> <ul> <li><strong>Open the default OS shell</strong> on the location of the file (or its folder) selected.</li> <li><strong>Open the file system browser</strong> on the location of the file (or its folder) selected.</li> <li><strong>Copy to the clipboard</strong> the path of the file selected.</li> </ul> <p><em>Always enabled:</em></p> <ul> <li><strong>Launch a shell command</strong> (with parameters, customizable on preferences)</li> <li><strong>FileSystem browser on any location</strong> (favorites, customizable on preferences)</li> <li><strong>Open a shell on any location</strong> (favorites, customizable on preferences)</li> </ul>

According to Docker best practices a Docker container should not be up if the process fails to load properly. Apache Tomcat deploys all the web applications loaded in its webapp folder. This is a resilient solution for web applications not influencing the application server. However, In a Docker environment according to best practice, the process should fail in case the web application failed to initialize properly. By adding the additional jar created by this project to Tomcat classpath and adding the new listener in the Tomcat conf/server.xml the user can make sure the Tomcat process fails in case there is an initialization exception in their web application which will cause the Tomcat used the tomcat container to abort in immediately indicate that there was an initialization error Abort tomcat when a webapp fails to deploy in Docker container Docker container best practice. Tomcat does not stop if a webapp fail to deploy and the container will continue to run. By adding this listener the tomcat will abort in case the Tomcat fails to deploy the webapp, And the container will not start. You will need to place the listener in Tomcat server.xml and set the Tomcat classpath to contain this jar

This Tool provides the means to monitor the performance of Spring Batch applications without the need to manipulate the respective code basis. Through Listeners and AOP it evaluates the throughput of a monitored Job and writes the result to a simble database-schema (a file-based H2 by default). It measures the performance of Job, Step, Chunk, Reader/Processor/Writer/Tasklet down to indivdual Items. Installation/Usage: 1. Add the springBatchPerformanceMonitoring-dependency to your POM 2. Add the de.viadee.spring.batch.infrastructure.Configurator.class to your Spring-Application-Context (via @Import on your Configuration) 3. Run the Job 4. By default the monitoring result is written to project-folder/target/database/monitoringDB.mv.db

Customizable cruft-free Scala archetype. Options: -sourceFolders: [all-in-src-java, scala-only, both-split-src]. DEFAULT: all-in-src-java. --all-in-src-java: Scala and Java code are both in src/main/java (same for test). Plays nicely with IDEs. --scala-only: only src/main/scala set up, and set as source folder. --both-split-src: both src/main/java and src/main/scala. Can play merry havock with IDEs, so not the default. -testLibrary: [scalatest, specs2, scalacheck-only, junit-only]. DEFAULT: scalatest. --scalatest: adds Scalatest AND Scalacheck AND JUnit for most of your testing needs. --specs2: adds specs2 AND Scalacheck AND JUnit. --scalacheck-junit: adds Scalacheck AND JUnit. --junit-only: adds JUnit ONLY. -scalaVersion: 2.10.x+. DEFAULT: 2.11.2. *The Scala tool version is generated automatically. *Some Scala versions may not be compatible with selected test library versions. Adjust as necessary.

A Maven Mojo to download and "degenerate" non-maven projects into sources and binaries This MOJO is supposed to scrape and "de-generate" a zip file containing jars into a project's generated-sources folder, skipping items provided in the `src/` folder. It is intended to "mavenize-with-changes" an existing project and allow the user (of the Mojo) to replace classes which they do not have the ability/desire to recompile without setting up a full build. It can also be used to import non-maven projects by not changing anything. The itch I wanted to scratch was mostly to port libGDX to Maven, while replacing the native methods on Matrix4, without rebuilding the whole project. In essence - it's an alternative to patching someone else's project.

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 += &quot;au.com.dius&quot; %% &quot;pact-jvm-consumer-specs2&quot; % &quot;3.2.11&quot; ``` or if you are using Gradle: ```groovy dependencies { testCompile &quot;au.com.dius:pact-jvm-consumer-specs2_2.11:3.2.11&quot; } ``` __*Note:*__ `PactSpec` requires spec2 3.x. Also, for spray users there&apos;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 = &quot;My Consumer&quot; val provider = &quot;My Provider&quot; override def is = uponReceiving(&quot;a request for foo&quot;) .matching(path = &quot;/foo&quot;) .willRespondWith(body = &quot;{}&quot;) .withConsumerTest { providerConfig =&gt; Await.result(ConsumerService(providerConfig.url).simpleGet(&quot;/foo&quot;), Duration(1000, MILLISECONDS)) must beEqualTo(200, Some(&quot;{}&quot;)) } } ``` This spec will be run along with the rest of your specs2 unit tests and will output your pact json to ``` /target/pacts/&lt;Consumer&gt;_&lt;Provider&gt;.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`.

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: ``` libraryDependencies += "au.com.dius" %% "pact-jvm-consumer-specs2" % "2.0.6" ``` ## Usage To author a test, extend `PactSpec` Here is a simple example: ``` import au.com.dius.pact.consumer.PactSpec class ExamplePactSpec extends PactSpec { val consumer = "My Consumer" val provider = "My Provider" uponReceiving("a request for foo") .matching(path = "/foo") .willRespondWith(body = "{}") .during { providerConfig => ConsumerService(providerConfig.url).simpleGet("/foo") must beEqualTo(200, Some("{}")).await } } ``` 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 ```

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 += &quot;au.com.dius&quot; %% &quot;pact-jvm-consumer-specs2&quot; % &quot;3.2.2&quot; ``` or if you are using Gradle: ```groovy dependencies { testCompile &quot;au.com.dius:pact-jvm-consumer-specs2_2.11:3.2.2&quot; } ``` __*Note:*__ `PactSpec` requires spec2 3.x. Also, for spray users there&apos;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 = &quot;My Consumer&quot; val provider = &quot;My Provider&quot; override def is = uponReceiving(&quot;a request for foo&quot;) .matching(path = &quot;/foo&quot;) .willRespondWith(body = &quot;{}&quot;) .withConsumerTest { providerConfig =&gt; Await.result(ConsumerService(providerConfig.url).simpleGet(&quot;/foo&quot;), Duration(1000, MILLISECONDS)) must beEqualTo(200, Some(&quot;{}&quot;)) } } ``` This spec will be run along with the rest of your specs2 unit tests and will output your pact json to ``` /target/pacts/&lt;Consumer&gt;_&lt;Provider&gt;.json ```