Repository: karaf Updated Branches: refs/heads/master 55ce22850 -> 3c381cf80
removed the DS part of the refactoring in the RELEASE-NOTES Project: http://git-wip-us.apache.org/repos/asf/karaf/repo Commit: http://git-wip-us.apache.org/repos/asf/karaf/commit/3c381cf8 Tree: http://git-wip-us.apache.org/repos/asf/karaf/tree/3c381cf8 Diff: http://git-wip-us.apache.org/repos/asf/karaf/diff/3c381cf8 Branch: refs/heads/master Commit: 3c381cf80efef11884d71798b7e5acab5228c309 Parents: 55ce228 Author: anierbeck <[email protected]> Authored: Fri Oct 10 20:07:59 2014 +0200 Committer: anierbeck <[email protected]> Committed: Fri Oct 10 20:07:59 2014 +0200 ---------------------------------------------------------------------- RELEASE-NOTES | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/karaf/blob/3c381cf8/RELEASE-NOTES ---------------------------------------------------------------------- diff --git a/RELEASE-NOTES b/RELEASE-NOTES index 64bc83b..babdef9 100644 --- a/RELEASE-NOTES +++ b/RELEASE-NOTES @@ -22,7 +22,7 @@ Apache Karaf 4.0.0.M1 represents a major refactoring of the project, and includes numerous new features. We ask that users provide the community with their feed back so that the full Apache Karaf 4.0.0 release can be as feature complete and stable as possible. - The 4.0.x line will ship with OSGi Rev5 support via Felix 4.4.1 and Equinox 3.9.1-v20140110-1610, and a completely refactored internal framework based on Declarative Services instead of Blueprint. From a users point of view these changes will yield a smaller, more efficient Karaf core. There will be a Blueprint feature present in Karaf so that you can easily install Blueprint based applications. You will always be capable of using Blueprint in Karaf. So the main difference from a user perspective is that youâd need to depend on the Blueprint service if you need it. + The 4.0.x line will ship with OSGi Rev5 support via Felix 4.4.1 and Equinox 3.9.1-v20140110-1610, and a completely refactored internal framework without Blueprint for internal usage. From a users point of view these changes will yield a smaller, more efficient Karaf core. There will be a Blueprint feature present in Karaf so that you can easily install Blueprint based applications. You will always be capable of using Blueprint in Karaf. So the main difference from a user perspective is that youâd need to depend on the Blueprint service if you need it. Apache Karaf 3.0.0
