This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
the problem in that link is the same as this problem. but i dont think its a threading problem like I stated in the link forum thread...
I have a problem with a JFace application.
I have some jars in different eclipse plug-in projects. and i can access those jars by manipulating the manifest. I can also run code compiled in those jars from other plug-in projects. But NOT when i try to run code inside a jar from the User Interface.
so basically: I can run code from JUnit tests and from main methods. but when I run my application and the GUI shows up, the classes in my jar cannot be found. the manifest is updated: so all may jars are referenced to in the manifest
I hope you understand my problem. kinda hard to explain
Maneesh Godbole wrote:You mention a manifest. Is this the typical manifest.mf file?
Have you made a self executable jar of your application and trying to run that?
Have you packaged the external jars inside your jar?
1: yes, this is the MANIFEST.MF file
2: yes and no: I have a 'product configuration file' that I am running. I have not yet created an executable from it. I run it directly from eclipse as an 'Eclipse Application'
3: the external jars are added to the classpath of my Manifest. and all 'exported packages(in manifest)' from the jar are also added in the manifest
it seems that the UI cant 'see' the jars, but my code can. It works when I call the same code in a main method, but not when i run it from the 'product configuration file'. so I think some jars are invisible for the UI..