Do plug-ins no longer need to bundle commons-*.jar files?

Is there a change between 103.* and 106.* that means plug-ins no longer
need to bundle jars like commons-httpclient, commons-codec and commons-
logging?

I'm seeing exceptions testing a plug-in against 106.273 but not against
103.212.

If I remove the commons-*.jar files from the plug-in's lib directory then
the exceptions disappear and the plug-in works once more.

Looking at the plug-ins bundled with IDEA I can see that they no longer
provide their own copies of those jars.  I assume plug-is now have access
to the corresponding jars in IDEA's own lib directory?

--
Mark Scott
mark@codebrewer.com

2 comments
Comment actions Permalink

On Sat, 26 Mar 2011 17:23:35 +0000, Mark Scott wrote:

Oops, wrong newsgroup.  Sorry.

--
Mark Scott
mark@codebrewer.com

0
Comment actions Permalink

Hello Mark,

Yes, there is such a change. For commons-httpclient and commons-codec, you
can either continue bundling your own version or use the one shipped with
IntelliJ. For commons-logging, you must remove the version you were bundling,
because otherwise commons-logging complains.

Is there a change between 103.* and 106.* that means plug-ins no
longer need to bundle jars like commons-httpclient, commons-codec and
commons- logging?

I'm seeing exceptions testing a plug-in against 106.273 but not
against 103.212.

If I remove the commons-*.jar files from the plug-in's lib directory
then the exceptions disappear and the plug-in works once more.

Looking at the plug-ins bundled with IDEA I can see that they no
longer provide their own copies of those jars.  I assume plug-is now
have access to the corresponding jars in IDEA's own lib directory?


--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Please sign in to leave a comment.