The Apache Commons project is pleased to announce the release of Commons BeanUtils 1.8.0. Commons BeanUtils provides easy-to-use wrappers around the Reflection and Introspection APIs provided by the Java language. BeanUtils 1.8.0 is binary compatible with version 1.7.0 and contains a number of bug fixes and enhancements. Full details of changes are available in the Release Notes: http://commons.apache.org/beanutils/v1.8.0/RELEASE-NOTES.txt Commons BeanUtils is available in either binary or source form from the following download page: http://commons.apache.org/beanutils/download_beanutils.cgi For more information on Commons BeanUtils, visit the project home page: http://commons.apache.org/beanutils/ - Niall Pemberton - on behalf of the Apache Commons community

View original post | Add to del.icio.us | Share

The Apache Harmony team are pleased to announce the immediate availability of Apache Harmony 5.0M7. Apache Harmony is the Java platform project of the Apache Software Foundation. Apache Harmony 5.0M7 is the latest stable build with numerous enhancements and bug fixes including: * new performance improvements, especially in object serialization and pack200 decoding, * a new 'javap' the class file disassembler tool, and alpha version of 'policytool' the security policy management tool. * bug fixes and functional enhancements throughout the class libraries, especially in the Swing widget toolkit, * ...and many more We would particularly like to thank our Google Summer of Code students András Belicza (policytool) and Tharindu Mathew (Swing enhancements), and welcome them to the project! Source code and binary builds are available from the project download site: http://harmony.apache.org/download.cgi Apache Harmony welcomes your help. For more information on how to report problems, successes, and to get involved in Apache Harmony visit the project website at http://harmony.apache.org The Apache Harmony Team

View original post | Add to del.icio.us | Share

The Apache MyFaces Orchestra team is pleased to announce the release of Apache MyFaces Orchestra Core 1.2. Get a full overview at Orchestra's homepage [1]. The distribution is available at * http://myfaces.apache.org/orchestra/download.html Apache MyFaces Orchestra is available in the central Maven repository under Group ID "org.apache.myfaces.orchestra". Have fun! Regards, Simon [1] http://myfaces.apache.org/orchestra

View original post | Add to del.icio.us | Share

The development version of Ruby on Rails has cool new internationalization features. Although the framework itself doesn’t provide a lot of I18N functionality, it does provide the necessary hooks for plugins to implement I18N however they see fit. Simon Tokumine has written an I18N demo application to show you what Rails is capable of, when used in combination with the localized_dates plugin.

We’ve deployed the demo application at http://i18n-demo.phusion.nl/. Check it out.

[Ruby on Rails ]
View original post | Add to del.icio.us | Share

The Apache JAMES Project http://james.apache.org is pround to announce that Apache JSieve 0.2 is now available. Apache JSieve is a Java implementation of RFC 3028 Sieve: A Mail Filtering Language. A prime (though not the only) use case for Sieve is rule-based filtering into mailboxes after delivery to a server. JAMES server uses JSieve for this purpose. For more information see http://james.apache.org/jsieve. This is the first release of JSieve though the code base is reasonably mature. It can be downloaded from ������http://james.apache.org/download.cgi. Please remember to check the signature or sum. Robert Burrell Donkin

View original post | Add to del.icio.us | Share

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Axis2 team is proud to announce the release of Apache Axis2 version 1.4.1. Apache Axis2 1.4.1 fixes a security vulnerability present in Apache Axis2 1.4 policy processing. Downloads are available at: http://ws.apache.org/axis2/download.cgi The Maven2 main repository has the latest jars as well. Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy addition of plug-in "modules" that extend its functionality for features such as security and reliability. Known Issues and Limitations in 1.4.1 Release: - - Please see JIRA for the current status of bugs We welcome any and all feedback at: - - axis-user@ws.apache.org (please include "[axis2]" in the subject, please subscribe first) - - axis-dev@ws.apache.org (please include "[axis2]" in the subject, please subscribe first) - - http://issues.apache.org/jira/browse/AXIS2 Thank you for your interest in Apache Axis2! The Axis2 Development Team http://ws.apache.org/axis2/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIsxTbmA4ts7hLdV8RAl/uAKCQh9Q8J2lTJpWs3UMGjQ1QlXffcwCeLBVn Tj7lveVJ+g8pHFqlLo1WhAQ= =hnw4 -----END PGP SIGNATURE-----

View original post | Add to del.icio.us | Share

Problem description and motivation

There is a lot of software (both Rails related and unrelated) which rely on servers or daemons. To name a few, in no particular order:

• Ultrasphinx, a Rails library for full-text searching. It makes use the Sphinx search software for indexing and searching. Indexing is done by running a command, while searching is done by querying the Sphinx search server.
• acts_as_ferret, another Rails library for full-text searching. It uses the Ferret search software. On production environments, it relies on the Ferret DRB server for both searching and indexing.
• BackgrounDRb, a Ruby job server and scheduler. Scheduling is done by contacting the BackgrounDRb daemon.
• mongrel_cluster, which starts and stops multiple Mongrel daemons.

Relying on daemons is quite common, but not without problems. Let’s go over some of them.

Starting daemons is a hassle

If you’ve used similar software, then you might agree that managing these daemons is a hassle. If you’re using BackgrounDRb, then the daemon must be running. Starting the daemon is not hard, but it is annoying. It’s also possible that the system administrator forgets to start the daemon. While configuring the system to automatically start a daemon at startup is not hard, it is an extra thing to do, and thus a hassle. We thought, why can’t such daemons be automatically started? Indeed, this won’t be possible if the daemon is to be run on a remote machine. But in by far the majority of use cases, the daemon runs on the same host as the Rails application. If a Rails application - or indeed, any application - is configured to contact a daemon on the local host, then why not start the daemon automatically on demand?

Daemon starting code may not be robust or efficient

We’ve also observed that people write daemon controlling code over and over again. Consider for example UltraSphinx, which provides a rake sphinx:daemon:start Rake task to start the daemon. The time that a daemon needs to initialize is variable, and depends on things such as the current system load. The Sphinx daemon usually needs less than a second before we can connect to it. However, the way different software handles starting of a daemon varies. We’ve observed that waiting a fixed amount of time is by far the most common way. For example, UltraSphinx’s daemon starting code looks like this:

