I have a Web project that depends on the jar file of an EJB project, on Eclipse. When I alter this EJB project and rebuild it's client jar file, I have to remove the jar file from the Build Path of the Web project, and add it back, so that the changes are visible to the Web project.
Is there a faster way for these changes to be visible?
Cleaning the webproject doesn't refresh the changes made to the jars, but adding the ejb project to the Build Path instead of the jar file does.
Joined: Sep 03, 2004
Hello everyone, again.
I've noticed that if I use the Java perspective instead of the Java EE perspective, I get an extra node under my Web Project called Referenced Libraries, where all the jars referenced by the project is included, and if I refresh that node, hurray, the jars are refreshed. Or even if I refresh the entire Web Project the referenced jars are refreshed.
I think that's the folder Cristophe was talking about.
I thought I should share this here since you guys were so helpful.
I still wonder though why that doesn't happen when using the Java EE perspective.
subject: Eclipse - Jar file doesn't refresh automatically in build path