Daily Roundup

Google to Release 'Wave in a Box' and Maven 3.0-beta-3 Gets Guice and Aether

Two New Releases for Apache Traffic Server

The Apache Traffic Server team have announced two new releases: 2.1.2 and 2.0.1.

The 2.1.2 release addresses the CVE-2010-2952 DNS security improvements. It also introduces the basic features to compile with Intel CC and adds configure option to enable detailed logging. All examples have been updated to use non-deprecated APIs.

Version 2.0.1 is a maintenance release for the 2.0 branch. It backports the part of TS-322 that deals with indexing arrays with char, and backports TS-336 to 2.0.x.

Apache Traffic Server is a HTTP/1.1 compliant caching proxy server, which was donated to the Apache Foundation by Yahoo!

Preview Beta of AWS Identity and Access Management

Amazon have launched a preview beta of AWS Identity and Access Management (IAM)for managing the permissions of each user within an AWS Account. IAM aims to eliminate the need for sharing passwords or access keys, and facilitates the enabling and disabling of a user's access, as desired.

With the beta, you can add users to an AWS Account, set groups and permissions for these users, and enable the users to call AWS Service APIs. Support for users to login to the AWS Management Console is planned for future releases, alongside extending the AWS Management Console to support IAM.

Third Beta of Maven 3.0 With Aether and Guice

Maven 3.0-beta-3 is now available.

This third beta release integrates Aether and moves from Plexus to Guice as IoC container. There is also a list of bug fixes, in areas such as regression in parsing command-line arguments, stack trace and plugin-level dependency scope.

Maven 3 ultimately aims to ensure backward compatibility with Maven 2, allow safe embedding, and lay the foundations for implementing many oft-demanded new features.

Google To Release “Wave in a Box.”

Google have shed some light on the future of Google Wave's open source code and Wave federation protocol.

Google pledge to expand on the Wave code currently open sourced, and build on the existing example Wave server and web client, ultimately delivering “Wave in a Box.” The project will include an application bundle of a server and web client that uses the same structured conversations as the Google Wave system, a wave panel in the web client and gadget, robot and data API support. Developers will be able to run Wave servers and host Waves on their own hardware, although the project will not have the full functionality of Google Wave.

“While Wave in a Box will be a functional application, the future of Wave will be defined by your contributions. We hope this project will help the Wave developer community continue to grow and evolve,” reads the announcement.

Jessica Thornsby

What do you think?

Comments

Latest opinions