Embedded Emmet

Starting with Danno 1.1, the WAR files in a Danno download have an embedded Emmet installation. If you are using a pre-built Danno WAR file you do not need to download and install a separate Emmet WAR file.

Downloading an Emmet binary distribution.

Binary distribution ZIP files for Emmet are available for download from the "Metadata.net" project on SourceForge. These files contain one or more WAR files, and a README.txt file with some simple installation and tailoring instructions.

The WAR files in the binary distribution are primarily intended to allow you to setup a local test installation of Emmet. They are preconfigured to use "localhost" as the server hostname and have security and access control disabled. You can make simple configuration changes by expanding the WAR file and editing properties files, but if you are intending to use Emmet in production, you would be advised to follow the procedures described in the "Customizing Emmet" section. This (currently) entails building Emmet from a source distribution or Subversion checkout.

Checking out the Sources from Subversion

A complete distribution may also be obtained from the "Metadata.net" project's Subversion repository on SourceForge. You can checkout the project from the command shell using the following command:

     svn co https://metadata-net.svn.sourceforge.net/svnroot/metadata-net/emmet/trunk emmet

Alternatively, you can use the Eclipse "Subversion Repositories" view to checkout Danno into your Eclipse workspace as follows. (These instructions assume that you are using the "Subversive" plugin and that you also have the Maven plugin installed.)

1. Start Eclipse and switch to the workspace you want to use.
2. Open the SVN Repositories view.
3. Use the view's New Repository Location wizard (invoke it via the view's tool bar or the context menu) to add the repository location for the "Metadata.net" SVN repository. Use "https://metadata-net.svn.sourceforge.net/svnroot/metadata-net" as the repository URL.
4. Expand the "metadata-net" entry, select "emmet/trunk", and use the context menu to start the "Check Out" wizard.
5. When the checkout of the "emmet" project has completed, Eclipse will attempt to build it, and in the first instant the build will fail. This is normal.
6. Select the "emmet" the project in the Navigator view, and use the context menu to invoke "Maven > Enable Nested Modules". (If there is no "Maven>Enable Nested Modules" in the context menu, open the Maven preferences, and check the checkbox for "Support multiple Maven modules mapped to a single Eclipse project".)

Normally this will be sufficient for Emmet to build. Note: if this is the first time you have built Emmet on this machine, Maven will spend some time downloading Emmet's dependencies to your local repository. This is normal.

Fetching Emmet from a Maven repository

In the future, we intend to implement a public Maven repository to serve releases and snapshots of various "metadata.net" projects.

Obtaining Technical Documentation.

The primary source of technical documentation for the Emmet project is the project's Maven site. The source for this documentation is in the project's subversion repository; look in the ".../emmet/src/site" directory.