[ http://jira.codehaus.org/browse/MPCHECKSTYLE-20?page=comments#action_58453 ]
Jeff Jensen commented on MPCHECKSTYLE-20: ----------------------------------------- We still have this problem with plugin 2.5 and 3.0 (CS 3.5 and 4.0). Does anyone else still have this problem? Is there a known final fix for this (or is it the 2004 blog entry in the prior comment?)? In trying to find a common cause, so far have only found these coincidences or symptoms: 1) The cross reference report creates links to the exception classes that CS flags as unable to find. 2) The cross reference report does not create links to the exception classes that CS does not flag as not found. > Unable to get class information for custom exceptions > ----------------------------------------------------- > > Key: MPCHECKSTYLE-20 > URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-20 > Project: maven-checkstyle-plugin > Type: Bug > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
