Manuel Pichler - projects

PHPMD 1.1.0 released

nospam@example.com (Manuel Pichler) — Mon, 21 Mar 2011 11:42:15 +0100

Version 1.1.0 of PHPMD was released on March the 20th 2011. The key features for this release were two new rules. The first one utilizes the Coupling Between Objects (CBO) metric to detect strongly coupled classes. The second one detects the usage of PHP's questionable goto statement. Beside that we have closed a minor bug in the LongVariable rule, where also private properties with descriptive names were reported. And finally we have replaced deprecated PHPUnit features in the PHPMD's test suite, so that PHPMD's tests should now work with PHPUnit 3.4.x and 3.5.x without deprecated warnings.

Features

Implemented #10474873: Add rule for PHP's goto statement. Implemented with commit #2745a20.
Implemented #10474987: Implement rule for CBO metric. Implemented with commit #14277b4.
Implemented #11012465: Replace deprecated PHPUnit features in test suite. Implemented with commit #4adb88d.

Bugfixes

Fixed #10096717: LongVariable rule should not apply on private properties. Fixed with commit #f063bc9.

Download

You can download release 1.1.0 through PHPMD's PEAR Channel Server or you can download the release as a Phar archive

A brief introduction to the Coupling Between Objects metric

nospam@example.com (Manuel Pichler) — Tue, 15 Mar 2011 11:59:00 +0100

In this blog post I will give you a brief introduction into the Coupling Between Objects metric, that is one of the metrics calculated by the static code analysis tool PHP_Depend.

The Coupling Between Objects or CBO metric was originally defined by Chidamber & Kemerer in their IEEE paper "A Metrics Suite for Object Oriented Design" [1]. This software metric represents the number of other types a class or interface is coupled to. The CBO metric is calculated for classes and interfaces. It counts the unique number of reference types that occur through method calls, method parameters, return types, thrown exceptions and accessed fields. But there is an exception for types that are either a subtype or supertype of the given class, because these types are not included in the calculated CBO value.

Excessive coupled classes prevent reuse of existing components and they are damaging for a modular, encapsulated software design. To improve the modularity of a software the inter coupling between different classes should be kept to a minimum. Beside reusability a high coupling has a second drawback, a class that is coupled to other classes is sensitive to changes in that classes and as a result it becomes more difficult to maintain and gets more error-prone. Additionally it is harder to test a heavly coupled class in isolation and it is harder to understand such a class. Therefore you should keep the number of dependencies at a minimum.

Thresholds

Based on their research Sahraoui, Godin and Miceli [2] suggest a maximum CBO value of 14, because higher values have negative impacts on several quality aspects of a class, which includes the maintainability, stability and understandability.

Bibliography

[1]

http://www.iiitd.ac.in/PhD2010/papers/SW_Paper2.pdf

IEEE Transactions on Software Engineering; A Metrics Suite for Object Oriented Design; Chidamber & Kemerer, 1994

[2]

http://www.iro.umontreal.ca/~sahraouh/papers/ICSM00.pdf

Software Maintenance, 2000. Proceedings. International Conference; Can metrics help to bridge the gap between the improvement of OO design quality and its automation?; Sahraoui, Godin, Miceli; 2000

PHP_Depend 0.10.2 released

nospam@example.com (Manuel Pichler) — Mon, 28 Feb 2011 11:25:00 +0100

We are proud to announce release 0.10.2 of PHP_Depend. Beside two bug fixes this release implements four new software metrics:

Efferent Coupling: The number of classes a class depends on.
Afferent Coupling: The number of classes that depend on a class.
Number of Public Methods: The public api/interface of a class.
Coupling Between Objects: The coupling of a class.

A detailed CHANGELOG can be found on the project's download page and a complete, detailed description of the newly implemented software metrics in PHP_Depend's metric catalog.

Brief introduction to the Class Interface Size metric

