[camel] branch master updated: Added list of splitted JARs for camel-core in Migration Guide

[ac...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

acosentino 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 66947c8  Added list of splitted JARs for camel-core in Migration Guide
66947c8 is described below

commit 66947c8345554c49c24cecdba62d68da4affd7c7
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Tue Feb 5 17:02:01 2019 +0100

    Added list of splitted JARs for camel-core in Migration Guide
---
 MIGRATION.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/MIGRATION.md b/MIGRATION.md
index aa79cef..29222fb 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -16,9 +16,13 @@ Modularization of camel-core
 One of the biggest change is the modularization of camel-core.
 In Camel 2.x camel-core was one JAR file, which now has been splitup into many JARs as follows:
 
-TODO: as table of all the modules
-- camel-core
 - camel-api
+- camel-base
+- camel-core
+- camel-management-api
+- camel-management-impl
+- camel-support
+- camel-util
  
 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.