Author: jgoodyear
Date: Fri Oct 10 18:09:57 2014
New Revision: 1630949
URL: http://svn.apache.org/r1630949
Log:
[KARAF-3272] Release Apache Karaf 4.0.0.M1. Update online release notes.
Modified:
karaf/site/trunk/src/main/webapp/index/community/download/karaf-4.0.0.M1-release.page
Modified:
karaf/site/trunk/src/main/webapp/index/community/download/karaf-4.0.0.M1-release.page
URL:
http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-4.0.0.M1-release.page?rev=1630949&r1=1630948&r2=1630949&view=diff
==============================================================================
---
karaf/site/trunk/src/main/webapp/index/community/download/karaf-4.0.0.M1-release.page
(original)
+++
karaf/site/trunk/src/main/webapp/index/community/download/karaf-4.0.0.M1-release.page
Fri Oct 10 18:09:57 2014
@@ -20,6 +20,4 @@ h2. Release Notes - Karaf - Version 4.0.
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.
