JavaDoc Editor plugin problem

I installed the JavaDoc Editor plugin but unable to see its properties in Settings. Even I can not get into keymapping screen after installing this plugin. If I uninstall it, it let me see the keymapping.
Default key for JavaDoc editor plugin is F11. I removed the existing mapping of F11 to make sure there is no conflict left, but still same result. I uninstalled the plugin and installed (copy) the the JavaDoc editor plugin I was using with IDEA 3.05 but still same result.

7 comments
Comment actions Permalink

Here is the exception I see in the idea.log

IDEA-Config - writeExternal(Element element)
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager -
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager - IntelliJ IDEA 4.0 Build #1165
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager - JDK: 1.4.2_03
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager - VM: Java HotSpot(TM) Client VM
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager - Vendor: Sun Microsystems Inc.
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager - OS: Windows 2000
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager - Last Action: EditorCopy
2004-03-26 15:48:52,476 ERROR - ij.components.ComponentManager -
java.lang.NoClassDefFoundError: com/intellij/openapi/util/JDOMExternalizableList
at com.jzox.idea.javadoc.JDSettings.]]>(JDSettings.java:56)
at com.jzox.idea.javadoc.JDPlugin.getSettings(JDPlugin.java:42)
at com.jzox.idea.javadoc.JDPlugin.writeExternal(JDPlugin.java:143)
at com.intellij.openapi.components.b.a.a(a.java:92)
at com.intellij.openapi.application.a.b.f(b.java:200)
at com.intellij.openapi.application.a.b.saveSettings(b.java:105)
at com.intellij.ide.bh.c(bh.java:38)
at com.intellij.ide.bh.access$300(bh.java:57)
at com.intellij.ide.bh$2.run(bh$2.java:1)
at com.intellij.util.Alarm$1.run(Alarm.java:1)
at com.intellij.util.Alarm$2.run(Alarm.java:4)
at com.intellij.openapi.application.LaterInvocator$FlushQueue.run(LaterInvocator.java:15)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
at com.intellij.ide.q.b(q.java:0)
at com.intellij.ide.q.a(q.java:85)
at com.intellij.ide.q.dispatchEvent(q.java:24)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
2004-03-26 15:50:03,217 INFO - fs.impl.VirtualFileManagerImpl - refresh(), modalityState=ModalityState.NON_MODAL
2004-03-26 15:50:03,227 INFO - impl.local.LocalFileSystemImpl - adding request to synchronize queue:com.intellij.openapi.vfs.a.b.g$4@10f7276
2004-03-26 15:50:03,227 INFO - impl.local.LocalFileSystemImpl - Executing request:com.intellij.openapi.vfs.a.b.g$4@10f7276
2004-03-26 15:50:03,267 INFO - fs.impl.VirtualFileManagerImpl - beforeRefreshStart()
2004-03-26 15:50:03,287 INFO - fs.impl.VirtualFileManagerImpl - afterRefreshFinish()
2004-03-26 16:00:03,921 INFO -

0
Comment actions Permalink

I don't think that plugin has been updated since 3.0. Probably doesn't work
with 4.0

"Ghazenfer Mansoor" <gmansoor@defywire.com> wrote in message
news:16110983.1080678151708.JavaMail.itn@is.intellij.net...

I installed the JavaDoc Editor plugin but unable to see its properties in

Settings. Even I can not get into keymapping screen after installing this
plugin. If I uninstall it, it let me see the keymapping.

Default key for JavaDoc editor plugin is F11. I removed the existing

mapping of F11 to make sure there is no conflict left, but still same
result. I uninstalled the plugin and installed (copy) the the JavaDoc editor
plugin I was using with IDEA 3.05 but still same result.
>
>


0
Comment actions Permalink

as per version tag in plugin.xml in the jar; it should work.
<idea-version min="3.0" max="4.0" />

0
Comment actions Permalink

Yes, but the last time it was updated in plugin manager was October. Well
before 4.0 was released.

"Ghazenfer Mansoor" <gmansoor@defywire.com> wrote in message
news:11552694.1080686892376.JavaMail.itn@is.intellij.net...

as per version tag in plugin.xml in the jar; it should work.
<idea-version min="3.0" max="4.0" />



0
Comment actions Permalink

On Tue, 30 Mar 2004 20:31:13 +0000, Ghazenfer Mansoor wrote:

ij.components.ComponentManager - java.lang.NoClassDefFoundError:
com/intellij/openapi/util/JDOMExternalizableList
at com.jzox.idea.javadoc.JDSettings.<init>(JDSettings.java:56) at
com.jzox.idea.javadoc.JDPlugin.getSettings(JDPlugin.java:42) at


This is the same problem I had within the JIRA plugin.

I ended up unjarring, and rejaring just the xpath classes I needed and
included that in my plugin lib directory. Its a nasty hack, but it worked.


--
Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live.

Mark Derricutt --- mark@ talios.com --- http://www.talios.com

0
Comment actions Permalink

If the author didn't know what the future version numbers would be, how
should they have specified in the xml file that it should only work in 3.x?
Should they list the current version at the time the plugin was built as the
max and assume that it will be broken in the next build?

What are new 4.x plugins saying is the max version number? I think that
most are saying 4.1 but that version isn't out yet, so how do they know if
their plugin will work there?

I don't think that the developer is the best person to specify the max
version number. Maybe the max version number for all plugins should be
automatically updated when there is a new IDEA build released and then
rolled back when the first bug is reported (or auto-uninstalled after an
exception).


"Brad" <none@nowhere.org> wrote in message
news:c4cu2p$93s$1@is.intellij.net...

Yes, but the last time it was updated in plugin manager was October. Well
before 4.0 was released.

>

"Ghazenfer Mansoor" <gmansoor@defywire.com> wrote in message
news:11552694.1080686892376.JavaMail.itn@is.intellij.net...

as per version tag in plugin.xml in the jar; it should work.
<idea-version min="3.0" max="4.0" />

>
>


0
Comment actions Permalink

I agree mostly. The max version should be the newest version the plugin has
been tested with. I think you should be able to assume the plugin will work
with all previous versions of the same major build. That is, if you've
tested on 4.0.2 then I would assume it would work on 4.0.1. That's what I do
anyway.

"Tim Haley" <ymaraner@yahoo.com> wrote in message
news:c4ekb3$pp7$1@is.intellij.net...

If the author didn't know what the future version numbers would be, how
should they have specified in the xml file that it should only work in

3.x?

Should they list the current version at the time the plugin was built as

the

max and assume that it will be broken in the next build?

>

What are new 4.x plugins saying is the max version number? I think that
most are saying 4.1 but that version isn't out yet, so how do they know if
their plugin will work there?

>

I don't think that the developer is the best person to specify the max
version number. Maybe the max version number for all plugins should be
automatically updated when there is a new IDEA build released and then
rolled back when the first bug is reported (or auto-uninstalled after an
exception).

>
>

"Brad" <none@nowhere.org> wrote in message
news:c4cu2p$93s$1@is.intellij.net...

Yes, but the last time it was updated in plugin manager was October.

Well

before 4.0 was released.

>

"Ghazenfer Mansoor" <gmansoor@defywire.com> wrote in message
news:11552694.1080686892376.JavaMail.itn@is.intellij.net...

as per version tag in plugin.xml in the jar; it should work.
<idea-version min="3.0" max="4.0" />

>
>

>
>


0

Please sign in to leave a comment.