This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 113285 - placing jar to windows temp folder and not clearing it after I close the application
Summary: placing jar to windows temp folder and not clearing it after I close the app...
Status: RESOLVED WORKSFORME
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-21 08:40 UTC by anandpritam
Modified: 2007-10-30 16:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description anandpritam 2007-08-21 08:40:33 UTC
Hi, 

 

I am using netbeans5.5 platform for launching my module. My problem is its placing my module jar to  windows temp 
folder and not clearing it after I close the application. Plz check my module config file.

<module name="com.viswa.reportSystem.report.client.template">

    <param name="autoload">false</param>

    <param name="eager">false</param>

    <param name="enabled">true</param>

    <param name="jar">modules/designer.jar</param>

    <param name="release">1</param>

    <param name="reloadable">true</param>

    <param name="specversion">1.0</param>

</module>

 

If i chnage reloadable attribute value to false. it's not caching it, but components in my module are coming in zig 
zag order.

 

plz suggest any other alternative to avoid copying the module file to %temp%????
Comment 1 Milos Kleint 2007-08-21 08:55:49 UTC
I assume you are developing netbeans modules? -> reassigning to apisupport
Comment 2 Jesse Glick 2007-08-21 16:41:05 UTC
What JARs in particular? Reloading modules (using --reload on the command line) will create /tmp/*-test.jar to avoid
file locking or race condition problems, especially on Windows. NetBeans calls File.deleteOnExit so they should be
deleted when the IDE is shut down normally.

I cannot diagnose further without detailed steps to reproduce.
Comment 3 Jesse Glick 2007-10-30 16:13:44 UTC
No further information, closing for now.