GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1753
CAMEL-11395-maven update surefire
[INFO] Camel :: Integration Tests :: Test Bundles ......... SUCCESS [
3.575 s]
[INFO] Camel :: Integration Tests :: Test Bundles: mock-javamail-1.7
SUCCESS [ 9.386 s]
[INFO] Camel :: Integration Tests ......................... SUCCESS [
1.132 s]
[INFO] Camel :: Integration Tests :: Standalone ........... SUCCESS [
5.973 s]
[INFO] Camel :: Integration Tests :: Non OSGi ............. SUCCESS [13:55
min]
[INFO] Camel :: Integration Tests :: CDI .................. SUCCESS [
15.606 s]
[INFO] Camel :: Integration Tests :: Blueprint CXF Tests .. SUCCESS [
40.728 s]
[INFO] Camel :: Integration Tests :: Blueprint ............ SUCCESS [
7.519 s]
[INFO] Camel :: Integration Tests :: Partial Classpath .... SUCCESS [
4.031 s]
[INFO] Camel :: Integration Tests :: TypeConverter Scan ... SUCCESS [
3.566 s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 15:29 min
[INFO] Finished at: 2017-06-10T14:28:08+03:00
[INFO] Final Memory: 78M/990M
[INFO]
------------------------------------------------------------------------
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/onders86/camel CAMEL-11395
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1753.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 #1753
----
commit 83fef43f4d53d686d81626192ce5978cf93cffa7
Author: onders86 <ondersezgin+git...@gmail.com>
Date: 2017-06-10T11:37:20Z
CAMEL-11395-maven update surefire
----
---
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.
---
