Bug 78824 - [jars] Jar files in the plugin directory cannot be overwritten
Summary: [jars] Jar files in the plugin directory cannot be overwritten
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2004-11-17 06:05 EST by Peter Kriens CLA
Modified: 2007-03-27 16:24 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Kriens CLA 2004-11-17 06:05:43 EST 
JAR files that are placed in the plugin directory are kept open by Eclipse. 
This makes it impossible to overwrite the JAR file with a new version.
(BTW, nice that JAR files are picked up as well, much nice to deploy)
Comment 1 Pascal Rapicault CLA 2004-11-17 09:22:37 EST 
Why would you be willing to replace them while the system is running?
Comment 2 Jeff McAffer CLA 2004-11-17 10:02:05 EST 
This is strange.  If the plugin is a jar and the plugin is running then the jar 
is open as classes are being loaded.  Perhaps if the plugin was somehow not 
activated then the jar should be closed.
Comment 3 Pascal Rapicault CLA 2005-03-16 09:48:17 EST 
We should understand what is going on here as it may reveal some problems /
performance issues in the way we deal with jars.
Comment 4 Thomas Watson CLA 2005-03-24 10:50:57 EST 
This is somewhat related to bug 88915.  The framework was not properly closing 
bundles jars when they were uninstalled or when the framework was being 
shutdown.

But I'm still not sure I understand the scenario here, or how we could support 
it.  The suggestion is that we should be able to replace binaries of bundles 
which the system is currently running from.  We currently lazily open the jars 
on demand (when a class or resource is requested from the bundle).  But once 
the jar is open for use there is no way you will be able to replace it.  We 
are considering adding a timeout to the amount of time we keep jars open but 
this will still not give you the ability to replace the file until the timeout 
has been reached.  Either way I don't see us doing anything for this in M6.
Comment 5 John Arthorne CLA 2005-03-31 10:11:31 EST 
Slipping milestone.
Comment 6 Pascal Rapicault CLA 2005-05-05 15:51:29 EDT 
removing milestone
Comment 7 DJ Houghton CLA 2007-03-27 16:23:46 EDT 
Re-assigning to proper component...
Comment 8 DJ Houghton CLA 2007-03-27 16:24:58 EDT 
... and closing. Its been over 2 years since the bug was opened and we still haven't defined a proper use case for this.