grails

A new version of the Amazon S3 plugin is now available.

The new release contains changes to help the plugin play nicely in a clustered environment:

• Quartz jobs are now non-volatile and durable to stop them being deleted/recreated when a node is stopped/started
• S3Asset now contains a hostName property (and hence a new column that you will need to add to the DB) which holds the host name of the server that created the row. This allows the plugin job to only try and upload assets where the local file exists on the server that it is running on.

The latest release of the Amazon S3 plugin for grails is now available.

Version 0.6.3.2 provides some bug fixes as well as several improvements.

• The S3 access/secret key pair can now be set on a per-asset basis
• The bucket name can be set on a per-asset basis. Note that it will be prefixed with the access key used in order to avoid uniqueness errors.
• An ACL (access control list) can be specified for passing through to S3 in order to prevent public access to your assets if required
• Unnecessary default options are no longer created in the S3Asset.options map and they are eager loaded to avoid flushing errors and extra queries
• The plugin is now built with Grails 1.1.1 and the Quartz 0.4.1 plugin

The full documentation for the plugin can be found here.

Version 0.6 of the Grails Amazon S3 plugin has been released. This version adds further configuration options to the plugin as well as making better use of jets3t's multi threaded API methods to improve upload/delete performance (the number of concurrent threads is controlled by jets3t configuration - see http://jets3t.s3.amazonaws.com/index.html for details).

See http://grails.org/plugin/amazon-s3 for the latest documentation.

The latest version of the Amazon S3 plugin has been released which incorporates the latest jets3t snapshot library (0.7.1-SNAPSHOT) which has improved compatibility with the Eucalyptus open source EC2/S3 clone and some bug fixes.

The plugin S3 event handling code was also updated to avoid stale object and optimistic locking exceptions being thrown by Hibernate.

If anyone is trying to use Intellij with Grails 1.1 - just a quick post to say that the EAP release (build 9805) seems to have fixed the Grails 1.1 plugin problems.

It Worked perfectly with new projects. To get it to work with an existing project I just had to:

• remove all unnecessary plugin source directories & libraries
• select Tools->Run Grails Target
• type "clean" to run a grails clean, let it do it's library update thing and magically everything seems to fix itself up.

I think there might possibly be a problem with global plugins - didn't seem to pick up those directories. Hopefully they will fix this before 8.1.1 is released.

In between meeting all the interesting folk at OSDC, I attended the Sydney Groovy (and Grails) User Group. I presented a short talk on the new features in Grails 1.1 then demoed the Portlets Plugin and new features in the WebTest Plugin 0.6. Dave Cameron then gave a great Intro to Gant talk with comparisons to buildr. Come along next time to hear more from Dave about Gradle :)

The group is organsied by Nick Carrol from Thoughtworks and the venue (in The Rocks near Sydney harbour) was great. If you're ever in the area, get onto the mailing list and see when the next meeting is.

-- Lee