Greetings Monks,
 Recently I have setup a subversion per-commit hook to check perl source code for certain coding standards, via Perl::Critic. One of the option is to check if the code has been run thru Perl::Tidy (Perl::Critic::Policy::CodeLayout::RequireTidyCode). Im using Perl::Critic thusly ... 

#internal method to get file content of this commit
my $content = read_file_content($file_name);
my @violations = critique({-profile => 'perlcritic.conf'}
, \$content);
    
# report violations
foreach my $crit (@violations){
    print STDERR "[$file_name] " . $crit->to_string . "\tsource: " . 
$crit->source . "\n";
}

[download]

and the perlcritic.conf: 
[CodeLayout::RequireTidyCode]
perltidyrc = /svn/hooks/perltidy.conf

[download]

and the perltidy.conf 
-bl     # braces on new lines
-l=80 #80 col width
-i=4  #4 char per indent
-ce    # cuddled else

[download]

and one of the test commits had the following code: 
....
if(1)
{
 print "1";
}
else
{
 print "2";
}
...

[download]
among other violations, such as unindented code and code crossing 80 columns etc.
I have read the perldocs and was sure this case would be reported as an violation, however it didn't. How do I configure the Perl::Critic's profile to report violations on code that fail Perl::Tidy ?
update: changed the title

In reply to Perl::Critic and Perl::Tidy by InfiniteLoop

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.