nospam@example.com (Manuel Pichler) — Fri, 25 Feb 2011 16:50:00 +0100

This blog post will give you a brief introduction into the Class Interface Size metric, as it is calculated by the static code analysis tool PHP_Depend.

The Class Interface Size or CIS metric is measure of the public services that a class provides. This metric was orginally defined in the QMOOD model [1] by Bansiya & Davis.

The orginal version of the CIS metric was defined as the number of public methods that a class provides. Each of these methods can be seen as a service where surrounding application can send messages to or receive messages from a class.

CIS = public(NOM)

A newer variant of the CIS metric also includes the public attributes of a class, because theses properties can also be used to transport messages or information between a class and the surrounding application.

CIS = public(NOM) + public(VARS)

PHP_Depend uses the second variant and counts all public methods and attributes declared in a class to calculate its Class Interface Size metric.

This metric is a good indicator for the choosen software design. Several classes with a high CIS value are a sure sign that the design of the analyzed software prefers composition over inheritance to share common functionality between different components. So in most cases a high value is a good a sign, because composition increases the reusability and flexibility. But there are also situations where wrongly used composition of functionality leads to a design that is harder to understand and maintain.

Thresholds

It is not easy to define good thresholds for this metric, because those values heavy depend on the choosen design, e.g. inheritance or composition. But in generall we can say that is best practice to limit the public interface that can be used to alter the internal state of an object. Therefore we suggest 20 as a reference point for the upper limit.

Bibliography

[1]

http://www.ptidej.net/teaching/inf6306/fall09/notes/course4/Bansiya02-QualityModel.pdf

IEEE Transactions on Software Enginerring; Hierarchical Model for Object-Oriented Design Quality Assessment; Bansiya & Davis; 2002

PHP_Depend 0.9.16 bugfix release

nospam@example.com (Manuel Pichler) — Sat, 19 Jun 2010 13:07:40 +0200

Today/Yesterday we have released the bugfix version 0.9.15 and 0.9.16 of PHP_Depend. With these releases we have closed a critical bug in PHP_Depend's handling of namespaces, where identical class names in two different namespaces resulted in an endless loop, so that the php process died with a fatal error.

Fixed #152: Endless loop bug for identical class and parent name. Fixed in svn revision #1320.
Fixed #153: Only count those classes and interfaces that are flagged as user defined types. Fixed in subversion revision #1327.
Implemented #154: Make execution order of analyzers reproducable. Implemented in svn revision #1331.

As always, you can get the latest PHP_Depend version from its PEAR channel: pear.pdepend.org:

mapi@arwen ~ $ pear channel-discover pear.pdepend.org
mapi@arwen ~ $ pear install pdepend/PHP_Depend-beta

Or you can fetch the sources from the subversion reposition:

mapi@arwen ~ $ svn co http://svn.pdepend.org/trunk pdepend

And additionally you can find a repository mirror on github:

mapi@arwen ~ $ git clone git://github.com/manuelpichler/pdepend.git

phpUnderControl 0.6.0beta2 released

nospam@example.com (Manuel Pichler) — Thu, 10 Jun 2010 12:25:00 +0200

Today I have released the second beta version of phpUnderControl. Beside several minor tweaks and bug fixes, this release contains one additional feature I was asked for during the IPC in Berlin. This feature allows you to specify a maximum number of log entries that will be shown in the generated metric charts. This can be very useful once you have a project with a great amount of builds and the chart rendering gets slower and slower.

This feature adds a new option --max-number to phpUnderControl's chart command. To rebuild all your charts you can call phpUnderControl's shell script with the following command:

  mapi@arwen ~ $ phpuc --force-update --max-number 42 \
                 /opt/cruisecontrol/logs/phpUnderControl \
                 /opt/cruisecontrol/logs/phpUnderControl

