You can find information about the various pieces of the EnhydraME platform's software on this page. In addition to the expected binary downloads that you can install and run, EnhydraME makes all source code available to its users (and evaluators!). You'll find links to the source code not only for this project, but for the various EnhydraME sub-projects as well. Additionally, you can get access to the licenses for each and every component of EnhydraME, and ensure that the platform and its projects will integrate seamlessly into your own development efforts.
Downloads
The heart of any project is what you can do with it, and of course EnhydraME is no different.
You can download a binary release of the platform, with all related sub-projects, as well
as source code for the platform, documentation, samples, and more. Links to all of these
components can be found on the downloads page.
Additionally, each project has a set of downloads specific to that project. They are located
here:
CVS Repositories
All of the EnhydraME project source code is within CVS repositories. This means that you
can easily view the code for the various projects (see the hyperlinks listed below). Even
more importantly, you are encouraged to make enhancements to the source code; tracking down
bugs, adding features, and even aiding in documentation makes open source work. You can
then use the various project mailing lists to
contribute this code back to the community, and help improve the world (well, at least this
little corner of it).
Each of the EnhydraME projects has its own CVS repository:
License
The EnhydraME platform is licensed under the Enhydra Public License (EPL), version 1.1. You can
read this license online here. This details how
the code and binaries are released, as well as providing information on deployment of the
platform. It is based largely upon the Mozilla Public License,
which is a liberal license allowing you the easiest access to the code and releases.
Additionally, each EnhydraME sub-project has the option to use a different license, as long
as they are compatible with the EPL; a common example is the
Lesser GNU Public License (LGPL).
You should check out the licenses for each of the projects you wish to use: