[jbosstools-issues] [JBoss JIRA] (JBIDE-13848) Issue caused by changing editor ID for ClassFileEditor in Juno

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Fri Apr 12 13:19:55 EDT 2013


    [ https://issues.jboss.org/browse/JBIDE-13848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766851#comment-12766851 ] 

Snjezana Peco commented on JBIDE-13848:
---------------------------------------

{quote}
That said - Snjezana, this new feature has so many funky sideeffects and behaviors that both Fred and I are getting lost in this - could you document what this feature does, i.e. what parts are hardcoded, what part is changing users configuration files (i.e. classpath changes like here) and launch configurations for source lookup etc. 
{quote}

I have created a screencast showing this feature - http://screencast.com/t/iGFBsQYBOhtG.
Hoping it answers all your questions.

You can see what happens if a source attachment is empty, if it doesn't exist, if the preference is disabled...

You must include both of the PRs: https://github.com/jbosstools/jbosstools-central/pull/96 and https://github.com/jbosstools/jbosstools-central/pull/97 in order this to work.

After fixing JBIDE-13850 - Filtering libraries in Source Lookup plugin and JBIDE-13851 - Add source lookup classes to Java Search, we will be able to open a class from a JBoss AS using the standard Eclipse Navigate>Open Type (Ctrl+Shift+T) action.
                
> Issue caused by changing editor ID for ClassFileEditor in Juno
> --------------------------------------------------------------
>
>                 Key: JBIDE-13848
>                 URL: https://issues.jboss.org/browse/JBIDE-13848
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: maven
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Snjezana Peco
>            Assignee: Snjezana Peco
>         Attachments: test13848.zip
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list