[jira] Created: (MAVEN-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "

[ji...@codehaus.org]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-489


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-489
    Summary: Checkstyle Error - "Got an exception - java.lang.ClassCastException "
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
 Components: 
             plugin-other
   Versions:
             1.0-beta-10

   Assignee: 
   Reporter: Nick Minutello

    Created: Sat, 14 Jun 2003 6:05 AM
    Updated: Sat, 14 Jun 2003 6:05 AM
Environment: JDK1.4.1_01 on Win2K

Description:

I have the latest HEAD build of Maven (built late 13th June GMT) and I am seeing this error 100s of times over in the checkstyle report.


Error                                                 Line  
Got an exception - java.lang.ClassCastException       0  


Mailing list conversations:

On Fri, Jun 13, 2003 at 04:40:44PM +0800, Willie Vu wrote:
>> > Vincent,
>> >
>> > After I changed antlr plugin to use 2.7.2, I run into this problem:
>> >
>> > XXX.java: 0: Got an exception - java.lang.ClassCastException
>> >
>> > What is the problem?
>> >
>> > Willie
>> >
>> >
>> I think, I've ran into the same problem - and nothing to do with
>> the new checkstyle jar in my case. You cab check this by looking at
>> the checkstyle reports in target - they are all right at me.
>> 
>> The problem is that in my project.xml I'm using the
>> 
>> <sourceDirectory>${basedir}/src/java</sourceDirectory>
>> 
>> convention, and in the checkstyle jsl, that formats the raw checkstyle
>> report expects the sourceDirectory as a ${baseDir} relative value (line 56):
>> 
>> <j:set var="fullSrcDir" value="${basedir}/${pom.build.sourceDirectory}"/>

>> And the whole jsl processing is went wrog from this, as the  transformer
>> would be working with a ${basedir}/ ${basedir}/<basedir_relative_filename>
>> from here. Sometimes it causes exception, sometimes simply wrong.
>> 
>> A dirty/quick cure to modify project.xml not to use ${basedir} (altough
>> if you use reactor you may get troubles with that). I'm thinking how to
>> patch the jsl script, just wrote this, maybe more knowledgeable jelliers
>> are faster at fix than I am.
>> 
>> incze


However, my Project.xml uses relative "src/java" and I still have the same problem.




---------------------------------------------------------------------
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/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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org