2 comments
Comment actions Permalink

On Wed, 27 Apr 2005 16:22:33 +0200, Sascha Weinreuter wrote:

Element.addContent(Element) method as well as the new
Element.addContent(Content) one? This might solve a good number of the
problems we see.


Looks like in JDOM 1.0 Element extends Content, so a simple recompile
should suffice right? Well I'm confused, I've compiled my JIRA plugin
against the jdom.jar shipped with 3317, everythings fine, yet when I run
IDEA with the plugin installed, I get that famous stacktrace.

So now I'm hellishly confused...



At least that's what it looks like from this end.

I wonder how well setting up a cruise-control server for plug-ins would
be.... then when a new build comes out, all the plug-ins can be
configured and built from there...

Maybe a dedicated Intellij GForge server somewhere or something...


NOTE: As 1.4 is still supported, plugins should be compiled target=1.4 - I
wonder how long till we start hearing about class issues. Its the wrong
NG but maybe the plugin.xml needs to have a language-level specifier...

0
Comment actions Permalink

Mark Derricutt wrote:

On Wed, 27 Apr 2005 16:22:33 +0200, Sascha Weinreuter wrote:

>
>
>>Element.addContent(Element) method as well as the new
>>Element.addContent(Content) one? This might solve a good number of the
>>problems we see.
>
>

Looks like in JDOM 1.0 Element extends Content, so a simple recompile
should suffice right?


Right.

Well I'm confused, I've compiled my JIRA plugin
against the jdom.jar shipped with 3317, everythings fine, yet when I run
IDEA with the plugin installed, I get that famous stacktrace.


Did you recompile everything from scratch? The same happened to me when I forgot
to do an "ant clean" before rebuilding...

Sascha

0

Please sign in to leave a comment.