Ticket #207 (closed enhancement: fixed)

Opened 5 months ago

Last modified 2 months ago

PhpLintTask: optional use a different PHP interpreter

Reported by: Markus Fischer <markus@fischer.name> Assigned to: hans
Priority: trivial Milestone: 2.3.1
Component: phing-tasks-ext Version: 2.3.0
Keywords: phplint patch Cc:

Description

I'm using different PHP interpreters on my system and found the need to specify the <phplint> task which interpreter to use. I'm having interpreter with and without namespace, gc and scalar hinting patches and need to explicitly specify which one to use.

Although Phing itself can be run with a different interpreter easily, the PhpLintTask doesn't take advantage of so I included this also.

I added a new phing default property php.command which is set from the environment PHP_COMMAND.

PhpLintTask upon initialization defaults to the new property but can be overridden with the interpreter-Attribut.

Documentation is updated with the patch too.

Attachments

phing-lint-interpreter.diff (2.4 kB) - added by Markus Fischer <markus@fischer.name> on 01/01/08 12:59:55.
Add php.command property, have PhpLintTask take advantage of it and provide new interpreter attribute, updated docs.

Change History

01/01/08 12:59:55 changed by Markus Fischer <markus@fischer.name>

  • attachment phing-lint-interpreter.diff added.

Add php.command property, have PhpLintTask take advantage of it and provide new interpreter attribute, updated docs.

01/01/08 13:03:58 changed by Markus Fischer <markus@fischer.name>

I just realized I named the property php.command because the environment variable was named that way, actually I would prefer to also name the property php.interpreter because that is what it really is ...

01/21/08 14:50:01 changed by mrook

  • status changed from new to closed.
  • resolution set to fixed.

Patch committed in r342, thanks!

Add/Change #207 (PhpLintTask: optional use a different PHP interpreter)




Action