Issue 329 in glassdb: unload package on empty package doesn't do the job

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Issue 329 in glassdb: unload package on empty package doesn't do the job

glassdb
Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-GLASS0.231  
bugid-39799

New issue 329 by [hidden email]: unload package on empty package  
doesn't do the job
http://code.google.com/p/glassdb/issues/detail?id=329

a golden oldy from Norbert:

at the moment I'm refactoring much. I move classes between
packages, defining new ones,....

If a package is empty it disappears from the Browser. But the
the PackageInfo is still there. Is this like it is intended?
I removed the obsolete ones manually. Is this necessary? I
mean the packages even overcome the "unload package" done with
Monticello.