Aslak Knutsen

SHRINKRES-213 Add support for

Fix test issue with GZIP Compressed response

Apache HTTP Client default add Accept-Encoding: gzip,deflate to

the Request if no Accept-Encoding is given directly.

LIVEOAK-510 Add support for storing JSON Array of Objects

Check the content of the Collection to see if it needs converting as well.

Add Request/Response compression handler

Add Request/Response compression handler

Support decoding application/x-www-form-urlencoded

Support simple www-form-urlencoded message bodies for storage


Message body format:


Remove duplicate slf4j and log4j dependency entries

Use @ArquillianResource URL injection to avoid hardcoding ports

@ArquillianResource URL will inject the web-context URL to the deployed

archive as described by the Container.

e.g. http://localhost:8080/context

Remove unused arquillian.xml configuration

* WildFly 8.0.0.Final use Servlet 3.0 as default protocol

* Servlet protocol configuration has no option executionType

    • -6
    • +0
Remove dependency on wildfly-dist ZIP

Add Eclipse files to gitignore

Use testable=false to avoid Package enrichment

As long as the TestClass is only doing ClientSide tests, it's faster

to use testable=false and by pass the Package Enrichment phase.

With testable=false, @RunAsClient is implied as no InContainer enrichment

is prepared.

Clean up Arquillian/ShrinkWrap dependencies

Only entry point junit-container, resolver dep chain and a container

adapter is needed.

Fix Test method spelling in Highlighter scanners

Let XMLScanner extend HTMLScanner to support type lookup on XML

Register more file extensions to Highlighter Scanners

Add support for YAML to Highlighter

FORGE-1696 Add support for Groovy to Highlighter

Fix spelling in Highlighter State.initial

FORGE-1695 Add support for SQL to Highlighter

populate when --<tab> is called

FORGE-1682 Open HighLighter service to consume Imported<Scanner> instances

  1. … 5 more files in changeset.
FORGE-1681 Add Scanner support for Properties files

Based on the definition from Wikipedia:

Update Console tests to use BaseConsoleTest.invokeTestConsole

invokeTestConsole handles:

* Creation of Pipes

* Creation of Console

* CountDownLatch setup

* Verification Exceptions

invokeTestConsole comes in 3 different varieties:

* Setup, Verify

* CallbackCount, Setup, Verify

* CallbackCount, Setup, Verify, SettingsBuilder

CallbackCount is the CoundDownLatch number to use. How many callbacks

should we wait for before moving on.

Add CountDownLatch and Exceptions List to feed information back to main thread

TestConsoleCallback function as a base class for ConsoleCallback in tests

that takes a CountDownLatch and List<Throwable>.

The TestConsoleCallback expose a verify method that can be used as a

replacement for execute in ConsoleCallback to verify the execution.

The TestConsoleCallback takes care of adding caught exceptions to the

exception list and call the CountDownLatch when done.

Waiting for the CoundDownLatch and re throw of Exceptions caught in the

TestConsoleCallback needs to be done in the Main thread executing the test

method so the errors are reported back to JUnit.

Remove travis ci gradle parallel override

Test failure has nothing to do with running in parallel

Attempt to turn parallel test execution off to avoid random test failure on CI

Add TERM=dumb to travis config to get clean output from gradle

Add TERM=dumb to travis config to get clean output from gradle

Add ReadMe with travis build status image