Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Eclipse User Library and Plugin Development

 
Rafael Angarita
Ranch Hand
Posts: 67
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello everybody,

I'm developing a plugin for Eclipse which uses several external libraries. This project is shared among 6 programmers using Subversion, therefore I want to make library paths absolutes. I started using the User Library of eclipse, which lets me add all the external libraries I need and keep the path relative. I worked fine because I only had this in the .classpath file:

<classpathentry kind="con" path="org.eclipse.jdt.USER_LIBRARY/LIB"/>


One of the libraries I'm placing in this User Library is mysql-connector. The problem comes when I try to configure the plugin dependencies in the Manifest file because I can't choose mysql-connector neither from the list of Required Plugins nor from Runtime libraries.

I could do that before because I had the mysql-connector jar in the plugins directory of Eclipse. I know I will run into this same problem with other libraries I will use in the future.

What should I do? Place mysql-connector in the Eclipse plugins folder? I would really like to keep everything well organized.

Thank you very much for your advise.
 
Tim Holloway
Saloon Keeper
Posts: 18302
56
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually, I recommend not using internal absolute paths, if for no other reason than it limits your OS options (Linux and Solaris take a dim view of "D:\libraries\drivers", for example). And because there's always the possibility that what you're doing may be so useful that some other group with a completely different set of standards will be unable to take advantage of your brilliance.

I exploit Eclipse's support of local symbolic assignments. So, for example, if a project needs to refer to the servlet.jar file of Tomcat, I define it as $TOMCAT_LIB/servlet.jar in the project build properties, which allows me to put Tomcat (and its library directory) anywhere I want and not tie other project users to my choice. Same applies to JDBC drivers and stuff like that.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic