Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Log4j Appender #1616

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: RA #1616

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Blueprint #1616

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Tooling #1616

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Partition Management #1616

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Console #1616

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy #1616

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ #1616

See

[GitHub] activemq-artemis pull request: ARTEMIS-525 Adding test on interrup...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/524 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] activemq-artemis pull request: new logging.properties and trace fo...

Github user jbertram commented on the pull request: https://github.com/apache/activemq-artemis/pull/523#issuecomment-220125612 IMO it's a bit verbose for normal test logging, but I can see how it might be useful for actual traces. --- If your project is set up for it, you can reply

[GitHub] activemq-artemis pull request: new logging.properties and trace fo...

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/523#issuecomment-220126181 @jbertram we may change just the .traces... I have been finding it more useful to read through as it gets more visual. --- If your project is set up

[GitHub] activemq-artemis pull request: new logging.properties and trace fo...

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/523#issuecomment-220117175 If everyone usually working on this branch could review it please? --- If your project is set up for it, you can reply to this email and have your

[GitHub] activemq-artemis pull request: new logging.properties and trace fo...

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-artemis/pull/523#issuecomment-220116931 I find this tracing format easier to read (especially when going through actual traces.log). To see if you like it, make the following

[GitHub] activemq-artemis pull request: new logging.properties and trace fo...

GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-artemis/pull/523 new logging.properties and trace format You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-artemis

[GitHub] activemq-artemis pull request: ARTEMIS-523 re-order SASL mechs

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/521 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] activemq-artemis pull request: A few fixes I have been working on

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/522 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the