[cxf] 01/02: Update for 3.2.14 release notes

[dk...@apache.org]

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

dkulp pushed a commit to branch 3.2.x-fixes
in repository https://gitbox.apache.org/repos/asf/cxf.git

commit fa459dfb5a0c4fd1a0d98e64487a64364af201ec
Author: Daniel Kulp <dk...@apache.org>
AuthorDate: Tue Jun 23 12:39:32 2020 -0400

    Update for 3.2.14 release notes
---
 distribution/src/main/release/release_notes.txt | 56 +++++++++++++++++--------
 1 file changed, 39 insertions(+), 17 deletions(-)

diff --git a/distribution/src/main/release/release_notes.txt b/distribution/src/main/release/release_notes.txt
index 54d084c..d32c62c 100644
--- a/distribution/src/main/release/release_notes.txt
+++ b/distribution/src/main/release/release_notes.txt
@@ -1,4 +1,4 @@
-Apache CXF 3.2.13 Release Notes
+Apache CXF 3.2.14 Release Notes
 
 1. Overview
 
@@ -17,7 +17,7 @@ New features include:
 * Preliminary support for running on Java 9  (no module support yet)
 * New http-undertow transport
 
-3.2.13 fixes over 15 JIRA issues reported by users and the community since 3.2.12.
+3.2.14 fixes over 11 JIRA issues reported by users and the community since 3.2.13.
 
 
 Important notes:
@@ -70,25 +70,47 @@ for caveats when upgrading.
 7. Specific issues, features, and improvements fixed in this version
 
 ** Bug
-    * [CXF-7959] - WebClient invocation builder header(name, value) method is not implemented according to interface
-    * [CXF-8200] - Use name() instead of toString() for enums when generating WADL
-    * [CXF-8201] - Path not appended when using UriBuilder.fromUri().path() with file scheme
-    * [CXF-8207] - SseEventSource loses lastEventId on the 2nd reconnect attempt
-    * [CXF-8208] - Requests with encoded special characters fail with IllegalArgument exception in SwaggerUiResourceLocator
-    * [CXF-8210] - Incompatibility with recent Brave versions causes NullPointerException and hides root cause
-    * [CXF-8215] - SSE breaks Pipeline Processing
-    * [CXF-8220] - The tag "http.status_code" is always 200 in server side tracing span, no matter what situation
-    * [CXF-8234] - Response Content-Type is missing 'charset' when Transformation feature is enabled
-    * [CXF-8235] - AsyncResponseImpl.initContinuation() throws NPE when Continuation is null
-    * [CXF-8241] - cxf-codegen-plugin not using the proxy port configured in settings.xml
-    * [CXF-8249] - SSE client refuses to accept valid stream
+    * [CXF-8242] - Stop blocking executor thread on microprofile rest asynchronous call
+    * [CXF-8259] - Blocked thread of JMS transport during jboss shutdown
+    * [CXF-8261] - Exceptions being thrown in a ClientResponseFilter are ignored
+    * [CXF-8282] - Set read timeout using netty client
+    * [CXF-8296] - Custom Boolean ParamConverter wrong behaviour
+    * [CXF-8298] - An invalid package name is generated
 
 ** Improvement
-    * [CXF-8193] - upgrade to jetty 9.4.27
-    * [CXF-8238] - Tracing spans need more tag to make it clearer
+    * [CXF-8286] - AbstractStaticFailoverStrategy.getEndpoints() never returns anything for JAX-RS clients (with RetryStrategy)
+    * [CXF-8306] - be able to configure http-undertow worker|threadpool name
 
 ** Task
-    * [CXF-8197] - Update to Spring Framework 4.3.26
+    * [CXF-8078] - Support RxJava 3.0
+    * [CXF-8271] - The async JAX-RS client never completes the response in case of an exception during the interceptor chain processing.
+    * [CXF-8300] - Swagger2Feature displays cached API when service is redeployed
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+g Framework 4.3.26