We have finally released Lure Version 2.0.0. Several enhancements were added in this release but the most important new feature is the Lure Configuration Editor which is a GUI based editor for Lure property files. This will substantially simplify and speed up configuration of Lure based database projects.

The Lure Configuration Editor was built on the Eclipse Rich Client Platform and as a result we ended up moving the entire Lure application to the Eclipse RCP. As a consequence the entire structure and layout of the distribution had to change. Thus, even though the basic code extraction and deployment behaviour did not change significantly in this release, we thought it appropriate to increase the major version number.

The complete list of new features and enhancements are:

  1. Lure Configuration Editor - an Eclipse RCP based UI editor for Lure property files.
  2. Support for Windows, Linux GTK and Mac OS X (and separate distributions for each platform)
  3. Support for multiple Lure connect files within the same root folder. (This simplifies property file management.)
  4. Support for using any Oracle® database user with special privileges instead requiring the use of the SYSTEM user.
  5. Options to override include/exclude filters during export. During import filters are not applied any more.

Yes we are working hard on a new release which will be available for download in the second quarter of this year.

This new release will primarily include a brand new user interface application for setting up and maintaining the configuration files of a Lure project. After careful consideration and evaluation we decided to base this new application on the Eclipse Rich Client Platform (RCP), and we are very pleased with the way in which it is turning out. And we are confident that you will be pleased too!

This is just the first step though as we already have plans on the way to develop a full featured user interface for synchronization, also based on the Eclipse RCP and the existing Lure application.

Initially these UI components will be available as standalone applications but we will also make them available shortly after as Eclipse plugins.

We will keep you posted here about the progress and let you know as soon as possible when a release date has been confirmed.

We just released Lure Version 1.0.1. This is a minor enhancement release in which we added first class support for the Perforce configuration management system. The same integration features already available for Subversion are now also available for Perforce.

Lure makes use of the Perforce command-line client, p4. Before using Lure together with Perforce you will need to set up a Perforce client workspace and synchronize with any files already present in the depot.

Perforce integration plays a role during both Export and Import.

  • During Export Lure will query Perforce to determine the HEAD change number. This number is then used as the revision number for all versioned patch files that are generated during the Export.
  • Before exporting any source file Lure will first determine if the file is in a read-only status on the file system. If it is then Lure will execute "p4 edit" against this file which will then add the file to the default changelist. This eliminates the need for users to add these files manually to the changelist before running Export.
  • Before exporting any changes to a table source file Lure will query the Perforce repository to determine if any later versions of the table source file has been committed to the depot. If there is a later version available then Lure will not export the change to the table file but instead log a message to indicate to the user that the table file must first be synchronized with the depot. This is required since otherwise the generated patch file will not correctly update the table to the latest version.
  • During Import Lure will connect to the Perforce depot and retrieve older versions of the table source files as required. This procedure is needed in order to determine which patch files to apply to the target table.
  • Finally, the integration with Subversion was also enhanced in this release. Before Lure exports changes to any source file it will first determine if the source file is in a read-only state. If it is then Lure will attempt to make it writable by executing the "svn lock" command against this file.

We believe that these changes will allow for a much smoother workflow when using Lure together with either Subversion or Perforce.

In the past week we changed our hosting service provider and you might have experienced some difficulties in accessing our website during this time.

We apologize if this caused you any inconvenience but we are confident that this change will result in a faster more reliable service.