+1

As mentioned to Dan, I actually noticed that when building the 2.3.1 tag using 'mvn -Pjaxws22,fastinstall' (java 1.6.0_21), a 2.3.1-SNAPSHOT artifact is referenced, unless I locally apply a change like the following one:

Index: systests/container-integration/grizzly/pom.xml
===================================================================
--- systests/container-integration/grizzly/pom.xml    (revision 1041399)
+++ systests/container-integration/grizzly/pom.xml    (working copy)
@@ -4,13 +4,13 @@
<parent>
<groupId>org.apache.cxf.systests</groupId>
<artifactId>cxf-systests-container-integration</artifactId>
- <version>2.3.1-SNAPSHOT</version>
+ <version>2.3.1</version>
<relativePath>../pom.xml</relativePath>
</parent>
<groupId>org.apache.cxf.systests</groupId>
<artifactId>cxf-systests-ci-grizzly</artifactId>
<name>Apache CXF Container Integration Test Grizzly</name>
- <version>2.3.1-SNAPSHOT</version>
+ <version>2.3.1</version>

<repositories>
<repository>

This is anyway *not* a real issue to me, and I'm definitely in favour of this 2.3.1 release and looking forward for it given all the improvements/fixes it includes.

Cheers
Alessio


On 12/02/2010 03:54 PM, Daniel Kulp wrote:

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.3.0 release.   Over 55 JIRA issues
are resolved for 2.3.1.

Note:  this vote also includes a release of the cxf-buildutils to fix some 
compatibility issues with the build and the latest Eclipse plugins.


List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315385&styleName=Html&projectId=12310511&Create=Create

The Maven staging area is at:
https://repository.apache.org/content/repositories/orgapachecxf-036/

The distributions are in:
https://repository.apache.org/content/repositories/orgapachecxf-036/org/apache/cxf/apache-cxf/2.3.1/

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.3.1
http://svn.apache.org/repos/asf/cxf/build-utils/tags/cxf-build-utils-2.3.1/

The vote will be open for 72 hours.

Here is my +1.




--
Alessio Soldano
Web Service Lead, JBoss

Reply via email to