You can get the latest release of phpUnderControl through its pear channel:

  mapi@arwen ~ $ pear upgrade --alldeps phpuc/phpUnderControl-0.6.0beta2
  Starting to download phpUnderControl-0.6.0beta2.tgz (546,314 bytes)
  ...................................................................
  .............................done: 546,314 bytes

or you can get the latest development version on github.

Artikel zum Thema Softwaremetriken

nospam@example.com (Manuel Pichler) — Wed, 12 May 2010 09:04:12 +0200

This blog post is in German as the mentioned article was published in German.

In der heute erschienenen Ausgabe 4.10 des PHP Magazins ist auch ein Artikel von mir enthalten, und wie sollte es wohl anders sein *Trommelwirbel*, beschäftigt der sich mit dem Thema Softwaremetriken In diesem Artikel gibt es eine sehr ausführliche Einführung in die Thematik, mit eine Reihe von praktischen Beispielen und den daraus ableitbaren Aussagen über den untersuchten Quelltext.

Über Kommentare, Anregungen und Kritik rund um den Artikel würde ich mich sehr freuen. Und sollte euch der Artikel gefallen haben, empfehle ich die Internationale PHP Conference 2010, die vom 30. Mai bis 2. Juni in Berlin stattfindet, an der ich teilnehmen und zwei Vorträge halten werden.

PHP-Magazin Artikel zum Thema Softwaremetriken

nospam@example.com (Manuel Pichler) — Wed, 12 May 2010 09:04:12 +0200

This blog post is in German as the mentioned article was published in German.

PHP_Depend 0.9.13 bugfix release

nospam@example.com (Manuel Pichler) — Mon, 10 May 2010 17:31:00 +0200

Today we have released the bugfix version 0.9.13 of PHP_Depend, the tool to measure several software metrics for your PHP application. This release fixes two critical bugs. One in the tokenizer implementation, which has modified valid code under test in such a way, that it has become invalid PHP code. The second fix is related to PHP_Depends's test code, where a missing require_once statement has caused a E_FATAL while running the test suite in PHPUnit's process isolation mode.

Fixed #145: Incorrect require_once statement in ASTSwitchStatement source file. Fixed in svn revision #1262.
Fixed #150: Invalid nowdoc substitution has produced broken code. Fixed in svn revision #1266.

As always, you can get the latest PHP_Depend version from its PEAR channel: pear.pdepend.org:

mapi@arwen ~ $ pear channel-discover pear.pdepend.org
mapi@arwen ~ $ pear install pdepend/PHP_Depend-beta

Or you can fetch the sources from the subversion reposition:

mapi@arwen ~ $ svn co http://svn.pdepend.org/trunk pdepend

And additionally you can find a repository mirror on github:

mapi@arwen ~ $ git clone git://github.com/manuelpichler/pdepend.git

Goodbye Cologne

nospam@example.com (Manuel Pichler) — Thu, 29 Apr 2010 13:20:00 +0200

As many of you may already have noticed, there will be a big change in my career as a professional software engineer and architect this summer. Together with Kore and Toby I am in the process of founding a company. The focus of this company will be on services all around the whole quality life cycle in PHP projects.

Under the hood of our company we will also offer support, trainings and consulting for several quality assurance tools, like pdepend, phpmd and phpUnderControl. For you, this opens a great opportunity. You can use the tools and the documentation, as well as participate in the community, as usual. But from now on you can also purchase professional support, if you get stuck or need general assitance. And when you miss a feature or need an individual extension for one of these tools, don't hesitate to contact us.

I am really excited what cool things will happen in the next couple of years and I am looking forward to cowork with professionals like Toby and Kore.

To finalize the little marketing for the company and its services I would appreciate to meet you, your colleagues and your compmany, to give presentations or into-depth trainings on one of the tools or on quality assurance in general.

PHP_Depend 0.9.12 release

nospam@example.com (Manuel Pichler) — Sun, 25 Apr 2010 14:44:15 +0200

