LoadService always passes on fully-expanded paths when loading files, noising 
up backtraces, generated class names, and such
----------------------------------------------------------------------------------------------------------------------------

                 Key: JRUBY-2922
                 URL: http://jira.codehaus.org/browse/JRUBY-2922
             Project: JRuby
          Issue Type: Bug
          Components: Miscellaneous
    Affects Versions: JRuby 1.1.3
            Reporter: Charles Oliver Nutter
            Assignee: Charles Oliver Nutter
             Fix For: JRuby 1.1.4


Note the difference between these two traces:

Ruby:
{noformat}
./test2.rb:3: unhandled exception
        from test1.rb:2:in `require'
        from test1.rb:2
{noformat}

JRuby:
{noformat}
/Users/headius/NetBeansProjects/jruby/./test2.rb:3:in `(unknown)': unhandled 
exception
        from /Users/headius/NetBeansProjects/jruby/./test2.rb:2:in `require'
        from test1.rb:2:in `(unknown)'
{noformat}

LoadService is currently expanding paths to their full absolute path (and in 
some cases, to their canonical non-symlinked path) before passing the file off 
to be parsed and loaded. This is largely why backtraces, trace events, compiled 
package names, and so on have the full path. Tom Enebo fixed the parser in the 
last release to not use long paths, and it seems that currently the only 
remaining issue is in the load process.

We should correct this by feeding to the parser only the filename that Ruby 
users would expect to see (<load path entry>/<filename>) even if we use an 
expanded version to load the physical file.

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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to