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.
When I debug my MIDlet the CLEAN target is always executed, this means that it is not possible to start 2 simultanous debug sessions for example to test BT communications between two MIDlets. I don't think it is correct behavior to always perform a CLEAN when debugging, when I want a clean build, there's an option that lets me do so. Now I have to dive into the rather complex ANT-scripts and ammend them, which is not a simple task. Iwan
it sounds as a valid use case. I've just checked it and on windows it is not possible to execute an application twice because execution locks the jar file and build process of the second execution fails.
Clean before debug is a fix of another annoying problem with debugging of obfuscated classes. You don't have to turn the obfuscation off before debugging but clean is explicitelly invoked. And if you build or run your application again - the clean is invoked again to build the application back as obfuscated. For your case there are four possible workarounds: 1. you already mentioned the modification of the debug target dependencies in build.xml 2. you can create two project configurations - they are built into a different folders so it workarounds any Windows file lock problems 3. you can debug first instance and then use Quick Run With... to execute the second instance of your application 4. use OTA execution mode BTW not all the emulators lock the .jar and .jad files during execution or debugging