I am proud to announce the 0.9.12 release of PHP_Depend. PHP_Depend is a low level static code analysis tool. It takes the given source and calculates several software metrics for the code. This data can be used by software-developers, architects and designers to control the quality of a software-product without time consuming code audits.

This new release of PHP_Depend has done a great step into the direction of a token free PHP_Depend version. This means future versions of PHP_Depend will work without the need to traverse linear token streams up and down, to measure metrics. Instead PHP_Depend will rely on it's internal abstract syntax tree, that represents the logical structure of the analyzed source code. With this solution it will be possible to implement several new features that will make PHP_Depend more useful, for example static callgraph analysis.

Implemented #97: Replace current token approach in CCN- and NPath-Analyzer with AST-Nodes. Implemented in svn revision #1248.
Implemented #125: PHP_Depend silently parses list statements. Fixed in svn revision #1223. Thanks to Joey Mazzarelli for providing this patch.
Implemented #126: Generate reproducable node identifiers instead of random numbers. Implemented in svn revision #1244.
Fixed #128: Variable variables in foreach statement cause an exception. Fixed in svn revision #1237.
Fixed #133: Fatal error: Maximum function nesting level of '100' reached, aborting! in /usr/share/pear/PHP/Depend/Util/Log.php on line 109. Fixed in svn revision #1257.
Fixed #134: ASTReturnStatement is not derived from ASTStatement. Fixed in svn revision #1250.
Fixed #135: Several Statement classes do not inherit ASTStatement. Fixed in svn revision #1255.

As always, you can get the latest PHP_Depend version from its PEAR channel: pear.pdepend.org:

mapi@arwen ~ $ pear channel-discover pear.pdepend.org
mapi@arwen ~ $ pear install pdepend/PHP_Depend-beta

Or you can fetch the sources from the subversion reposition:

mapi@arwen ~ $ svn co http://svn.pdepend.org/trunk pdepend

And additionally you can find a repository mirror on github:

mapi@arwen ~ $ git clone git://github.com/manuelpichler/pdepend.git

Howto create custom rule sets for PHPMD

nospam@example.com (Manuel Pichler) — Thu, 08 Apr 2010 14:25:00 +0200

In this blog post I will describe a useful feature in PHPMD that will simplify your life when it comes to create custom rule sets for PHPMD. PHPMD can be seen as an one level down/low level equivalent to PHP_CodeSniffer. It is a simple command line tool that can be used to check your application's source code for possible bugs, suboptimal or overcomplicated code. The current release of PHPMD ships with three default rule sets. The first set of rules tests the codesize of class, methods and functions. The second rule set contains rules that check your code for unused variables, methods etc. and finally there is a rule set that tests the code against some naming conventions.

Normally when you start using a quality assurance tool, you will not want to use it's default configuration. Sometimes you would like to use only a subset, because the full stack will produce too much noise, or you would like to customize some thresholds, because the factory defaults do not fit to your environment. In this blog post I give a short introduction into PHPMD's rule set syntax and howto to create your own rule set, by reusing parts of the existing default configuration.

If you would like to only pick some of the rules that come with PHPMD and you want to customize some of the predefined thresholds, you can do this by creating your own rule set file that references a custom collection of rules with an individual configuration.

Starting with an empty ruleset.xml file

The simpliest way to start with a new rule set is to copy one of the existing files and remove all the rule-tags from the document body. Otherwise you can use the following example as a template for your own rule set file. You should change the content of the @name attribute and <description /> element to something that describes the purpose of this set.

<?xml version="1.0"?>
<ruleset name="My first PHPMD rule set"
         xmlns="http://pmd.sf.net/ruleset/1.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://pmd.sf.net/ruleset/1.0.0
                     http://pmd.sf.net/ruleset_xml_schema.xsd"
         xsi:noNamespaceSchemaLocation="
                     http://pmd.sf.net/ruleset_xml_schema.xsd">
    <description>
        My custom rule set that checks my code...
    </description>