system "searchd --config '#{Ultrasphinx::CONF_PATH}'" sleep(4) # give daemon a chance to write the pid file if ultrasphinx_daemon_running? say "started successfully" else say "failed to start" end

This is in no way a slam against UltraSphinx. However, if the daemon starts in 200 miliseconds, then the user who issued the start command will be waiting for 3.8 seconds for no good reason. This is not good for usability or for the user’s patience.

Startup error handling

Different software handles daemon startup errors in different ways. Some might not even handle errors at all. For example, consider mongrel_cluster. If there’s a typo in one of your application source files, then mongrel_cluster will not report the error. Instead, you have to check its log files to see what happened. This is not good for usability: many people will be wondering why they can’t connect to their Mongrel ports after issuing a mongrel_rails cluster::start — until they realize that they should read the log file. But the thing is, not everybody realizes this. And typing in an extra command to read the log file to check whether Mongrel started correctly, is just a big hassle. Why can’t the daemon startup code report such errors immediately?

Stale or corrupt Pid files

Suppose that you’re running a Mongrel cluster, and your server suddenly powers off because of a power outage. When the server is online again, it fails to start your Mongrel cluster because the PID file that it had written still exists, and wasn’t cleaned up properly (it’s supposed to be cleaned up when Mongrel exits). mongrel_cluster provides the –clean option to check whether the PID file is stale, and will automatically clean it up if it is. But not all daemon controlling software supports this. Why can’t all software check for stale PID files automatically?

Implementation problems

From the problem descriptions, it would become apparent that our wishlist is as follows. Why is this wishlist often not implemented? Let’s go over them.

A daemon should be automatically started on demand, instead of requiring the user to manually start it.

The most obvious problems are related to concurrency. Suppose that your web application has a search box, and you want to start the search daemon if it isn’t already started, then connect to. Two problems will arise:

• Suppose that Rails process A is still starting the daemon. At the same time, another visitor tries to search something, and Rails process B notices that the daemon is not running. If B tries to start the daemon while it’s already being started by A, then things can go wrong. A robust daemon starter must ensure that only one process at the same time may start the daemon.
• It’s not a good idea to wait a fixed amount of time for the daemon to start, because you don’t know in advance how long it will take for it to start. For example, if you wait 2 seconds, then try to connect to the daemon, and the daemon isn’t done initializing yet, then it will seem as if the daemon failed to start.

These are the most probable reasons why people don’t try to write auto-starting code, and instead require the user to start the daemon manually.

These problems, as well as several less obvious problems, are closely related to the next few points.

The daemon starter must wait until the daemon is done initializing, no longer and no shorter

Because only after the daemon is fully initialized, is it safe to connect to it. And because the user should not have to wait longer than he really has to.

During startup, the daemon will have to be continuously checked whether it’s done initializing or whether an error occured. Writing this code can be quite a hassle, which is why most people don’t do it.

The daemon starter must report any startup errors

If the daemon starting command — e.g. “sphinx -c config_file.conf”, “apachectl start” or “mongrel_rails cluster::start” — reports startup errors, then all is fine as long as the user is starting the command from a terminal. A problem occurs when the error occurs after the daemon has already gone into the background. Such errors are only reported to the log file. The daemon starter should also check the log file for any startup errors.

Furthermore, it should be able to raise startup errors as exceptions. This allows the the application to decide what to do with the error. For less experienced system administrators, the error might be displayed in the browser, allowing the administrators to become aware of the problem without forcing them to manually check the log files. Or the error might be emailed to a system administrator’s email address.

The daemon starter must be able to correct stale or corrupted PID files If the PID file is stale, or for some reason has been corrupted, then the daemon starter must be able to cope with that. It should check whether the PID file contains a valid PID, and whether the PID exists. Introducing daemon_controller

daemon_controller is a library for managing daemons in a robust manner. It is not a tool for managing daemons. Rather, it is a library which lets you write applications that manage daemons in a robust manner. For example, mongrel_cluster or UltraSphinx may be adapted to utilize this library, for more robust daemon management.

daemon_controller implements all items in the aforementioned wishlist. It provides the following functionalities:

Starting a daemon

This ensures that no two processes can start the same daemon at the same time. It will also reports any startup errors, even errors that occur after the daemon has already gone into the background but before it has fully initialized yet. It also allows you to set a timeout, and will try to abort the daemon if it takes too long to initialize.

The start function won’t return until the daemon has been fully initialized, and is responding to connections. So if the start function has returned, then the daemon is guaranteed to be usable.

Stopping a daemon

It will stop the daemon, but only if it’s already running. Any errors are reported. If the daemon isn’t already running, then it will silently succeed. Just like starting a daemon, you can set a timeout for stopping the daemon.

Like the start function, the stop function won’t return until the daemon is no longer running. This makes it save to immediately start the same daemon again after having stopped it, without worrying that the previous daemon instance hasn’t exited yet and might conflict with the newly started daemon instance.

Connecting to a daemon, starting it if it isn’t running Every daemon has to be connected to using a different way. As a developer, you tell daemon_controller how to connect to the daemon. It will then attempt to do that, and if that fails, it will check whether the daemon is running. If it isn’t running, then it will automatically start the daemon, and attempt to connect to the daemon again. Failures are reported. Checking whether a daemon is running This information is retrieved from the PID file. It also checks whether the PID file is stale. All failures are reported via exceptions So that you can exactly determine how you want to handle errors. Lots and lots of error checking So that there are very few ways in which the system can screw up.

daemon_controller’s goal is to make daemon management less of a hassle, and as automatic and straightforward as possible.

Tutorial #1: controlling Apache

Suppose that you’re a Phusion Passenger developer, and you need to write tests for the Apache module. In particular, you want to test whether the different Phusion Passenger configuration directives are working as expected. Obviously, to test the Apache module, the Apache web server must be running. For every test, you will want the unit test suite to:

1. Write an Apache configuration file, with the relevant configuration directive set to a specific value.
2. Start Apache.
3. Send an HTTP request to Apache and check whether the HTTP response matches your expectations.
4. Stop Apache.

That can be done with the following code:

