Free 2.0.0 build software for linux

PLCash project is a platform-independent personal financial program.
Main features:
- Create and manage personal financial accounts.
- Import and export data from/to Quicken and other financial programs.
- Create reports and analyze your transactions using a sophisticated report generator.
- Import prices to track the performance of your investments.
- Interface with many other programs intuitively, using an industry-standard, transparent data file format.
- Reconcile your records with bank statements.
- Print checks in a variety of ways.

Ingres is a mature, high-performance relational database solution.
The project offers scalability, integration and flexibility to leverage information resources across a wide range of platforms, including Linux, Unix, OpenVMS, and Windows.
Reliable and cost effective, it supports mission-critical applications in small to medium-size businesses and high- volume deployments in large scale enterprises.
Enhancements:
- Numerous major enhancements, code speedups, and bugfixes.

Ivy project is a very powerful dependencies manager oriented toward java dependency management, even if it can be used to manage dependencies of any kind.
For sure, Ivy is integrated with the most popular build management system for java projects.
For simple cases, ivy is really simple to use. Declare your dependencies, and thats all. See the quick start tutorial to check yourself, it should take less than 5 minutes !
Ivy can thus be used to bring the dependency management feature of maven to ant build files, for those of you who already use ant and who do not want to setup a maven project. But Ivy does not stop here, and provides much more great features !
Ivy is able to produce mainly two kind of reports: html reports and graph reports. HTML reports gives you a good understanding of what ivy did, and which dependencies your project depends upon. The graph reports let you have a good overview of the transitive dependencies (see below) and conflicts in your project.
Ivy most common use is to resolve dependencies and copy them in the lib dir of your project. Once copied, your build does not depend on ivy any more. Thus you can easily migrate existing builds using the lib dir pattern to store dependencies. Moreover, you can easily deliver your project with its dependencies so that the build file does not depend on ivy.
With Ivy, you usually do not have to adapt your project to ivy structure, its ivy which can be adapted to your environment.
Even if Ivy comes with a lots of default values to work out of the box, you can change many things in ivy. For sure, the dependencies repositories possibilities covers a lot of uses (file system, url based, repository chaining, ...). But thats not all. You can change the way ivy finds latest versions of your dependencies, you can change of conflict manager, you can choose if you want ivy to copy deps in your project libs or to use them directly from ivy cache, ...
When ivy does not what you want out of the box, you can often extend it to solve your problem. For instance, you can plug your own repository (like scott haug did for a svn repository now available in ivy tools). But you can also defines your own latest strategy and your own conflict manager. See how to extend ivy in the reference doc.
Imagine you have a component that you often reuse in your software developments. Imagine that this component has itself dependencies. Then with classical dependencies management, each time you use this component in your software you have to declare it as a dependency, but also all its dependencies.
With ivy its different: you simply write a dependency file once for the component, declaring its own dependencies, then anytime you want to use this component you simply have to declare a dependency on it.
And this is even more powerful if the component your software depends on changes of dependencies during its own development. Then, without ivy, you have to maintain all your components dependencies declaration each time the dependencies of this component change. With ivy, you update the ivy file of the component and thats it !
If you want to quickly start using this feature or simply see it in action with real world examples, check the official repository: ivyrep
Enhancements:
- This release adds enhanced support for reading Maven2 POM files, cleaner code for easier developer participation, and minor bugfixes (as documented in Jira).

Yed is an Open Source research project; its mission is the developing of a C software library made of modules ( objects )iUnknown.org instanceable in according to the main paradigms of Object Oriented Programming: incapsulation,data hiding and inheritance.

Yed core acts at only C compiler preprocessing level, using particular macros; therefore, using Yed objects is transparent to the C compiler, and it is not necessary to develope additional " translation" tools that have to be run before compiling.

Yed library contains objects that handle XML files, FTP connections, file system operations and so on.

YSlow is licensed under the Mozilla Public License (MPL) version 1.1, with portions licensed by third parties under other license terms.

Major Features:

1. Performance report card
2. HTTP/HTML summary
3. List of components in the page
4. Tools including JSLint

Enhancements: Is certified to work with Firefox 3.5 and Firebug 1.4b5.

Requirements: Mozilla Firefox

Gmsh is an automatic three-dimensional finite element mesh generator, primarily Delaunay, with built-in pre- and post-processing facilities. Gmsh projects goal is to provide a simple meshing tool for academic problems with parametric input and advanced visualization capabilities.
Gmsh is built around four modules: geometry, mesh, solver and post-processing. All geometrical, mesh, solver and post-processing instructions are prescribed either interactively using the graphical user interface (GUI) or in ASCII data files using Gmshs own scripting language.
Interactive actions generate language bits in the input files, and vice versa. This makes it possible to automate all treatments, using loops, conditionals and external system calls. A brief description of the four modules is given hereafter.
Enhancements:
- This release adds support for STEP, IGES, and native OpenCascade models.
- It also includes a brand new geometry and mesh graphics pipeline, a new mesh I/O layer (with support for industry-standard UNV, BDF, and STL files), and an improved graphical interface (with immediate application of changes in the option panels and a reworked visibility browser).
- The release also adds support for incomplete second order elements (8-node quads, 20-node hexas, etc.), offscreen rendering, and scalable vector graphics (SVG) output.

Vexi is a platform for creating and publishing Graphical User Interfaces that can be used over the Internet or an intranet.

Vexi project features a very simple and powerful syntax based on xml and javascript, a set of complete, extensible, themable widgets, and a sandbox-like security model to protect users.

Vexi2 is in the final stages of stabilization. All features have been implemented. Most remaining work to be done is on project infrastructure (documentation, demos, etc) so that a visitor can easily use and learn about Vexi.

Soon Vexi will be able to adapt to each browser and platform, allowing it to work on most desktop computers without administrative intervention. Currently it requires Java is present on the client machine but the native builds are the next focus for the project.