</ruleset>

Adding rule references to the new ruleset.xml file

The first thing we would like to do is to add all unused code rules to the new rule set file. This can simply be done with a <rule /> element that references the entire unused code rule set that comes with PHPMD.

<?xml version="1.0"?>
<ruleset name="My first PHPMD rule set"
         xmlns="http://pmd.sf.net/ruleset/1.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://pmd.sf.net/ruleset/1.0.0
                     http://pmd.sf.net/ruleset_xml_schema.xsd"
         xsi:noNamespaceSchemaLocation="
                     http://pmd.sf.net/ruleset_xml_schema.xsd">
    <description>
        My custom rule set that checks my code...
    </description>

    <!-- Import the entire unused code rule set -->
    <rule ref="rulesets/unusedcode.xml" />
</ruleset>

That's it. Now the custom rule set applies all unused code rules against the analyzed source code.

We would also like to use the cyclomatic complexity rule from the existing codesize set in our custom rule set. To achieve this we can reuse the same syntax with a <rule /> element and a @ref attribute.

<?xml version="1.0"?>
<ruleset name="My first PHPMD rule set"
         xmlns="http://pmd.sf.net/ruleset/1.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://pmd.sf.net/ruleset/1.0.0
                     http://pmd.sf.net/ruleset_xml_schema.xsd"
         xsi:noNamespaceSchemaLocation="
                     http://pmd.sf.net/ruleset_xml_schema.xsd">
    <description>
        My custom rule set that checks my code...
    </description>

    <!-- Import the entire unused code rule set -->
    <rule ref="rulesets/unusedcode.xml" />

    <!-- Import the entire cyclomatic complexity rule -->
    <rule ref="rulesets/codesize.xml/CyclomaticComplexity" />
</ruleset>

Now that the new rule set uses the cyclomatic complexity rule we would also like to customize some of the rule's properties. First we will increase the rule's priority to the highest possible priority value 1 and we also decrease the threshold when the rule reports a violation. This customization can be done with same xml elements that are used to configure the original rule, so that you can take a look at one of the original rule set file.

<?xml version="1.0"?>
<ruleset name="My first PHPMD rule set"
         xmlns="http://pmd.sf.net/ruleset/1.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://pmd.sf.net/ruleset/1.0.0
                     http://pmd.sf.net/ruleset_xml_schema.xsd"
         xsi:noNamespaceSchemaLocation="
                     http://pmd.sf.net/ruleset_xml_schema.xsd">
    <description>
        My custom rule set that checks my code...
    </description>

    <!-- Import the entire unused code rule set -->
    <rule ref="rulesets/unusedcode.xml" />

    <!--
        Import the entire cyclomatic complexity rule and
        customize the rule configuration.
    -->
    <rule ref="rulesets/codesize.xml/CyclomaticComplexity">
        <priority>1</priority>
        <properties>
            <property name="reportLevel" value="5" />
        </properties>
    </rule>
</ruleset>

You should know that PHPMD handles all custom settings additive. This means that PHPMD keeps the original configuration for every setting that isn't customized in a rule reference.

Excluding rules from a rule set

Finally we would like to reuse the naming rule set of PHPMD. But we don't like the two variable naming rules, so that we must exclude them from out rule set file. This exclusion can be achieved by declaring an <exclude /> element within the rule reference. This element has an attribute @name which specifies the name of the excluded rule.