require 'daemon_controller' File.open("apache.conf", "w") do |f| f.write("PidFile apache.pid\n") f.write("LogFile apache.log\n") f.write("Listen 1234\n") f.write(... other relevant configuration options ...) end controller = DaemonController.new( :identifier => 'Apache web server', :start_command => 'apachectl -f apache.conf -k start', :ping_command => lambda { TCPSocket.new('localhost', 1234) }, :pid_file => 'apache.pid', :log_file => 'apache.log', :timeout => 25 ) controller.start .... apache is now started .... .... some test code here .... controller.stop

The File.open line is obvious: it writes the relevant Apache configuration file.

The next line is for creating a new DaemonController object. We pass a human-readable identifier for this daemon (”Apache web server”) to the constructor. This is used for generating friendlier error messages.
We also tell it how Apache is supposed to be started (:start_command), how to check whether it can be connected to (:ping_command), and where its PID file and log file is. If Apache failed with an error during startup, then it will be reported. If Apache failed with an error after it has gone into the background, then that will be reported too: the given log file is monitored for new error messages.
Finally, a timeout of 25 seconds is given. If Apache doesn’t start within 25 seconds, then an exception will be raised.

The ping command is just a Proc which returns true or false. If the Proc raises Errno::ECONNREFUSED, then that’s also interpreted by DaemonController as meaning that the daemon isn’t responding yet.

After controller.start has returned, we can continue with the test case. At this point, we know that Apache is done with initializing.
When we’re done with Apache, we stop it with controller.stop. This does not return until Apache has fully stopped.

The cautious reader might notice that the socket returned by the ping command is never closed. That’s true, because DaemonController will close it automatically for us, if it notices that the ping command proc’s return value responds to #close.

From this example, it becomes apparent that for daemon_controller to work, you must know how to start the daemon, how to contact the daemon, and you must know where it will put its PID file and log file.

Tutorial #2: Sphinx indexing and search server management

We at Phusion are currently developing a web application with full-text search capabilities, and we’re using Sphinx for this purpose. We want to make the lives of our developers and our system administrators as easy as possible, so that there’s little room for human screw-up, and so we’ve developed this library. Our Sphinx search daemon is completely managed through this library and is automatically started on demand.

Our Sphinx config file is generated from an ERB template. This ERB template writes different values in the config file, depending on whether we’re in development, test or production mode. We will want to regenerate this config file every time, just before we start the search daemon.
But there’s more. The search daemon will fail if there is no search index. If a new developer has just checked out the application’s source code, then there is no search index yet. We don’t want him to go through the pain of having to generate the index manually. (That said, it isn’t that much of a pain, but it’s just yet-another-thing to do, which can and should be automated.) So before starting the daemon, we will also want to check whether the index exists. If not, then we’ll generate it, and then start the daemon. Of course, no two Rails processes may generate the config file or the index at the same time.

When querying the search server, we will want to automatically start it if it isn’t running.

This can be achieved with the following code:

