[
https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808009#comment-13808009
]
Stefan Egli edited comment on SLING-3162 at 10/29/13 2:13 PM:
--------------------------------------------------------------
[~justinedelson], I have double-checked. The Package Explorer is not intended
to be extended - ie there is no extension API for the package explorer to hook
in the content browser. There might be dubious ways of hacking this in there,
but I think we should rather not go there. Hence I think we have to live
without the content browser in the package explorer..
was (Author: egli):
[~justinedelson], I have double-checked. The Package Explorer is not intended
to be extended - ie there is not extension API for the package explorer to hook
in the content browser. There might be dubious ways of hacking this in there,
but I think we should rather not go there. Hence I think we have to live
without the content browser in the package explorer..
> Sling virtual resource tree only appears in the Project Explorer, not the
> Package Explorer
> ------------------------------------------------------------------------------------------
>
> Key: SLING-3162
> URL: https://issues.apache.org/jira/browse/SLING-3162
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Justin Edelson
> Priority: Minor
>
> In the Java EE perspective, the default navigator view is the Project
> Explorer. In the Java perspective, it is the Package Explorer. Personally, I
> never use the Java EE perspective (and thus the Project Explorer) because
> Sling != JavaEE :)
> It seems to be OK if I just remove the Package Explorer view from the Java
> perspective and add the Project Explorer. But IMHO, this isn't intuitive.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
