Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Fragment imposes restriction on host plugin, why?
Fragment imposes restriction on host plugin, why? [message #290632] Sun, 28 August 2005 19:28
Eclipse UserFriend
Originally posted by: petter.holmstrom.parnet.fi

Hello,

My RCP-application uses Commons Logging for almost all its logging. I have
installed a wrapper plugin from http://eplug.sf.net. However, I'd like to
use log4j as a backend, which means I have to make sure the log4j classes
are in the same classpath as the commons logging plugin. I've tried to do
this by creating a fragment of the commons logging plugin which simply adds
the log4j jar to its classpath and exports its libraries. During runtime,
everything works great. However, when this fragment is open, all plugins
that use the commons logging classes start to complain that the type
LogFactory is not accessible due to restriction on required
library /home/petter/JavaDevel/eclipse/plugins/org.apache.jakarta.
commons.logging_1.0.3/commons-logging.jar.

If I close my fragment project, export the plugins, then reopen it, export
it separatly and copy it manually into my RCP's plugin-directory,
everything works. My question is: Is this a bug, or am I doing something
wrong? I have not been able to find any information on the subject in
either the Eclipse documentation, or on Google.

Thanks in advance,

-Petter-

--
Get my public PGP key from http://www.keyserver.net

Help fight continental drift.
Previous Topic:eclipse links
Next Topic:Building Eclipse Plugins with Maven
Goto Forum:
  


Current Time: Fri Apr 19 22:17:07 GMT 2024

Powered by FUDForum. Page generated in 0.03002 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top