This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new e356de4 Add test scope to junit
e356de4 is described below
commit e356de4fed868e84a117606a3e294602e15568fb
Author: Claus Ibsen <[email protected]>
AuthorDate: Sat Apr 6 12:36:15 2019 +0200
Add test scope to junit
---
MIGRATION.md | 7 ++++---
core/camel-caffeine-lrucache/pom.xml | 1 +
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/MIGRATION.md b/MIGRATION.md
index 4423c9f..f9a6628 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -18,11 +18,14 @@ In Camel 2.x camel-core was one JAR file, which now has
been splitup into many J
- camel-api
- camel-base
+- camel-caffeine-lrucache
+- camel-cloud
- camel-core
- camel-management-api
- camel-management-impl
- camel-support
- camel-util
+- camel-util-json
Maven users of Apache Camel can keep using the dependency *camel-core* which
will have transitive dependency on all of its modules, and therefore no
migration is needed.
However users whom wants to trim the size of the classes on the classpath, can
use fine grained Maven dependency on only the modules needed.
@@ -47,11 +50,9 @@ We have also modularized many of the core components and
moved them out of `came
- camel-stub
- camel-timer
- camel-validator
+- camel-vm
- camel-xslt
-TODO: there are some remainder components in camel-core we would like to
modularize
-TODO: we need camel-core-minimal dependency for just basic Camel
-
Migrating custom components
---------------------------
diff --git a/core/camel-caffeine-lrucache/pom.xml
b/core/camel-caffeine-lrucache/pom.xml
index f84612b..450f61b 100644
--- a/core/camel-caffeine-lrucache/pom.xml
+++ b/core/camel-caffeine-lrucache/pom.xml
@@ -51,6 +51,7 @@
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
+ <scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
