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 40794 - Compiler Target change does not show compiled in IDE when Target is not the same as the source
Summary: Compiler Target change does not show compiled in IDE when Target is not the s...
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
: 40438 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-03-05 13:05 UTC by kleslie
Modified: 2007-09-26 09:14 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 kleslie 2004-03-05 13:05:04 UTC 
When I change the compiler output target 
directory/folder for internal javac compiler 
where the classes are compiled the IDE does not 
look in this folder to see if the files are 
compiled and then toggle the 'needs compiled' 
icon indicator off.  Usually, if the target 
folder is the same as the source folder the 
little red indicator is switched off when the 
files are compiled.  If the classes are put into 
a folder other than the same by using the Tools 
Options Compiler Target setting the IDE does not 
look in the Target folder and set the switch 
properly. I suspect it still is looking in the 
source folder. I was hoping that this might be an 
easy fix since the IDE has the mechanism to check 
the folder where the .java files reside and could 
be enhanced to check the Target folder if there 
is one set...or am I missing a step somewhere?
Comment 1 Milan Kubec 2004-03-05 14:24:35 UTC 
Reassigning for evaluation.
Comment 2 Jan Pokorsky 2004-03-09 11:07:47 UTC 
The same is reproducible with the external compiler too. Problem is in
org.netbeans.modules.java.JavaCompilerType.isUpToDate where java file
seems to be newer than class file.

Everything seems to work well until Clean is run. It needs deeper
investigation.
Comment 3 Jan Pokorsky 2004-03-11 17:31:17 UTC 
*** Issue 40438 has been marked as a duplicate of this issue. ***
Comment 4 Jan Becicka 2004-07-13 15:38:07 UTC 
solved by new build system in promoD