Closed GoogleCodeExporter closed 8 years ago
Forgot to mention, specifying the interpreter manually within the Phing PHPLint
task
will resolve this, however, that seems like a work-around and not a fix, as it
makes
the Phing build scripts less portable and as previously mentioned, the PHPLint
task
works fine when run manually via phing.
Original comment by FarSide...@gmail.com
on 23 Apr 2009 at 8:34
Original comment by apshoema...@gmail.com
on 25 Apr 2009 at 4:40
FarSide: Can you post your build.xml please?
Original comment by opitz.al...@googlemail.com
on 20 Aug 2011 at 10:35
Original comment by opitz.al...@googlemail.com
on 1 Oct 2011 at 11:16
No response and I have no problem with phplint and phing
Original comment by opitz.al...@googlemail.com
on 7 Aug 2013 at 10:22
Using a fresh install of Xinc 2.2 and Phing 2.5.0 then modifying the default
SimpleProject's build.xml to utilize phplint results in the error, "sh: phing:
command not found". The modified build.xml is attached. Environment is CentOS
5.6 and PHP 5.3.2.
Original comment by adam.j.s...@gmail.com
on 7 Aug 2013 at 2:26
Attachments:
Ugh, ignore that previous comment. Should have had my coffee before leaving a
comment this morning. That problem was because I did not specify the phing
path in Xinc's ini Configuration. The original issue reported regarding the
error "sh: php: command not found" does not appear to be an issue with xinc 2.2.
Original comment by adam.j.s...@gmail.com
on 7 Aug 2013 at 2:50
Original issue reported on code.google.com by
FarSide...@gmail.com
on 21 Apr 2009 at 3:21