As usual, the Download page now points to this stable release:

http://seasr.org/meandre/download/

The raw artifacts are available at the SEASR repository:

http://repository.seasr.org/Meandre/Releases/1.4/1.4.5/

Visible changes since 1.4.4:

• Workbench now supports flows written in ZigZag
• Workbench can output flows to the .mau format
• Bug fixes in the job submission API for flows that finish quickly
• Flow RDF representations can be converted to ZigZag
• Infrastructure web API and HTML interface added “Publish All” ability
• Bug fixes for multiple users running the same flow
• Stack trace is now printed for the failing Component when a Flow execution aborts unexpectedly

The artifacts of the release are available here:

http://repository.seasr.org/Meandre/Releases/1.4/1.4.4/

As always, the new release is available at the Download page:

http://seasr.org/meandre/download/

Visible changes since 1.4.3:

• fixed problem in Infrastructure’s jar servlet plugin that was preventing the Eclipse plugin from working properly

• upgraded to Eclipse plugin 1.2.9

• fixed problem with Windows release zips that sometimes caused strange “unable to create directory” errors, which in turn created incomplete installations.

• Components can now access their own ‘run’ resources directory to write files to via the ComponentExecutionContext they receive when executed.

Changes:

• Bug fixes

• New ConfigurableWebUI class (for use by Component developers)

• Jobs (Flow Executions) now track which user submitted the job.

• Meandre Manager - administration tool for users, flows, and components
• Meandre Infrastructure - execution environment
• Meandre Development Eclipse plug-in - tool for installing components
• Meandre Workbench - visual icon-based programming environment
• Meandre Zig-Zag - development scripting language
• Community Hub : Keyword Cloud – end-user gateway to published applications (flows)
• Component and flow repositories

Our goal with this release was to reach developers who want to create new components and begin application development with the SEASR environment. We encourage you to download and provide us feedback.

To download Meandre, Components and Examples, click here.

• Fixing known bugs.
• Preparing the tools to be easy to install and run.
• Finishing documenting the code and the user manual.
• Sketching a quick start guide and a tutorial.
• Preparing the website.

I guess we can say that something is coming

The main changes are under the hood.  I refactored most of the code to remove the static dependencies.  Now you can start many self-contained MeandreServers in your embedded usage of Meandre.  This will simplify writing test cases against the web services api.  I have not moved the old (1.2) web services test, because it needs revamping.

I have also been working on adding new tools:

1. Mau files are now self-contained. A mau file is a jar containing the repository rdf and all the contexts required to run (jars). This is usually generated via the ZigZag compiler or interpreter.
2. Improved the ZigZag compiler to generate the new mau file format.
3. Modified the ZigZag run time to be able to run the new mau files.
4. Yes, you heard it right. I added a ZigZag interpreter.  It comes with a console and you can build flows incrementally, merge flows together, save flows and maus, run a flow, etc, among other things. Just type “help” and it will talk to you.

I finally gave up and learned ant.  Great news, I guess, for the rest of the people on the team:).  This version (1.3) includes my take on the old (1.2) build.xml.  It provides the following tasks:

• compile
• compile-tests
• clean
• run-tests
• test-reports
• javadoc
• dist

No, it does not provide a run task, or like capability. You should not run the Meandre server there. The dist task generates the usual libraries (and a few more I have added) and 4 standalone jars:

• meandre-server-X.Y.jar (Meandre server)
• zz-X.Y.jar (The ZigZag interpreter conole)
• zzc-X.Y.jar (The ZigZag compiler)
• zzre-X.Y.jar (The ZigZag runtime for MAU files)

You can run each of them by typing java -jar name.jar. So, for instance if you want to run the core, copy meandre-server-X.Y.jar to wherever you want to have the working directory and run java -jar meandre-server-X.Y.jar. That’s it: self contained and auto configured. You can stop it then and play with the config files if you want to tweak things–or instance use MySQL/Oracle instead of the embedded Derby.

As I said before, this is for intrepid souls.  Please let me know if you run into problems, bugs, etc. Also, jira now contains a Meandre-Terracota-Executor project; feel free to report the bugs there directly and I will do my best to catch up.