Modify

Ticket #514 (closed defect: invalid)

Opened 19 months ago

Last modified 18 months ago

phpCpd does not support haltonerror attribute

Reported by: max.romanovsky@… Owned by: victor
Priority: minor Milestone: 2.4.3
Component: phing-tasks-ext Version: 2.4.1
Keywords: phpcpd Cc:

Description

When haltonerror attribute is defined

<phpcpd haltonerror="true">...</phpcpd>

phing reports an error:

Execution of target "phpcpd" failed for the following reason: path/to/build.xml:21:22: phing.tasks.ext.phpcpd.PHPCPDTask doesn't support the 'haltonerror' attribute.

BUILD FAILED
/path/to/build.xml:21:22: phing.tasks.ext.phpcpd.PHPCPDTask doesn't support the 'haltonerror' attribute.

Attachments

Change History

comment:1 Changed 18 months ago by victor

  • Owner changed from mrook to victor
  • Status changed from new to assigned

I am not sure if I got the request correctly since nor phpcpd, nor PHPCPDTask has the haltonerror option.

Here is "phpcpd -v" output:

phpcpd 1.3.1 by Sebastian Bergmann.

Usage: phpcpd [switches] <directory|file> ...

  --log-pmd <file>         Write report in PMD-CPD XML format to file.

  --min-lines <N>          Minimum number of identical lines (default: 5).
  --min-tokens <N>         Minimum number of identical tokens (default: 70).

  --exclude <directory>    Exclude <directory> from code analysis.
  --suffixes <suffix,...>  A comma-separated list of file suffixes to check.

  --help                   Prints this usage information.
  --version                Prints the version and exits.

  --verbose                Print progress bar.

Checking the  documentation - no mention of haltonerror.

So, imo, it's definitely not a new defect as marked by original reporter.

Marked as "invalid" until ticket is clarified.

comment:2 Changed 18 months ago by victor

  • Status changed from assigned to closed
  • Resolution set to invalid
View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.