The following comment has been added to this issue:
Author: Sean Gay
Created: Sun, 6 Feb 2005 6:30 PM
Body:
If the report is run after a clean the problem occurs, if the classes are
compiled in your target directory then checkstyle can find the custom class
information.
It may be a little hassle until a fix is completed to do this rather than the
post report generation goal mentioned in the previous comment.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPCHECKSTYLE-20?page=comments#action_29608
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPCHECKSTYLE-20
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPCHECKSTYLE-20
Summary: Unable to get class information for custom exceptions
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-checkstyle-plugin
Versions:
2.3
Assignee:
Reporter: Ryan Sonnek
Created: Sat, 27 Mar 2004 11:48 AM
Updated: Sun, 6 Feb 2005 6:30 PM
Environment: maven-1.0-rc2
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
