Author: buildbot
Date: Mon Mar 26 19:48:18 2012
New Revision: 810107
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/26-migration-guide.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/26-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/26-migration-guide.html (original)
+++ websites/production/cxf/content/docs/26-migration-guide.html Mon Mar 26
19:48:18 2012
@@ -140,7 +140,7 @@ Apache CXF -- 2.6 Migration Guide
<h3><a shape="rect" name="2.6MigrationGuide-DependencyChanges"></a>Dependency
Changes</h3>
-<ul><li>The org.apache.cxf.tools.* classes that were in cxf-api have been
moved into cxf-tools-common or cxf-tools-validator.</li><li>The
org.apache.cxf.ws.policy classes that were in cxf-api have been moved into
cxf-rt-ws-policy.</li><li>cxf-common-utilities is no longer available. All the
classes in there were moved into cxf-api to represent a complete
"api".</li><li>Various classes in cxf-rt-core and cxf-rt-ws-addr have been
moved up to cxf-api to resolve split-package issues. Dependencies on
cxf-rt-core would have transitively brought in cxf-api anyway, so there should
be little impact.</li><li>Spring is now an optional component of the http-jetty
transports module and other modules. Applications that may have pulled in
Spring transitively via CXF will be required to declare required spring
dependencies in their own poms directly.</li></ul>
+<ul><li>The org.apache.cxf.tools.* classes that were in cxf-api have been
moved into cxf-tools-common or cxf-tools-validator.</li><li>The
org.apache.cxf.ws.policy classes that were in cxf-api have been moved into
cxf-rt-ws-policy.</li><li>cxf-common-utilities is no longer available. All the
classes in there were moved into cxf-api to represent a complete
"api".</li><li>Various classes in cxf-rt-core and cxf-rt-ws-addr have been
moved up to cxf-api to resolve split-package issues. Dependencies on
cxf-rt-core would have transitively brought in cxf-api anyway, so there should
be little impact.</li><li>Spring is now an optional component of the http-jetty
transports module and other modules. Applications that may have pulled in
Spring transitively via CXF will be required to declare required spring
dependencies in their own poms directly.</li><li>Most of the optional JAX-RS
Providers have been moved out of the cxf-rt-frontend-jaxrs module and into a
cxf-rt-rs-extension-provi
ders module with the various dependencies marked optional/provided.
Applications that use these optional providers will need to add the required
dependencies. Also, the package names of many of those providers has changed to
resolve split-package issues. Example:
org.apache.cxf.jaxrs.provider.JSONProvider ->
org.apache.cxf.jaxrs.provider.json.JSONProvider</li></ul>
