• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Eclipse Plug-in and dependencies from other JARs

Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I am developing an Eclipse plug-in extending an existing one which comes from Eclipse.

Inside I code I have added I need log4j and other classes that are inside other JAR built by me (but this is not a plug-in).

Using the Manifest Editor inside Eclipse I have added these two JARs in "Classpath" inside the "Runtime" tab and if I test my plug-in from inside Eclipse using "Run as Eclipse Application" everything is ok.

Problem comes up when I try to export my plug-in because I get some "import can not be resolved" for classes that are inside one of my JAR.

To add these two JARs to my final JAR plug-in I edited the "Runtime Information" inside tab "Build".
In the Manifest.MF tab I can see these two JARs added with:

In fact during export the second JAR is included, but I get "import can not be resolved" inside a log file (created during export).

Why? How can I solve?

    Bookmark Topic Watch Topic
  • New Topic