camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: Check Style MutableException check
Date Sun, 30 Jun 2013 21:02:12 GMT
Because we cannot rename the classes (part of the API) or delete the setter
methods (used by the unmarshaller), I went ahead and updated the Check
Style rule...

Best,
Christian
-----------------

Software Integration Specialist

Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Sun, Jun 30, 2013 at 6:02 PM, Christian Müller <
christian.mueller@gmail.com> wrote:

> Because of this check [1], the check style validation of the following
> classes fails:
> org/apache/camel/component/salesforce/api/dto/bulk/Error.java
> org/apache/camel/component/salesforce/api/dto/bulk/ResultError
> org/apache/camel/component/salesforce/internal/dto/LoginError
>
> If no body has objections, I will go ahead and change the reg exp from
> ^.*Exception$|^.*Error$
> to
> ^.*Exception$
>
> I'm also open for other solutions.
>
> [1] http://checkstyle.sourceforge.net/config_design.html#MutableException
>
> Best,
> Christian
> -----------------
>
> Software Integration Specialist
>
> Apache Camel committer: https://camel.apache.org/team
> V.P. Apache Camel: https://www.apache.org/foundation/
> Apache Member: https://www.apache.org/foundation/members.html
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message