Opened 16 years ago
Closed 16 years ago
#1043 closed defect (fixed)
JarClassLoader.getInstance() doesn't create a new class loader if a secondary JAR file has changed
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | minor | Milestone: | BASE 2.8 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
The documentation on the method says that a new class loader should be created if "the JAR file has changed ...". Currently this is only checked on the primary JAR file, not on secondary files listed in the Class-Path entry in the manifest file.
Change History (4)
comment:1 by , 16 years ago
| Status: | new → assigned |
|---|
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 by , 16 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
This fix broke #1041. When that ticket has been fixed again this ticket needs to be re-fixed.
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
(In [4390]) Fixes #1043: JarClassLoader.getInstance() doesn't create a new class loader if a secondary JAR file has changed
Note:
See TracTickets
for help on using tickets.
(In [4323]) Fixes #1043: JarClassLoader.getInstance() doesn't create a new class loader if a secondary JAR file has changed
And some issues with the extension api resulting from the change.