that's right, one solution that worked for me is to put all the path in the @throws tag : @throws org.my.exception , even if the exception is in the same package.

Stephane

STRAYER, JON (SBCSI) a �crit :

Well, I just realized that in my case it's having a problem when I have a
@throws tag for and exception I don't import (and don't use the full package
prefix).

-----Original Message-----
From: Ryan Sonnek [mailto:[EMAIL PROTECTED] Sent: Monday, April 26, 2004 12:11 PM
To: Maven Users List
Subject: RE: CheckStyle error:Unable to get class information for



i've had the same problem. i've filled an issue in jira (http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHECKSTYLE-20) regarding this problem and have also searched checkstyle's mailing lists to no avail. if anyone out there has a resolution, i have yet to find it.

Ryan


-----Original Message-----
From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED]
Sent: Monday, April 26, 2004 12:06 PM
To: Maven Users List
Subject: CheckStyle error:Unable to get class information for


I noticed some CheckStyle errors saying it couldn't get class information
for some of the exceptions we throw. I thought I could solve the problem by
adding the build path to the classpath Maven passes to CheckStyle, but it is
already there.


I'm out of ideas.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to