GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-6/pull/158
Fixing ServiceLocator and Logger errors
since I fixed the testsuite by separating XA tests and ByteMan tests I've
broken some of that integration which I'm now fixing
I'm also fixing some of the LoggerNot found messages that we would see on
the tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-6 master-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-6/pull/158.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #158
----
commit d101bcbf59bdbd1ad587b65c39903bcd70092fb4
Author: Clebert Suconic <clebertsuco...@apache.org>
Date: 2015-03-07T03:17:14Z
Fixing ServiceLocator on the testsuite
My previous commit broke the location of the ServiceUtil /
TransactionManagerLocator
This commit is setting a new DummyTM on the integration-tests-suite and the
proper TM Locator on the extra-tests
commit e40dc2c4e66a06761869703e26eace49bbb1e778
Author: Clebert Suconic <clebertsuco...@apache.org>
Date: 2015-03-07T03:55:03Z
Fixing Logger errors on the testsuite
There are a few testsuites (like proton) that don't have the proper
LogManager in place
even though the command line is setting it
For that reason we are adding the proper libraries in place
and also a dependency to activemq-commonts/testsuite since the
AssertionLogHandler is used on all the testsuite
----
---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
