You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Olivier Dehon <od...@gmail.com> on 2010/02/14 15:19:53 UTC

Checkstyle plugin 2.5 - Wrong exception reported?

Hello,

With the recent release of Checkstyle plugin 2.5, which uses Checkstyle
5.0, the format of the xml config file is not backwards compatible.

I struggled for a bit trying to understand why the checkstyle plugin
reported a "Could not find resource:
http://mycompany.com/templates/my-checkstyle-rules.xml" error, where
that resource was actually browsable.

It so happens because the format of the file is not compliant with
Checkstyle 5.0 anymore, and using version 2.4 of the checkstyle plugin
finds the file loads it and produces the reports just fine.

It seems that the XML parsing exception reported from checkstyle 5.0 is
interpreted as a resource not found by the plugin and reported as such,
which is confusing.

Has anyone encountered the same behavior? I can build a "test case" and
raise a JIRA if that is the case...

Thanks, -Olivier



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Checkstyle plugin 2.5 - Wrong exception reported?

Posted by Olivier Dehon <od...@gmail.com>.
Yes exact same case, even though I was under the impression that if the
xml file was 5.0 compliant, then the http URL was loaded OK.

I'll have to reconfirm that when I get into the office.

-Olivier

On Sun, 2010-02-14 at 20:34 +0100, Olivier Lamy wrote:
> Hi,
> Same case as http://jira.codehaus.org/browse/MCHECKSTYLE-129 ?
> 
> 
> 2010/2/14 Olivier Dehon <od...@gmail.com>:
> > Hello,
> >
> > With the recent release of Checkstyle plugin 2.5, which uses Checkstyle
> > 5.0, the format of the xml config file is not backwards compatible.
> >
> > I struggled for a bit trying to understand why the checkstyle plugin
> > reported a "Could not find resource:
> > http://mycompany.com/templates/my-checkstyle-rules.xml" error, where
> > that resource was actually browsable.
> >
> > It so happens because the format of the file is not compliant with
> > Checkstyle 5.0 anymore, and using version 2.4 of the checkstyle plugin
> > finds the file loads it and produces the reports just fine.
> >
> > It seems that the XML parsing exception reported from checkstyle 5.0 is
> > interpreted as a resource not found by the plugin and reported as such,
> > which is confusing.
> >
> > Has anyone encountered the same behavior? I can build a "test case" and
> > raise a JIRA if that is the case...
> >
> > Thanks, -Olivier
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> 
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Checkstyle plugin 2.5 - Wrong exception reported?

Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Same case as http://jira.codehaus.org/browse/MCHECKSTYLE-129 ?


2010/2/14 Olivier Dehon <od...@gmail.com>:
> Hello,
>
> With the recent release of Checkstyle plugin 2.5, which uses Checkstyle
> 5.0, the format of the xml config file is not backwards compatible.
>
> I struggled for a bit trying to understand why the checkstyle plugin
> reported a "Could not find resource:
> http://mycompany.com/templates/my-checkstyle-rules.xml" error, where
> that resource was actually browsable.
>
> It so happens because the format of the file is not compliant with
> Checkstyle 5.0 anymore, and using version 2.4 of the checkstyle plugin
> finds the file loads it and produces the reports just fine.
>
> It seems that the XML parsing exception reported from checkstyle 5.0 is
> interpreted as a resource not found by the plugin and reported as such,
> which is confusing.
>
> Has anyone encountered the same behavior? I can build a "test case" and
> raise a JIRA if that is the case...
>
> Thanks, -Olivier
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>



-- 
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org