Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
[AESH-223] more work

    • -0
    • +14
    • -0
    • +8
[AESH-223] further work

[AESH-223] added pipeline processing

    • -0
    • +21
    • -0
    • +80
[AESH-223] initial attempt on changing the CommandResult

    • -2
    • +4
    • -0
    • +8
    • -0
    • +25
  1. … 8 more files in changeset.
dev cycle 0.53

ready to release 0.52

[AESH-225] completion should work as expected when the completions size is over the set threshold.

[AESH-222] should also define the validatorinvocation value types for the validatorinvocationprovider

[AESH-222] validators should be able to get the command and context object while validating

[AESH-222] populate command when option name is not set

should populate before listing possible option names

make sure that the command object is populated when doing completion

0.52 dev cycle

0.51 release

console and exportmanager might be null

fixed vitests ignoring redirection and multiline tests for now...

    • -144
    • +370
Merge pull request #53 from aslakknutsen/test_failure

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

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 travis build status image

Merge pull request #52 from aslakknutsen/travis_fix

Make the travis.yml file hidden

fixed checkstyle

Make the travis.yml file hidden

Merge pull request #51 from aslakknutsen/travis

Add travis-ci configuration

Add travis-ci configuration

Builds on OpenJDK 7, OracleJDK 7 and OracleJDK 8

added specific executorservice for the execution reader, plus some cleanups

    • -27
    • +17
each process is given a unique pid