<?xml version="1.0"?>
<ruleset name="My first PHPMD rule set"
         xmlns="http://pmd.sf.net/ruleset/1.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://pmd.sf.net/ruleset/1.0.0
                     http://pmd.sf.net/ruleset_xml_schema.xsd"
         xsi:noNamespaceSchemaLocation="
                     http://pmd.sf.net/ruleset_xml_schema.xsd">
    <description>
        My custom rule set that checks my code...
    </description>

    <!-- Import the entire unused code rule set -->
    <rule ref="rulesets/unusedcode.xml" />

    <!--
        Import the entire cyclomatic complexity rule and
        customize the rule configuration.
    -->
    <rule ref="rulesets/codesize.xml/CyclomaticComplexity">
        <priority>1</priority>
        <properties>
            <property name="reportLevel" value="5" />
        </properties>
    </rule>

    <!-- Import entire naming rule set and exclude rules -->
    <rule ref="rulesets/naming.xml">
        <exclude name="ShortVariable" />
        <exclude name="LongVariable" />
    </rule>
</ruleset>

Conclusion

With PHPMD's rule set syntax it is possible to customize all aspects of rules for your own needs and you can reuse every existing rule set xml file in your own set. You should take a look at PHPMD's rule documentation if it happens that you don't know what rules exist or you don't know exactly, which settings are available for one rule, while you create your own set of rules. Another good source of information are the rule set files that are shipped with PHPMD.

You can get the latest PHPMD version from its PEAR channel: pear.phpmd.org

mapi@arwen ~ $ pear channel-discover pear.pdepend.org
mapi@arwen ~ $ pear channel-discover pear.phpmd.org
mapi@arwen ~ $ pear install --alldeps phpmd/PHP_PMD-alpha

Or from our github repository:

mapi@arwen ~ $ git clone git://github.com/manuelpichler/phpmd.git

I would be glad if you file a ticket in PHPMD's issue tracker for all issues and/or enhancements you encounter while testing PHPMD.

PHPMD 0.2.3 released with @SuppressWarnings support and new rule set.

nospam@example.com (Manuel Pichler) — Thu, 04 Mar 2010 10:32:00 +0100

We are proud to announce the 0.2.3 release of the PHP Mess Detector, a tool that takes source code and performs various tests to calculate various quality aspects from it. The measured values are a good starting point for future improvements. This release contains some new features, for example support for the @SuppressWarnings annotation, that allows you to exclude single methods or complete classes from PHPMD's analyzing process. This annotation can be used to suppress a single rule, a group of rules or PHPMD at all.

/**
 * Suppress all PHPMD warnings for this class.
 *
 * @SuppressWarnings(PHPMD)
 */
class PHPMD_SuppressAll 
{
}

class  PHPMD_SuppressOnMethod
{
    /**
     * Do not warn about the unused parameter $bar.
     *
     * @SuppressWarnings(PHPMD.UnusedFormatParameter)
     */
    public function foo($bar)
    {
    }
}

Beside several bugfixes this release comes with a new set of rules that check the naming of methods, variables etc. against common coding conventions and best practices.

Fixed #6: PHP Tokenizer required but no error when installing.
Fixed #7: UnusedLocalVariable ruleset incorrectly flags variables as unused when used inside double quoted string. Fixed in svn revision #187.
Implemented #9: Add support for "Suppress warnings" annotations. Implemented in svn revision #200.
Implemented #10: Support for exclude element in rule-set files added. Implemented in svn revision #189.
Implemented #13: Implement naming rules, e.g. short variables, parameter etc.
Fixed #14: ExcessivePublicCount rule should utilize PHP_Depend's cis metric. Fixed in svn revision #203.
Fixed #15: ExcessivePublicCount rule is never used. Fixed in svn revision #202.

You can get the latest PHPMD version from its PEAR channel: pear.phpmd.org

mapi@arwen ~ $ pear channel-discover pear.pdepend.org
mapi@arwen ~ $ pear channel-discover pear.phpmd.org
mapi@arwen ~ $ pear install --alldeps phpmd/PHP_PMD-alpha

Or from our github repository:

mapi@arwen ~ $ git clone git://github.com/manuelpichler/phpmd.git

PHP_Depend-0.9.11 released

nospam@example.com (Manuel Pichler) — Tue, 02 Mar 2010 21:08:03 +0100

