[
https://jira.codehaus.org/browse/MCOMPILER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286410#comment-286410
]
Kristian Rosenvold commented on MCOMPILER-142:
----------------------------------------------
Sorry, my bad. That should be properly credited now.
https://github.com/sonatype/plexus-compiler/commit/7d7e832dd72b97221280ffbf6f56e56edbb890e6
> classes complied by plexus-compiler-eclipse get 'source not found' problem in
> eclipse class file editor
> -------------------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-142
> URL: https://jira.codehaus.org/browse/MCOMPILER-142
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Reporter: Rice Yeh
> Assignee: Kristian Rosenvold
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