require 'daemon_controller' class SearchServer SEARCH_SERVER_PORT = 1234 def initialize @controller = DaemonController.new( :identifier => 'Sphinx search server', :start_command => "searchd -c config/sphinx.conf", :before_start => method(:before_start), :ping_command => lambda { TCPSocket.new('localhost', SEARCH_SERVER_PORT) }, :pid_file => 'tmp/pids/sphinx.pid', :log_file => 'log/sphinx.log', end def query(search_terms) socket = @controller.connect do TCPSocket.new('localhost', SEARCH_SERVER_PORT) end send_query(socket, search_terms) return retrieve_results(socket) end private def before_start generate_configuration_file if !index_exists? generate_index end end ... end

Notice the :before_start option. We pass a block of code which is to be run, just before the daemon is started. This block, along with starting the daemon, is completely serialized. That is, if you’re inside the block, then it’s guaranteed that no other process is running this block at the same time as well.

The query method is the method for querying the search server with search terms. It returns a list of result. It uses DaemonController#connect: one passes a block of that method, which contains code for connecting to the daemon. If the block returns nil, or if it raises Errno::ECONNREFUSED, then DaemonController#connect will automatically take care of auto-starting the Sphinx daemon for us.

A little bit of history

The issue of managing daemons has been a thorn in our eyes for quite some time now. Until now, we’ve solved this problem by equipping any daemons that we write with the ability to gracefully handle being concurrently started, the ability to initialize as much as possible before forking into the background, etc. However, equipping all this robustness into our code over and over is a lot of work. We’ve considered documenting a standard behavior for daemons so that they can properly support auto-starting and such.

However, we’ve recently realized that that’s probably a futile effort. Convincing everybody to write a lot of code for a bit more robustness is probably not realistic. So we took the pragmatic approach and developed a library which adds more robustness on top of daemons’ existing behavior. And thus, daemon_controller was born. It is a little bit less efficient compared to when the daemon is designed from the beginning with such abilities in mind, but it’s compatible with virtually all daemons, and is easy to use.

Availability

The source code is available on Github: http://github.com/FooBarWidget/daemon_controller/tree/master
Detailed API documentation is available in the form of inline comments in lib/daemon_controller.rb.

[Software ]
View original post | Add to del.icio.us | Share

Mime4J is a flexible MIME parsing library written in Java. SAX, DOM and pull parsing styles are supported. The 0.4 release brings a number of significant improvements in terms of supported capabilities, flexibility and performance: * Revised and improved public API with support for pull parsing * Support for parsing of 'headless' messages transmitted using non SMTP transports such as HTTP * Reduced external dependencies. Mime4j is no longer directly dependent on log4j and commons-io * Improved parsing performance (up to 10x for large messages) * More comprehensive header parsing including support for RFC1864, RFC2045, RFC2183, RFC2557 and RFC3066 * Revised packaging and exception hierarchy. MimeException now extends IOException. Detailed change log can be found here: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310521&styleName=Html&version=12312483 Notes ----- * 0.4 contains numerous API improvements and is not binary compatible with 0.3 * Mime4j API is still considered unstable and is likely to change in future releases * DOM support has known limitations and some roundtrip issues remain to be resolved * Some low level functions are available only in the pull parser (recommended for advanced users)

View original post | Add to del.icio.us | Share

I’m sure you know what “Crawl-Delay” is, but you may or may not know that, not all search engine crawlers support this nice stuff.

What to do for those don’t obey the instrustion? They’ll eat all your Mbits/month or slow your webserver down. OK, ban it with url.access-deny. This is the only option u can choose before. But you don’t want to remove your pages from the stupid search engine index, do you?

Here comes another option for you: with this patch, u can delay handling of a specified request for some seconds. Example configuration:

$HTTP["user-agent"] =~ "stupid-crawler" { connection.delay-seconds = 2 }

OK, here’s the link to the lighttpd-2296-request-handle-delay.patch which applies to branches/lighttpd-1.4.x@2296

Be aware that this patch is to be reviewed before commited to repo.

[lighttpd ]
View original post | Add to del.icio.us | Share

It’s been some time since the last 1.4 release and especially since the last 1.5 prerelease. There have been a lot of fixes in both branches so be sure to check them out, no matter if you are using 1.4 or 1.5.

You can get the prereleases from this url: http://opensu.se/~darix/lighttpd/

The 1.4.20 changes can be read here:
http://trac.lighttpd.net/trac/browser/branches/lighttpd-1.4.x/NEWS
While 1.5 changes can be fetched from here:
http://trac.lighttpd.net/trac/browser/trunk/NEWS

We ask you to test these snapshots as extensive as possible and report any broken things back to us.
If everything goes well and no showstoppers are encountered, there will be an official 1.4.20 release soon.

As for 1.5: should this prerelease be stable and bugfree enough, it will be the last prerelease and there will be a 1.5.0 release. It will not retire the 1.4 branch though. There are still some things missing in 1.5 like internal spawning of fcgi backends that prevent it form being the next main branch.

You can thank stbuehler for all his hard work he has put into both trees as he is responsible for nearly all of the work recently.

If you want to get the latest source for any branch, you can get it from our svn repository.
Documentation to do so can be obtained from this page:
http://trac.lighttpd.net/trac/wiki/Devel/Subversion
Bug reports or feature requests can be filed in our trac ticket system:
http://trac.lighttpd.net/trac/newticket
Please make sure to check if there isn’t a ticket already here:
http://trac.lighttpd.net/trac/report

Thank you for using lighty.

[lighttpd 1.4.20 1.5 prerelease r2294 ]
View original post | Add to del.icio.us | Share

The Apache Directory Team is pleased to announce the release of Apache Directory Studio 1.2.0, a major update of its Eclipse based LDAP Browser and Directory client. You can download Apache Directory Studio 1.2.0 as a standalone RCP application for Mac OS X, Linux and Windows here: http://directory.apache.org/studio/downloads.html You can also install it directly in Eclipse using this update site: http://directory.apache.org/studio/update/1.x/ Here are a few highlights of this new version: * The new Apache DS feature makes its introduction in Apache Directory Studio. This new feature allows you to run the latest version of Apache DS (1.5.3) from within Apache Directory Studio or Eclipse and makes it super easy (and fast) to create and run an LDAP Server. * The Apache DS Configuration plugin now supports the 4 latest versions of Apache DS. It's now capable to read/write the server.xml file of an Apache DS 1.5.0, 1.5.1, 1.5.2 and 1.5.3. * The Search Logs view has been added to the LDAP Browser. * We've also added the support to use the proxy features of Eclipse inside Studio as well as improved the platform (useful actions have been added to the platform, the Mac OS X application now respects the standards of Apple for the "About" and "Preferences" actions, etc.). * We've also fixed some bugs dealing with schema files and schema parsing in the Schema Editor and LDAP Browser plugins. Developed as a sub-project of the Directory Top Level Project, Apache Directory Studio is an Eclipse RCP application that takes full advantage of the benefits inherent in the Eclipse platform. Composed of several Eclipse (OSGi) plugins, Apache Directory Studio can be easily upgraded with additional plugins. Apache Directory Studio plugins can even run within a full installation of Eclipse itself. Apache Directory Studio contains 6 major features: * an LDAP Browser feature * an LDIF Editor feature * an ACI Editor feature for Apache Directory Server * a Schema Editor feature * an Apache DS feature * an Apache DS Configuration feature For more information about Apache Directory Studio, see our website: http://directory.apache.org/studio Below are the JIRA issues that were resolved since the release of Apache Directory Studio 1.2.0: Bug * [DIRSTUDIO-89] - Entry painted even though not created in server * [DIRSTUDIO-121] - Some property pages make the dialog very tall * [DIRSTUDIO-157] - Studio looses STRG-V over some time of use * [DIRSTUDIO-209] - Cannot expand attribute list * [DIRSTUDIO-266] - OpenLDAP schema files parser fails when DESC contains an empty string '' * [DIRSTUDIO-273] - Unable to get Base DNs on OID (Oracle Internet Directory) * [DIRSTUDIO-298] - NullPointerException raised when drag'n'dropping a connection to a folder (on Mac OS X only) * [DIRSTUDIO-315] - Choosing new value, in entry editor shows new entry when server error occures * [DIRSTUDIO-318] - Rename of multi-values RDN does not work when changing the second RDN * [DIRSTUDIO-319] - LDAP Browser creating new entry becomes empty and unusable in Windows Vista after certain actions * [DIRSTUDIO-323] - Studio fails to read ApacheDS server.xml * [DIRSTUDIO-325] - Keybinding conflicts occurred. They may interfere with normal accelerator operation. * [DIRSTUDIO-326] - Non-Operational attributes are marked as operational when bind to Siemens DirX 7.0 * [DIRSTUDIO-330] - CoreException raised in editor when opening a *.txt file * [DIRSTUDIO-336] - Errors when parsing schema of some LDAP servers * [DIRSTUDIO-341] - Paste error * [DIRSTUDIO-342] - Relax the parser for the *.schema files * [DIRSTUDIO-343] - Referrals not handled. * [DIRSTUDIO-347] - Keybinding conflict for CTRL+Q * [DIRSTUDIO-349] - Unable to enter large values for uid * [DIRSTUDIO-350] - DS is not properly displaying case of group DN * [DIRSTUDIO-360] - cannot read attribute from items with a / in the dn * [DIRSTUDIO-364] - Installing in Eclipse fails * [DIRSTUDIO-365] - Can't delete entry with studio 1.1.0. works with 1.0.1 Improvement * [DIRSTUDIO-46] - Add connections import/export * [DIRSTUDIO-126] - Triple click to edit attribute * [DIRSTUDIO-295] - Add a console for errors * [DIRSTUDIO-329] - Replace internal URL class by shared-ldap LdapURL class * [DIRSTUDIO-337] - Add Save and Print actions in the toolbar of the RCP application * [DIRSTUDIO-361] - Auto-activate 'show operational attributes' when adding an operational attribute New Feature * [DIRSTUDIO-321] - Need to be able to set SOCKS proxy in the RCP version * [DIRSTUDIO-328] - Search Logs View * [DIRSTUDIO-357] - Add plugin to run Apache DS from within Apache Directory Studio Task * [DIRSTUDIO-128] - Replace internal schema parser with the schema parser in shared-ldap. * [DIRSTUDIO-317] - Update legal files after moving to Apache Directory Shared LDAP version 0.9.9 * [DIRSTUDIO-332] - Add support for 1.5.3, 1.5.2 and 1.5.0 server.xml configuration files * [DIRSTUDIO-338] - Update Eclipse dependencies to the latest Eclipse version (3.3.2) * [DIRSTUDIO-339] - Add the 'org.eclipse.ui.carbon' Eclipse plugin to the Mac OS X distribution The Apache Directory Team

View original post | Add to del.icio.us | Share

Hello, Apache CouchDB 0.8.1-incubating has been released. This is the second release under the patronage of the ASF Incubator. This release is available for immediate download: http://incubator.apache.org/couchdb/downloads.html Apache CouchDB is a distributed, fault-tolerant and schema-free document-oriented database accessible via a RESTful HTTP/JSON API. Among other features, it provides robust, incremental replication with bi-directional conflict detection and resolution, and is queryable and indexable using a table-oriented view engine with JavaScript acting as the default view definition language. CouchDB is written in Erlang, but can be easily accessed from any environment that provides means to make HTTP requests. There are a multitude of third-party client libraries that make this even easier for a variety of programming languages and environments. Version 0.8.1-incubating ------------------------ * Various bug fixes for replication, compaction, the HTTP interface and the Javascript View Server. Apache CouchDB is alpha software and still under heavy development. Please be aware that important areas such as the public API or internal database format may see backwards incompatible changes between versions. Apache CouchDB is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. Relax and prosper, -- Noah Slater, http://people.apache.org/~nslater/

View original post | Add to del.icio.us | Share

The Apache MyFaces team is pleased to announce the release of MyFaces Core 1.1.6. MyFaces Core is a JavaServer(tm) Faces 1.1 implementation as specified by JSR-127. MyFaces Core has passed Sun's JSR-127 TCK and is 100% compliant with the JSR-127 specification. MyFaces Core 1.1.6 is available in both binary and source distributions. * http://myfaces.apache.org/download.html MyFaces Core is also available in the central Maven repository under Group ID "org.apache.myfaces.core". Release Notes - MyFaces Core - Version 1.1.6 Bug * [MYFACES-1287] - Provider for javax.xml.parsers.SAXParserFactory cannot be found * [MYFACES-1310] - IllegalStateException:Strict Servlet api:cannot call getOutputSteam() after getWriter() on Weblogic 8.1 sp 5 * [MYFACES-1311] - MyFaces Portlet at Weblogic 8.1 SP5: Request Parameter weren't submitted * [MYFACES-1379] - CLONE -commandLink actions ignored inside tree2 * [MYFACES-1467] - Validation doesn't run for required fields if submitted value is null * [MYFACES-1504] - oamSetHiddenInput function missing if ... * [MYFACES-1513] - myfaces-api has unnecessary commons-digester dependency * [MYFACES-1543] - mbean_source.jsp not working * [MYFACES-1549] - MyFaces-API issue: getValue of UIInput * [MYFACES-1555] - h:messages and h:message don't use style attribute when rendering * [MYFACES-1581] - UISelectOne encounters exception in call to equals() * [MYFACES-1590] - MyFaces build doesn't work offline - validation of TLDs fails * [MYFACES-1641] - ContentType cannot be set when only text/* media range is accepted * [MYFACES-1707] - log catched exceptions * [MYFACES-1740] - NullPointer exception in ErrorPageWriter * [MYFACES-1744] - Validation messages is shown for SelectOneMenu in case first child is not SelectItems or SelectItem * [MYFACES-1750] - Evaluation of EL-Expression fails with custom PropertyResolver * [MYFACES-1762] - h:messages - error while rendering id and styleClass attributes * [MYFACES-1797] - Config Parameter for refresh Period is never retrieved * [MYFACES-1802] - FacesException and nested exceptions * [MYFACES-1809] - Linkrenderer with TrinidadForm does not render parameters * [MYFACES-1818] - JavascriptUtils.encodeString does not properly translate '\' characters into "\\" (2) characters * [MYFACES-1832] - bad charset encoding on <f:param> tag * [MYFACES-1871] - UIInput throws IllegalArgumentException for unknown event types in broadcast() * [MYFACES-1876] - 1.1.6-SNAPSHOT version is not JDK 1.4 compatible * [MYFACES-1883] - /WEB-INF/faces-config.xml Loaded twice if logging disabled. * [MYFACES-1891] - ClassCastException in converter when Hiding / Showing unselected selectOneRadio Improvement * [MYFACES-1535] - findComponent slow for a high amount of calls * [MYFACES-1552] - Rendering less JavaScript for each button * [MYFACES-1569] - Error message when input text is disabled or readOnly * [MYFACES-1591] - Improved error handling in config management * [MYFACES-1688] - Highlighting of component on error page * [MYFACES-1689] - Reload of faces-config-files if changes are detected * [MYFACES-1853] - ErrorPageWriter causes Facelets/MyFaces confusion * [MYFACES-1874] - Component generation using myfaces builder plugin for 1.1 * [MYFACES-1887] - Print Multiple exceptions information thrown on update model * [MYFACES-1888] - catch Throwable errors when using ErrorPageWriter (myfaces error handling) New Feature * [MYFACES-1784] - Arabizing MyFaces Core Components Enjoy! regards Leonardo Uribe

View original post | Add to del.icio.us | Share

The Apache Archiva team is pleased to announce the release of Archiva 1.1.1. Apache Archiva is an extensible repository management software that helps taking care of your own personal or enterprise-wide build artifact repository. It is the perfect companion for build tools such as Maven, Continuum, and ANT. Archiva offers several capabilities, amongst which remote repository proxying, security access management, build artifact storage, delivery, browsing, indexing and usage reporting, extensible scanning functionality... and many more! The latest release is now available here: http://archiva.apache.org/download.html If you have any questions, please consult: - the web site: http://archiva.apache.org - the archiva-user mailing list: http://archiva.apache.org/mail-lists.html Change Log for Archiva 1.1.1 ============================ Bug • [MRM-584] - Newly created user cannot login • [MRM-631] - network proxy is always used when defined • [MRM-814] - Invalid cron expressions are accepted in Database Scanning • [MRM-873] - repository groups - move up/down should not show when it's not possible • [MRM-883] - RSS syndication java.lang.ArrayIndexOutOfBoundsException • [MRM-884] - network proxy fails after upgrading to archiva 1.1 • [MRM-888] - add notes on reindexing to the upgrade docs • [MRM-891] - Unable to use archiva as http source with maven-stage- plugin • [MRM-892] - Search for java classes and package names is broken • [MRM-895] - Archiva version doesn't appear on the footer when it is installed on Tomcat • [MRM-896] - classifier is appended to pom filename after artifact upload Improvement • [MRM-817] - Artifact information screen should indicate the name of repository in which the artifact resides Thanks, The Apache Archiva team -- Brett Porter brett@apache.org http://blogs.exist.com/bporter/

View original post | Add to del.icio.us | Share

A few days ago, the Ruby core team has announced several newly discovered security vulnerabilities. Ruby versions prior to 1.8.6-p285 and 1.8.7-p70 are vulnerable. The previous version of Ruby Enterprise Edition is also vulnerable because it’s based on 1.8.6-p114.

Earlier Ruby releases had some crash bugs and incompatibility problems. It goes without saying that such problems are unacceptable in production environments, so we’ve been careful and took the time to test 1.8.6-p286 against various test suites:

• We tested it against the Ruby on Rails test suite (edge). All tests passed.
• We tested it against the RubySpec test suite (git HEAD from yesterday). All tests passed. In fact, Ruby 1.8.6-p114 fails a few tests, so p286 is more Ruby-compliant.
• We tested it against Typo 5.0.3’s test suite. All tests passed.
• We tested it against the test suite of various of our internal applications. All tests passed.

So our conclusion is that Ruby 1.8.6-p286 is indeed stable and compatible. Kudos to the Ruby core developers for this excellent release!

We’ve prepared a new Ruby Enterprise Edition release, based on Ruby 1.8.6-p286. The official Ruby on Rails wiki has been running on this Ruby Enterprise Edition version since yesterday (in addition to Phusion Passenger git HEAD), and everything seems to be rock-solid so far.

This Ruby Enterprise Edition release not only includes upstream Ruby’s security vulnerability fixes and other bug fixes, but also some Ruby Enterprise Edition-specific improvements and fixes:

MySQL headers are autodetected Many people have problems installing the MySQL gem, especially on non-Linux platforms. That’s because the gem cannot find the MySQL development headers. The Ruby Enterprise Edition installer now autodetects the MySQL headers, for much better MySQL gem installation success rate. Bug fix: don’t overwrite shebang lines for non-Ruby scripts Normally, the installer changes the shebang lines of all scripts in $PREFIX/bin to the correct location of the Ruby Enterprise Edition binary. ($PREFIX is the location that one installs Ruby Enterprise Edition to) However, this would change all shebang lines, even for non-Ruby scripts. This has been fixed: only the shebang lines of Ruby scripts will now be changed. sqlite3-ruby gem permissions fixed The sqlite3-ruby gem installed itself with the wrong permissions. Its files would be world-writable by default. The installer now fixes this problem. ‘PassengerRuby’ instead of ‘RailsRuby’ The installer used to instruct the user to change the ‘RailsRuby’ option for Phusion Passenger. ‘RailsRuby’ has been deprecated since Phusion Passenger 2.0 in favor of ‘PassengerRuby’, so the installer now instructs the user to change ‘PassengerRuby’ instead. Upgrade instructions Via the source tarball

Please download the source tarball from the download page and run the built in installer, as instructed on the download page. To upgrade, please install Ruby Enterprise Edition to the same location that you specified last time.

Via the Debian package

Please install the Debian package by downloading it from the download page. (click on the “Linux” tab)

[Ruby Enterprise Edition ]
View original post | Add to del.icio.us | Share

2.0.3 is a minor release containing non-intrusive bug fixes and optimizations.

Changes Vendor Rails optimization Some people vendorize Ruby on Rails. In previous versions, Phusion Passenger creates a new framework spawner which caches the code for the vendorized Rails framework. This step has now been removed because it’s redundant. As a result, Phusion Passenger now uses less memory when serving applications that have vendorized Rails. It is therefore especially adviced that shared hosts upgrade to this version. ‘passenger-memory-stats’ now works on non-Linux systems The ‘passenger-memory-stats’ didn’t work correctly on non-Linux platforms. This has been fixed. However, ‘passenger-memory-stats’ is only capable of displaying the real memory usage of processes when running on Linux. Other operating systems don’t provide a way to query the real memory usage, unfortunately. So on non-Linux platforms, ‘passenger-memory-stats’ will display the Resident Set Size instead. WSGI fixes WSGI support in Phusion Passenger is mostly a proof of concept. Nevertheless, we find it worthwhile to fix any WSGI-related bugs that we may encounter. 2.0.3 fixes Python 2.4 compatibility (previous versions require at least Python 2.5), and fixes some WSGI compliance bugs. Thanks to Weyert de Boer for contributing the latter fix. How do I upgrade to 2.0.3? Via a gem

Please install it with the following command:

gem install passenger

Next, run:

passenger-install-apache2-module

Please don’t forget to copy & paste the Apache config snippet that the installer gives you.

Via a native Linux package

Neil Wilson from Brightbox has kindly provided an Ubuntu 8.04 package for Phusion Passenger. The package is available from the Brightbox repository which you can find at:

http://apt.brightbox.net

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb instruction, and then run ‘apt-get update‘).

