[ANN] Lineage fixed for #3177
Q: What has changed?
A: Two things:
1. Lineage now works with IDEA #3177 (and should still work with IDEA #3144).
2. Some small cosmetic changes to the extension dialog.
3. Version number is now 0.5.4
Q: What is Lineage?
A: At this moment three things:
1. Extend Class intention
2. Extend Interface intention
3. Convert Inteface to Class intention
Please sign in to leave a comment.
Three! I hope my code is better...:-)
Bas
error in 3193:
java.lang.NoSuchMethodError:
com.intellij.psi.PsiClass.getUseScope()Lcom/intellij/psi/search/GlobalSearchScope;
at
net.intellij.plugins.lineage.ConvertInterfaceToClassFilter.isAccepted(ConvertInterfaceToClassFilter.java:32)
at
net.intellij.plugins.lineage.LineageIntention.findMatchingElement(LineageIntention.java:30)
at
net.intellij.plugins.lineage.LineageIntention.isAvailable(LineageIntention.java:60)
at
com.intellij.codeInsight.daemon.impl.ShowIntentionsPass.a(ShowIntentionsPass.java:77)
at
com.intellij.codeInsight.daemon.impl.ShowIntentionsPass.doApplyInformationToEditor(ShowIntentionsPass.java:124)
at
com.intellij.codeInsight.daemon.impl.TextEditorHighlightingPass.applyInformationToEditor(TextEditorHighlightingPass.java:1)
at com.intellij.codeInsight.daemon.impl.d$3.run(d$3.java:1)
at com.intellij.openapi.application.impl.c$b_.run(c$b_.java:16)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
at
com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:89)
at com.intellij.ide.IdeEventQueue.a(IdeEventQueue.java:80)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:158)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:178)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Thanks for reporting Alain. I hadn't even noticed there was a new build
until I saw your message. This problem is fixed in version 0.5.5,
available now.
Bas
Alain Ravet wrote: