maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rice Yeh (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MCOMPILER-142) classes complied by plexus-compiler-eclipse get 'source not found' problem in eclipse class file editor
Date Mon, 06 Dec 2010 01:59:03 GMT
classes complied by plexus-compiler-eclipse get 'source not found' problem in eclipse class
file editor
-------------------------------------------------------------------------------------------------------

                 Key: MCOMPILER-142
                 URL: http://jira.codehaus.org/browse/MCOMPILER-142
             Project: Maven 2.x Compiler Plugin
          Issue Type: Bug
    Affects Versions: 2.3.2
            Reporter: Rice Yeh
            Priority: Critical


All classes complied by plexus-compiler-eclipse will get 'source not found' problem in eclipse
class file editor which is opened when you access the jar file containing the compiled classes
even though you have source jar associated with the jar file. A guy met the same problem as
mine, see http://www.mail-archive.com/users@maven.apache.org/msg80120.html. The following
is his observation on this problem: 

After having a look into the generated classes, I found that the debug 
information is different from the one I compiled with eclipse
jdt. For example,

Debug information from eclipse jdt compiler
Source File Name:   MyClass.java

Debug information from plexus-compiler-eclipse maven plugin
Source File Name:   com.mydomain.myproject.MyClass

This probable causes the problem.


Rice

-- 
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

        

Mime
View raw message