[
https://issues.apache.org/jira/browse/SLING-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580537#comment-14580537
]
Dan Klco commented on SLING-4792:
---------------------------------
Yep, I actually have it completed as a GitHub Pull Request here:
https://github.com/apache/sling/pull/94
You can see from the latest screenshot (attached to this issue), that by
default it displays the full file with syntax highlighting as well as links to
download the class, deps and java file.
BTW - is it possible to merge GitHub PR's into the Sling codebase? It seems
like I can't do it, but I'm wondering if there's a way to set this up. If not I
could create a patch and commit that into Subversion.
> FS ClassLoader Find .java File
> ------------------------------
>
> Key: SLING-4792
> URL: https://issues.apache.org/jira/browse/SLING-4792
> Project: Sling
> Issue Type: Improvement
> Affects Versions: File System ClassLoader 1.0.0
> Reporter: Dan Klco
> Assignee: Dan Klco
> Labels: features
> Fix For: File System ClassLoader 1.0.2
>
> Attachments: Screen Shot 2015-06-10 at 9.46.08 AM.png
>
>
> With SLING-4707, finding the .java files associated with a compiled script
> has been made more difficult as you need to find the ID of the FSClassLoader
> bundle, find the data directory for this bundle on the filesystem and find
> the associated files.
> I suggest we add a OSGi console for finding the associated .java files based
> on a script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