Once you’ve done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

(Note that Neil is currently packaging 2.0.3, so it might take a while before this release shows up in the apt repository.)

[General ]
View original post | Add to del.icio.us | Share

ApacheCon New Orleans: Open. To Just About Everything! November 3-7, 2008 http://us.apachecon.com/ ========================================= This is a reminder that the EARLY BIRD DISCOUNT ends August 15. Register NOW and save! Be sure to checkout the "Special" registration code if you're reserving a room at the show hotel, the Sheraton. Get the most you can out of your ApacheCon experience. Our CrowdVine Social Networking Site has been setup specifically for the conference. Check out the who's who of who will be there. Join the network and get as involved as you want! Community | http://apacheconus2008.crowdvine.com/ ========================================= ApacheCon US 2008: A week of Open Source at it's best! Hackathon | BarCampApache | OFBiz Symposium | Hadoop Camp In-Depth Trainings | Multi-Track Sessions | BOFs | Business Panel Lightning Talks | Receptions | Fast Feather Track | Expo... and more! - Shane Curcuru & The ApacheCon US 2008 Team http://us.apachecon.com/ 3-7 November -- New Orleans, Louisiana http://apacheconus2008.crowdvine.com/

View original post | Add to del.icio.us | Share

The Apache MyFaces Trinidad team is pleased to announce the release of Apache MyFaces Trinidad Core 1.0.9. Apache MyFaces Trinidad is a JavaServer(tm) Faces 1.2 component library. Trinidad Core 1.0.9 is available in both binary and source distributions: * http://myfaces.apache.org/trinidad/download.html Apache MyFaces Trinidad is available in the central Maven repository under Group ID "org.apache.myfaces.trinidad". Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661&styleName=Html&version=12313158 Enjoy! -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org

View original post | Add to del.icio.us | Share

The Apache MyFaces Trinidad team is pleased to announce the release of Apache MyFaces Trinidad Core 1.2.7. Apache MyFaces Trinidad is a JavaServer(tm) Faces 1.2 component library. Trinidad Core 1.2.9 is available in both binary and source distributions: * http://myfaces.apache.org/trinidad/download.html Apache MyFaces Trinidad is available in the central Maven repository under Group ID "org.apache.myfaces.trinidad". Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661&styleName=Html&version=12313157 Enjoy! -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org

View original post | Add to del.icio.us | Share

Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL Formatting Objects [1] and an output independent formatter. It is a Java application that reads a formatting object tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PS, PCL, AFP, Print and TIFF/PNG. Apache FOP is Open Source software and published under the Apache License v2.0. It took longer than expected but we're happy to present the final Apache FOP 0.95 stable release. This is basically a bugfix release to 0.95beta. The most important changes since the previous stable release (0.94) are: - many bug fixes and improvements in tables, better support for keeps and breaks, new features: conditional borders and background on columns and header/footer/body; - better image handling thanks to the new image loading framework provided by the Apache XML Graphics Commons dependency; - improvements and bugfixes for font handling and font auto-detection/-registration; - performance improvements and memory optimizations for the property handling in the FO tree. - elimination of a potential multi-threading problem. - some feature enhancements for RTF output (partial fo:leader support, fo:page-number-citation) Please note that support for Java 1.3 has been dropped. Only one type of binaries is provided now, that will run on 1.4+ JREs. Other important release notes are available at http://xmlgraphics.apache.org/fop/0.95/releaseNotes_0.95.html For a more complete list of changes, please visit http://xmlgraphics.apache.org/fop/0.95/changes_0.95.html For download information, see the following page: http://xmlgraphics.apache.org/fop/download.html [1] http://www.w3.org/TR/xsl11/ On behalf of the Apache XML Graphics team, Jeremias Maerki

