File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes IDEs, Version Control and other tools and the fly likes Eclipse User Library and Plugin Development Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Eclipse User Library and Plugin Development" Watch "Eclipse User Library and Plugin Development" New topic
Author

Eclipse User Library and Plugin Development

Rafael Angarita
Ranch Hand

Joined: Jan 09, 2009
Posts: 67
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.

Rafael Angarita.
SCJP 6.
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16019
    
  20

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.


Customer surveys are for companies who didn't pay proper attention to begin with.
 
 
subject: Eclipse User Library and Plugin Development