Eclipse Auto Complete: Java 1.7 Generics Diamond -


I just advanced from Luna (Kepler) and I've seen some less (yet troubled) problems:
To begin auto completion diamond, there is the absence of the possibility of generating diamonds for the specified generic "lt;>" For example, when I type:

 set  & Lt; String & gt; MySet = new HashSet  

I hope this will auto-complete

 set  

String & gt; MySet = New Hashet & lt; & Gt; (); Instead of

  set  String & gt; MySet = New Hashet & lt; String & gt; ();  

I am using JDK 1.7 and the compliance level is also set at 1.7.

It is also very strange that when I hit STRG + space several times during auto-completion, until it reaches java-autocompletion again and then hits the hits, this expected diamond Saves you

It looks like a bug for me.
Is this bug "known" and there is no alternative solution for this issue? Nothing related to this topic could be found.

You get the most code recommended plug-in unfortunately this plug-in This effect is broken by which this functionality breaks.

This bug only appears if you have enabled type enabled enabled list in the "default" content ( eclipse Preferences> Java> Editor> Content Assist> Advanced ). For example, I can return the correct behavior by disabling the following proposal types:

  • Basic Proposal
  • JPA Proposal
  • Template Proposal
  • (If you are using code templates, most likely to be worried ...)

    When you use ctrl + < Kbd> space , you are actually reaching the " Java Proposal " (instead of " Intelligent Java Offer (Code Recommendations) "), which is this bug Prabha from Damage is not.

    This bug is scheduled in June 2015. The best you can is for this time:

    • Play with offers
    • Vote and to fix them;
    • Propose patch to fix those bugs: -)
    < / Div>

Comments

Popular posts from this blog

java - org.apache.http.ProtocolException: Target host is not specified -

java - Gradle dependencies: compile project by relative path -

ruby on rails - Object doesn't support #inspect when used with .include -