Free dependency software for linux

Dependency Analyzer is a utility for graphically visualizing Maven2 artifacts dependency graphs. It is using Maven embedder for resolving dependencies and based the Java Universal Network/Graph Framework (Jung) for creating and visualizing the dependency graph. Spring rich client is used for building the GUI.
Enhancements:
- This release remembers previously opened pom details.
- It can show where the dependency comes from as a tool-tip on a link. It can show the path(s) from the main artifact to a dependency.
- A print command has been added. Using variables is supported.
- File drag and drop support has been added.

Depends project is a generic dependency tracker in C++.

The educational purpose of Depends

Much of Depends is its documentation: it explains in much detail how the dependency tracker is implemented and should be clear enough for any programmer to understand both how it is implemented and how to implement one themselves.

The productivity purpose of Depends

The Depends class implements a complete dependency tracker and an associative container for any given value-type and can be used as-is without any real knowledge of how it is implemented. From a productivity point of view, the extra documentation may be a plus, but is certainly not necessary.

When was Depends created?

The very first version of Depends was created for the Jail, which is still very much in its experimental stages at the time of this writing. The dependency tracker, however, took on a life of its own and was improved, debugged, and eventually used for at least one production application I am aware of so far. Part of its life was spent in my "petri-dish": the Developers Corner. It finally re-appeared on SourceForge as its own project on Aug. 8th 2007, where it is now.

Why was Depends created?

For one of the experiments I did on Jail, not all of which are public, I needed a dependency tracker to track the dependencies between singleton instances. The Depends library was first created for this sole and unique purpose. It has since been modified to follow new coding standards and to be incorporated in a proprietary package version manager. A draft of an article about a dependency tracker has become the documentation of that same tracker.

DEPS is a Dependency Extraction and Processing System.
DEPS started life with the graph-includes name. Since it is expected to do much more than just graph #include relationships in C/C++ code, it has been renamed to something hopefully more adequate.
DEPS is a toolkit whose primary goal is to help software authors to deal with internal depencies (eg. C/C++ #includes), and help locating abusive dependencies. It is slowly evolving towards a set of perl classes intended to do general graph processing, complementing the current command-line graph-includes tool.
Main features:
- Supported languages: C/C++ (complete), Perl5 (partial)
- Supported transformations: transitive reduction, regexp-based grouping, consolidation of multiple group levels
- Supported styling operations: group-based coloring, edge annotation
- Supported graph renderers: GraphViz (usable), Tulip (preliminar)
Basic concepts
Note: this section describes best version 0.12, still not ready for release.
DEPS allows you to create graphing projects, eg. for a programs source tree. A graphing project is a set of rules to construct graphs. A first graph gets extracted from your data (eg. C source files), and transformations (eg. file grouping, transitive reduction, color styling) are applied to create more graphs for various usages.
Enhancements:
- The default project class is not confused any more by leading "./" in paths.
- Dependencies are now correctly found again on Windows.
- A new node style to show statistics about group members was added.
- The documentation was updated.

Garden is a dependency injection for PHP5.

Inspired by Spring Framework, it uses XML application context with syntax as similar as possible to Spring context definitions.

Kickstarter

Create example.xml file like this (dont forget to put garden-beans.dtd next to it!):

< ?xml version="1.0" encoding="UTF-8"? >
< !DOCTYPE beans PUBLIC "-//GARDEN//DTD BEAN//EN" "garden-beans.dtd" >
< beans default-lazy-init="true" >

< bean id="dog" class="Dog" file="ext/Dog.php" >
< property name="collar" >
< ref local="dogCollar"/ >
< /property >
< /bean >

< bean id="dogCollar" class="Collar" file="ext/Dog/Collar.php" >
< property name="spiked" value="true"/ >
< /bean >

< /beans >

etx/Dog.php contains:
class Dog
{
private $collar;
public function setCollar($collar)
{
$this->collar = $collar;
}
public function getCollar()
{
return $this->collar;
}
}

etx/Dog/Collar.php contains:
class Collar
{
private $spiked;
public function setSpiked($spiked)
{
$this->spiked = $spiked;
}
public function getSpiked()
{
return $this->spiked;
}
}

StateMenu is a resource-monitoring desktop menu.
Its a popup desktop menu for not only launching apps, but also for monitoring and controlling the state of system resources (like daemons, CPU scaling, firewalls, etc.).
It works with Nautilus/GNOME, Xfce4, ROX Pinboard, and other environments.
Enhancements:
- Removed dependency on version 2.4 of Python by only using module subprocess if it is found.
- Removed PyMODINIT_FUNC macro to compile with Python-2.2.
- Added missing import.

jHomenet is a home automation application. jHomenet uses both X-10 and Dallas Semiconductor 1-Wire network sensors and devices to collect sensor data and control devices.
jHomenet project can be programmed to respond to events, including particular sensor data values or time-of-day events.
Enhancements:
- This is a binary only release that includes several changes.
- Most noticable is the change in the versioning format.
- This change, however, also includes a drastic change in the library versioning and dependency framework.
- Other changes include a revised EventLogger, some UI tweaks, and several new jhomenet-commons JUnit unit tests.
- Some significant changes were also made to the Ant build setup.

Sledge::Plugin::DI is a dependency injection for Sledge.

SYNOPSIS

use Sledge::Plugin::DI;

package Your::Pages;
use Sledge::Plugin::DI;
# no create_* methods!

# in your config.yaml
common:
di:
session: Sledge::Session::Memcached
cache: Sledge::Cache::Memcached
charset: Sledge::Charset::Default
authorizer:
- pages: Your::Pages
authorizer: Null
- pages: Your::Pages::Admin
authorizer: Your::Authorizer::Admin
- pages: Your::Pages::My
authorizer: Your::Authorizer::My
manager:
- pages: Your::Pages
session: Cookie
- pages: Your::Pages::Mobile
session: StickyQuery