Skip to content
Java
Branch: master
Clone or download
chrisdennis Merge pull request #550 from mathieucarbou/bugfix
Make sure TCMessageHydrateSink is not triggering a connection close when adding a new incoming message to the queue
Latest commit 3a4747e Jul 31, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.mvn/wrapper
client-message-tracker Fixing tests and dependencies to be compatible with java11. Jul 10, 2019
communicator-support Start 5.7 development Feb 27, 2019
concurrent-map-entity
healthchecker-entity
lease Fixing tests and dependencies to be compatible with java11. Jul 10, 2019
management Based on review idea by @mathieucarbou, make additions generic proper… Jul 26, 2019
offheap-resource Fixing tests and dependencies to be compatible with java11. Jul 10, 2019
platform-base
runnel
tc-config-generator Fixing tests and dependencies to be compatible with java11. Jul 10, 2019
voltron-proxy
.gitignore
Jenkinsfile license Jan 4, 2018
LICENSE
README.adoc 📝 Moved Git Emoji doc at upper level Nov 15, 2016
azure-pipelines.yml
header.txt
mvnw ❄️ Fixing dependency convergence issues and updated enforcer + added … May 19, 2017
mvnw.cmd ❄️ Fixing dependency convergence issues and updated enforcer + added … May 19, 2017
pom.xml use JSONAssert to compare JSON data Jul 25, 2019

README.adoc

terracotta-platform

terracotta platform terracotta platform terracotta platform

Terracotta-OSS@Cloudbees

For Developers

License Headers

This project uses the license-maven-plugin to make sure all license headers are present (including all java and xml files) and conform to the root header.txt (Apache 2 License) Whenever you add a new file, you can automatically have the header added using, at the root level :

mvn com.mycila:license-maven-plugin:format

Otherwise, you would get such an error while building :

[ERROR] Failed to execute goal com.mycila:license-maven-plugin:3.0.rc1:check (default) on project platform-root: Some files do not have the expected license header -> [Help 1]

Git Commit Messages

  • Use the present tense ("Add feature" not "Added feature")

  • Use the imperative mood ("Move cursor to…​" not "Moves cursor to…​")

  • Limit the first line to 72 characters or less

  • Reference issues and pull requests liberally

  • Consider starting the commit message with an applicable emoji:

    • 🎨 :art: when improving the format/structure of the code

    • 🐎 :racehorse: when improving performance

    • 🚱 :non-potable_water: when plugging memory leaks

    • 📝 :memo: when writing docs

    • 🐧 :penguin: when fixing something on Linux

    • 🍎 :apple: when fixing something on Mac OS

    • 🏁 :checkered_flag: when fixing something on Windows

    • 🐛 :bug: when fixing a bug

    • 🔥 :fire: when removing code or files

    • 💚 :green_heart: when fixing the CI build

    • :white_check_mark: when adding tests

    • 🔒 :lock: when dealing with security

    • ⬆️ :arrow_up: when upgrading dependencies

    • ⬇️ :arrow_down: when downgrading dependencies

    • 👕 :shirt: when removing linter warnings

    • 🔈 :speaker: when adding logging

    • 🔇 :mute: when reducing logging

    • 💡 :bulb: new idea

    • 🚧 :construction: work in progress

    • :heavy_plus_sign: when adding feature

    • :heavy_minus_sign: when removing feature

    • ❄️ :snowflake: when changing configuration, setting, build file, etc

(adapted from Atom guidelines)

You can’t perform that action at this time.