[ http://jira.codehaus.org/browse/MPCHECKSTYLE-20?page=comments#action_72056 ] David Hittner commented on MPCHECKSTYLE-20: -------------------------------------------
In my experience, this happens fairly constantly using Eclipse 3.1.1 with eclipse-cs plugin 4.0.93. It ONLY happens when the class method has a throws clause that throws MULTIPLE exception types, and a custom exception is one (or more) of the thrown exceptions. A throws clause with a single custom exception works properly. A quick-and-dirty workaround (as has been noted) is to reduce the throws clause to a single thrown exception type, but this not necessarily a desirable 'fix', as it reduces the catchable granularity with the same JavaDoc impact. Lukas, is this enough information to reproduce the problem, or do you still need a test project? > Unable to get class information for custom exceptions > ----------------------------------------------------- > > Key: MPCHECKSTYLE-20 > URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-20 > Project: maven-checkstyle-plugin > Issue Type: Bug > Affects Versions: 2.3 > Environment: maven-1.0-rc2 > Reporter: Ryan Sonnek > > checkstyle reports an error "Unable to get class information" for custom > exceptions within the same project. it is able to load exceptions that are > listed as dependencies for the project, but not for other exceptions. one > workaround is to only use throws Exception in the signiture, but that's > really a hack. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
