Keros 1.2

Summary

Summary

Keros provides the following functionality:

There should be a minimal learning curve to effectively use Keros.  Ideally it should work "right of of the box."
Keros must allow customization regardless of how it is used.  Often, default values are provided that can be overwritten per desired need.
Keros is completely reusable and designed, by default, to provide "good enough" functionality.  For example, the included Ant build script, keros-project should be sufficient for building most Java projects.
Projects are not just about building alone - additional functionality, such as cross platform scripting, is required so as to "leave one's options open."  Clearly the "write once, run everywhere" montra is very desirable.  Not binding one's projects to any specific platform as well as providing enough "plumbing" to be project ready - is a tremendous plus.  With that said, the Keros does all this and then some.
Build scripts that will build most, if not all, projects.  The minimal requirement is to define some properties and/or environment variables - both work equally well!  Please note:  the aforementioned may be required when a default value is not "good enough" or some dependency requires additional data.
Inevitably when creating a project, some scripting functionality will be needed - for instance, iterating over a collection of files to perform some action.  Keros provides plenty of useful script like functionality.  Additionaly, by standardizing on Java and Ant, all platforms that support them will support Keros too.

Please note:  Keros was built by software engineers for everyone.  By this, Keros "works equally well" for a software engineer who needs a cross platform environment to a release engineer who must build and manage applications - all are served equally well.

SourceForge.net Logo