View original post | Add to del.icio.us | Share

The Apache Tuscany team are pleased to announce the 1.3 release of the Java SCA project. Apache Tuscany provides a runtime environment based on the Service Component Architecture (SCA). SCA is a set of specifications aimed at simplifying SOA application development. These specifications are being standardized by OASIS as part of the Open Composite Services Architecture (Open CSA). This 1.3 release is the first release of Tuscany as an Apache top level project, and includes various improvements to the SCA runtime and extensions, along with performance improvements, and numerous bug fixes. See the RELEASE_NOTES and CHANGES file for details, and to download the distributions please go to: http://tuscany.apache.org/sca-java-releases.html To find out more about OASIS Open CSA go to: http://www.oasis-opencsa.org Apache Tuscany welcomes your help. Any contribution, including code, testing, contributions to the documentation, or bug reporting is always appreciated. For more information on how to get involved in Apache Tuscany visit the website at: http://tuscany.apache.org Thank you for your interest in Apache Tuscany! The Apache Tuscany Team.

View original post | Add to del.icio.us | Share

Remember: early bird rates go up in mid-August, so register soon! ApacheCon US and OFBiz Symposium bring together the Apache Community in New Orleans, November 3-7 ApacheCon US to hold new BarCamp at 2008 conference and host Voluntourism Day New Orleans, LA – July 30, 2008 - ApacheCon US, the official user conference of The Apache Software Foundation (ASF), will host new features at this year's US conference to bring the Apache community closer together, including a new BarCamp, a Voluntourism Day, and the social networking site CrowdVine. The conference schedule has been published and registration is open. Register by August 15 to receive Early Bird discount prices. The Apache Open For Business (OFBiz) Symposium is co-locating with ApacheCon US, bringing a new community of users to the event. Attendees will be able to mix-and-match the tracks from both conferences and have the opportunity to network with submitters, experts, and users. New at ApacheCon is BarCampApache, (November 4). The BarCamp will be the first Apache-focused, participant-driven unconference, gathering people interested in The ASF and its various projects to share and learn in an open environment. BarCampApache will be intense with discussions, demos and interaction from participants packed into an ad-hoc event. The BarCamp is free, but due to limited space, pre-registration is required. A special added feature of ApacheCon is Camp Hadoop, (November 6-7). Camp sessions will focus on Apache Hadoop, the platform being utilized by organizations to deliver petabyte scale computing and storage on commodity hardware, and by academic and industrial research groups to teach data parallel computing. Hadoop developers and users will review new projects and case studies of Hadoop applications while participating in interactive discussions on the platform's future. For the first time ApacheCon will host a Voluntourism Day on November 8, a day focused on lending a hand to the New Orleans area. The ASF has always emphasized "community over code" and now it will put that motto into action by assisting and supporting another community in need. Full details on the Voluntourism Day will be announced in September. "New Orleans is still in many ways suffering from the aftereffects of Hurricane Katrina. Our goal is to utilize The ASF's ideals of openness and collaboration to embrace the city's people and culture and work together to bring change. We have a truly dedicated community writing Open Source code and we hope our participants will stay to support the Voluntourism Day," said Lars Eilebrecht, Vice President of Conference Planning, ASF. Prior to this year's conference, ApacheCon US will create a social networking platform to help attendees, speakers, and sponsors to exchange information and ideas leading up to the event in order to foster a stronger sense of community. Users of the ApacheCon CrowdVine site can create a personal profile outlining their interests, network with other users, and write blog posts. Also joining the ApacheCon community in New Orleans are dedicated sponsors and exhibitors including CrowdVine, Day Software, Google, Hewlett-Packard, Hippo, HotWax Media, IONA, Linux Journal, Media Temple, SpringSource, WSO2, and Yahoo! These sponsors play an integral role in supporting Open Source technology and contributing to emerging trends in the industry. Sponsorship opportunities are still available. For details contact Delia Frees at delia@apachecon.com. About ApacheCon US 2008 ApacheCon is the official user conference of The Apache Software Foundation (ASF), drawing ASF Members, innovators, developers, vendors, and users to experience the future of Open Source development. The 2008 US event will take place in New Orleans from November 3-7. The most influential platform dialogue amongst the Apache community at large, ApacheCon is the must-attend user and developer forum showcasing key Apache and Open Source technologies. Attendees meet, mingle, and exchange ideas with like-minded participants on groundbreaking technologies and emerging industry trends, through informal networking, peer discussions, Birds-of-a-Feather sessions, and entertaining social events. Drawing internationally-renowned thought-leaders, contributors, influencers, and organizations in the Open Source community, ApacheCon offers insight into the culture and community that develops and shepherds industry-leading Open Source projects, including Apache HTTP Server—the world's most popular Web server software for ten years running. To find more information about ApacheCon US 2008 please visit http://www.us.apachecon.com ### Media Contacts: Prompt Communications LLC on behalf of ApacheCon James Gerber / Lisa Facinelli Tel: 617 576 5763 jgerber@prompt-communications.com / lfacinelli@prompt-communications.com - Shane Curcuru & The ApacheCon US 2008 Team http://us.apachecon.com/ 3-7 November -- New Orleans, Louisiana http://apacheconus2008.crowdvine.com/

View original post | Add to del.icio.us | Share

The Apache UIMA team is pleased to announce the first release of the UIMA-AS add-on for UIMA. (The release number is 2.2.2-incubating to correspond with the base UIMA level). UIMA-AS adds a highly flexible, robust, and easy to use scaleout capability to the core UIMA framework; it can be considered to be a next-generation replacement for the original CPM (Collection Processing Management) scaleout that is part of the core UIMA framework. Now you can selectively scale up (to take advantage of multiple cores) or scale out (over local and/or wide area networks) just those analytics that need the scaling, thus allowing optimization of computing resources. UIMA-AS has been successfully used on multiple projects, and scaled out to 100's of cores, with no limit in sight. It makes use of JMS (Java Messaging Services) and uses Apache ActiveMQ to support messaging between components. Already written UIMA Components can take advantage of UIMA-AS scaleout with no code or component descriptor changes. There is a short writeup that describes more details about the new capabilities and how to get started using it, on the UIMA website: http://incubator.apache.org/uima/doc-uimaas-what.html UIMA is a component framework supporting integration and deployment of components for the analysis of unstructured content such as text, audio, and video; the main web-site is here: http://incubator.apache.org/uima/index.html Thank you for your interest in Apache UIMA-AS! We look forward to hearing about your experience in using this new capability. --The Apache UIMA Team INCUBATION DISCLAIMER Apache UIMA is an effort undergoing incubation at The Apache Software Foundation (ASF). Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

View original post | Add to del.icio.us | Share

The Apache Tomcat team announces the immediate availability of Apache Tomcat 6.0.18 stable. This release includes many bugfixes over Apache Tomcat 6.0.16. Apache Tomcat 6.0 includes new features over Apache Tomcat 5.5, including support for the new Servlet 2.5 and JSP 2.1 specifications, a refactored clustering implementation, advanced IO features, and improvements in memory usage. Please refer to the change log for the list of changes: http://tomcat.apache.org/tomcat-6.0-doc/changelog.html Downloads: http://tomcat.apache.org/download-60.cgi Migration guide from Apache Tomcat 5.5.x: http://tomcat.apache.org/migration.html Thank you, -- The Apache Tomcat Team

View original post | Add to del.icio.us | Share

Hi, The Apache MyFaces community is pleased to announce its 1.2.7 release of the Apache MyFaces Trinidad Maven2 plugins. These Maven2 plugins have been deployed to the Apache Maven2 and they are mirrored by ibiblio as well. release notes: MyFaces Trinidad - Version 1.2.7-plugins * [TRINIDAD-919] - maven-jdev-plugin does not evaluate <!DOCTYPE> tag correctly for taglib (.tld) files Improvement * [TRINIDAD-987] - add 'scoped-id-holder' and 'multi-scoped-id-holder' to transform.xsl and transform12.xsl * [TRINIDAD-1011] - Add new properties to the maven-faces-plugin * [TRINIDAD-1065] - Support mfp:hidden to hide properties and facets from the tag documentation * [TRINIDAD-1163] - Improvements to property deprecation and a new no-op feature New Feature * [TRINIDAD-953] - Support for Code Examples in Trinidad Components, Validators, and Converters tagdocs * [TRINIDAD-1056] - Chang maven-faces-plugin to stop filtering out metadata Have fun, Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org

View original post | Add to del.icio.us | Share