아파치 소프트웨어 재단은 아파치 오픈 소스 소프트웨어 프로젝트 커뮤니티 지원을 제공합니다.
아파치 프로젝트는 협업과 개발 프로세스를 기반으로 하는 상호간의 공감대와 개방되어 있는 실용적인 소프트웨어 라이센스, 그 분야에서 선두를 달릴 수 있는 고품질 소프트웨어 개발을 추구하고 있습니다.
우리는 심플한 서버 공유 프로젝트의 모임이라고도 하지만 오히려 개발자와 사용자간의 커뮤니티라고 생각합니다.
The Apache Ivy project is pleased to announce its 2.2.0 release.
Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies, characterized by flexibility, configurability, and tight integration with Apache Ant.
Key features of the 2.2.0 release are
* enhanced Maven2 compatibility, with several bug fixes and more pom features covered
* new parent mechanism for Ivy files
* improved pom generation from an ivy.xml file
* automated PGP signature generation when uploading artifacts
* numerous bug fixes as documented in Jira and in the release notes
We encourage all users of Ivy to update to this new version.
Apache Buildr is a build system for Java-based applications, including support for Scala, Groovy and a growing number of JVM languages and tools.
http://buildr.apache.org/
This release comes less than 4 weeks after 1.4.2 to address a critical issue where created .jar/.zip packages may be corrupted (BUILDR-517). All users are encouraged to upgrade.
Changes in 1.4.3:
* Added: BUILDR-514 New ‘run’ local task. http://buildr.apache.org/more_stuff.html#run
* Added: BUILDR-518 Load _buildr.rb or .buildr.rb from same directory as Buildfile if they exist (Peter Donald)
* Added: BUILDR-519 Load repositories.release_to from build settings (Peter Donald)
* Fixed: BUILDR-513 —trace fails with NoMethodError : undefined method `include?’ for nil:NilClass
* Fixed: BUILDR-515 -update-snapshot doesn’t work as expected
* Fixed: BUILDR-517 package(:jar).include(directory, :as=>"foo") produces a corrupted jar
* Fixed: BUILDR-524 Optimized and more robust reading of jar MANIFEST.MF (Hugues Malphettes)
* Fixed: BUILDR-527 package(:war) fails if libs passed are files (instead of artifacts)
* Fixed: BUILDR-531 Improve error message when build requires gem that can’t be found in local/remote gem repositories (Peter Donald)
* Fixed: BUILDR-532 package_as_source does not package resources (Tammo van Lessen)
* Fixed: BUILDR-535 Failing “checks” produce no meaningful errors on JRuby
* Fixed: JavaRebel was previously not correctly detected.
And 10+ other minor bug fixes. See CHANGELOG for details.
The Apache CXF team is proud to announce the availability of the 2.3.0 release.
Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs like JAX-WS and JAX-RS.
These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI.
CXF includes a broad feature set, but it is primarily focused on the following areas:
* Web Services Standards Support: CXF supports a variety of web service standards including SOAP, the WSI Basic Profile, WSDL, WS-Addressing, WS-Policy, WS-ReliableMessaging, WS-Security, WS-SecurityPolicy, WS-Trust, and WS-SecureConversation.
* REST based service creation based on JAX-RS 1.1 standard API's.
* Frontends: CXF supports a variety of "frontend" programming models. CXF provides a JAX-WS 2.2 Compliant frontend. It also includes a "simple frontend" which allows creation of clients and endpoints without annotations.
CXF supports both contract first development with WSDL and code first development starting from Java.
* Ease of use: CXF is designed to be intuitive and easy to use. There are simple APIs to quickly build code-first services, Maven plug-ins to make tooling integration easy, JAX-WS API support, Spring XML support to make configuration a snap, and much more.
What's new in CXF 2.3.0:
* JAX-WS 2.2 Compliant (passes TCK)
* JAX-RS 1.1 Compliant (passes TCK)
* New annotations for Java first use cases to reduce the need for external configuration and provide more control over the runtime and generated WSDL
* @WSDLDocumentation annotation to add documentation nodes to generated wsdl
* @SchemaValidation annotation to turn on schema validation
* @DataBinding to set the databinding used (if other than JAXB)
* @GZIP to turn on GZIP compression
* @FastInfoset to turn on FastInfoset support
* @Logging to turn on and control various Logging functionality
* @EndpointProperty to configure endpoint properties
* @Policy to associate WS-Policy documents with the service
* SOAP/JMS spec implementation. While CXF has supported SOAP over JMS since 2.0, there wasn’t a standard specification to describe how it should be done so different vendors did things differently and interoperability was impossible. The new SOAP/JMS specification support implements the new SOAP/JMS spec to achieve a higher degree of interoperability.
* SDO databinding
* Schema Validation support for Aegis Databinding if Woodstox 4 is used for the Stax parser
* Many other small tweaks and enhancements, too many to enumerate.
The Apache Software Foundation
