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 231401 - Build is 10x slower than Clean and Build due (?) to Jar Signing
Summary: Build is 10x slower than Clean and Build due (?) to Jar Signing
Status: VERIFIED FIXED
Alias: None
Product: javafx
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.4
Hardware: PC All
: P3 normal (vote)
Assignee: Petr Somol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-18 05:30 UTC by Lou Dasaro
Modified: 2013-09-26 09:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

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 Lou Dasaro 2013-06-18 05:30:53 UTC 
This occurs on a JavaFX project, and has been an ongoing problem.
In an edit code / debug scenario, I want to write some code, hit debug, and watch my code run. 

Unfortunately, clicking either the "Debug" or "Run" button causes a Build which include signing of numerous Jars for about a minute or so e.g. (one of many)
"Warning: 
The signer certificate will expire within six months.
Enter Passphrase for keystore: Enter key password for nb-jfx: 
Signing JAR: /NetBeansProjects/reKiosk/dist/lib/c3p0-0.9.1.jar to /NetBeansProjects/reKiosk/dist/lib/c3p0-0.9.1.jar as nb-jfx"

This goes on for about a minute while I twiddle my thumbs.

However, if I first click on "Clean and Build", the build completes in five seconds and only signs _my_ Jar, and then I can click the "Debug" or "Run" button and my code executes almost immediately.

This is the reverse of what I would expect.

This bug seems related to elements of Bug#212668
Comment 1 Lou Dasaro 2013-06-18 05:38:26 UTC 
Results are identical in Windows 7 or Linux.
Comment 2 Lou Dasaro 2013-07-22 04:12:30 UTC 
This anomaly not present in NetBeans IDE Dev (Build 201307192300).
Tested on both Enterprise Linux and Windows 7.
I would consider it fixed.