I have just released version 0.9.11 of PHP_Depend. It contains a few bug fixes and improvements for PHP_Depend.

Fixed #118: Calculation of the Number Of Overwritten Methods is wrong. Fixed in svn revision #1112.
Fixed #119: Three test cases fail for all PHP versions prior to 5.3. Fixed in svn revision #1114.
Implemented #121: Parse arguments of the ASTForeachStatement. Implemented in svn revision #1115.
Critical issue in PHP_Depend's temporary data cache fixed. This bug only occured when running several instances of PHP_Depend in parallel. In this setup the used cache key spl_object_hash() has caused a corrupted cache, because different php process instances have written different data to the same cache file.

As always, you can get the latest PHP_Depend version from its PEAR channel: pear.pdepend.org:

  mapi@arwen ~ $ pear channel-discover pear.pdepend.org
  mapi@arwen ~ $ pear install pdepend/PHP_Depend-beta

Or you can fetch the sources from the subversion reposition:

  mapi@arwen ~ $ svn co http://svn.pdepend.org/branches/0.9.0/

And additionally you can find a repository mirror on github:

  mapi@arwen ~ $ git clone git://github.com/manuelpichler/pdepend.git

PHP_Depend-0.9.10 released

nospam@example.com (Manuel Pichler) — Tue, 23 Feb 2010 20:36:01 +0100

I have just released the bug fix version 0.9.10 of PHP_Depend. This release contains several bug fixes and improvements for PHP_Depend.

Implemented #72__: Add NOAM, NOOM and NOCC metrics. Implemented in svn revision #1084.
Implemented #74: Make CRAP-index available. Implemented in svn revision #1063.
Implemented #105: Support for deep search implement. Implemented in svn revision #1078.
Fixed #106: Filter algorithm is broken for namespaced internal classes. Fixed in svn revision #1039.
Fixed #110: Duplicate "coupling" directory in test code. Fixed in svn revision #1032.
Fixed #111: Dynamic Strings are treated as literal strings. Fixed in svn revision #1037.
Fixed #114: Parsing error caused by complex string expressions fixed. Fixed in svn revision #1068.
Fixed #115: Summary and PHPUnit Report lists unknown classes. Fixed in svn revision #1101.
Fixed #116: Returns reference results in parsing error. Fixed in svn revision #1090.
Performance intensive calculation result cached.
Test code restructured and improved.
Concurrency issue for parallel running pdepend instances fixed.

As always, you can get the latest PHP_Depend version from its PEAR channel: pear.pdepend.org:

  mapi@arwen ~ $ pear channel-discover pear.pdepend.org
  mapi@arwen ~ $ pear install pdepend/PHP_Depend-beta

Or you can fetch the sources from the subversion reposition:

  mapi@arwen ~ $ svn co http://svn.pdepend.org/branches/0.9.0/

And additionally you can find a repository mirror on github:

  mapi@arwen ~ $ git clone git://github.com/manuelpichler/pdepend.git

Manuel Pichler - projects

PHPMD 1.1.0 released

Features

Bugfixes

Download

A brief introduction to the Coupling Between Objects metric

Thresholds

See also

Bibliography

PHP_Depend 0.10.2 released

Brief introduction to the Class Interface Size metric

Thresholds

Bibliography

PHP_Depend 0.9.16 bugfix release

phpUnderControl 0.6.0beta2 released

Artikel zum Thema Softwaremetriken

PHP-Magazin Artikel zum Thema Softwaremetriken

PHP_Depend 0.9.13 bugfix release

Goodbye Cologne

PHP_Depend 0.9.12 release

Howto create custom rule sets for PHPMD

Starting with an empty ruleset.xml file

Adding rule references to the new ruleset.xml file

Excluding rules from a rule set

Conclusion

PHPMD 0.2.3 released with @SuppressWarnings support and new rule set.

PHP_Depend-0.9.11 released

PHP_Depend-0.9.10 released