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

[Fred Bricon (JIRA)]

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

Fred Bricon commented on JBIDE-13848:
-------------------------------------

OK I found the reference to the JDT UI bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=360642. In that regard, PR looks good to me.

{quote}
I will add a better solution: if a source attachment file doesn't exist, the Source Lookup will try to find a new file.
{quote}
I don't understand. You're describing the source lookup principle :-)

{quote}
This feature isn't related to JBIDE-13852.
{quote}
Can you please open a new JIRA for that, so you can reference subsequent fixes?

I agree with the fact users will prefer having the source code than not, my point was more about having .classpath getting non-portable changes behind the user's back (m2e uses a classpath container so it's not the same thing).
M2_REPO will stay there as long as m2e-wtp needs it, don't worry (EARs can't use classpath containers) :-)
                
> 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