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 116230 - Make run-single, debug-single, and test-single depend on compile-single{,-test}
Summary: Make run-single, debug-single, and test-single depend on compile-single{,-test}
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL: http://www.netbeans.org/servlets/Brow...
Keywords: PERFORMANCE
: 116103 (view as bug list)
Depends on: 115918 174247
Blocks: 85707 97053
  Show dependency tree
 
Reported: 2007-09-21 00:05 UTC by Jesse Glick
Modified: 2009-10-20 23:46 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 Jesse Glick 2007-09-21 00:05:11 UTC
For performance reasons, desirable to make e.g. run-single depend on compile-single (as in previous releases), rather
than compile (as changed in issue #85707). To address the issue of recompilation, need to disable the <force-recompile>
macro in this case; to address the issue of dependent files (see issue #97053), need to use a real sourcepath (which
issue #115918 already did).
Comment 1 Jesse Glick 2007-09-26 19:00:36 UTC
*** Issue 116103 has been marked as a duplicate of this issue. ***
Comment 2 Jesse Glick 2007-09-27 19:39:45 UTC
Checking in test/unit/src/org/netbeans/modules/java/j2seproject/BuildImplTest.java;
/shared/data/ccvs/repository/java/j2seproject/test/unit/src/org/netbeans/modules/java/j2seproject/BuildImplTest.java,v 
<--  BuildImplTest.java
new revision: 1.17; previous revision: 1.16
done
Checking in test/unit/src/org/netbeans/modules/java/j2seproject/J2SEActionProviderTest.java;
/shared/data/ccvs/repository/java/j2seproject/test/unit/src/org/netbeans/modules/java/j2seproject/J2SEActionProviderTest.java,v
 <--  J2SEActionProviderTest.java
new revision: 1.19; previous revision: 1.18
done
Checking in src/org/netbeans/modules/java/j2seproject/J2SEActionProvider.java;
/shared/data/ccvs/repository/java/j2seproject/src/org/netbeans/modules/java/j2seproject/J2SEActionProvider.java,v  <-- 
J2SEActionProvider.java
new revision: 1.61; previous revision: 1.60
done
Checking in src/org/netbeans/modules/java/j2seproject/resources/build-impl.xsl;
/shared/data/ccvs/repository/java/j2seproject/src/org/netbeans/modules/java/j2seproject/resources/build-impl.xsl,v  <--
 build-impl.xsl
new revision: 1.101; previous revision: 1.100
done
Comment 3 wqtnetbeans 2007-10-10 03:34:59 UTC
I am afraid the current change still does not help in this simple/common scenario:

I have MyClassTest.java which is a JUnit test case of MyClass.java. What helps is that when I change MyClass.java (not
MyClassTest.java), and then test-single/run MyClassTest.java, the change in MyClass.java should be accounted for,
without re-compile of the entire project. But my understanding of the current change is that it won't work that way. Am
I right?

 
Comment 4 Jesse Glick 2007-10-10 13:59:25 UTC
Correct. Tests do not necessarily have a 1-to-1 correspondence with source files.