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 29973 - Internal compiler attempts to recompile library source code
Summary: Internal compiler attempts to recompile library source code
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC OS/2
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-12 23:42 UTC by _ gtzabari
Modified: 2007-09-26 09:14 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 _ gtzabari 2003-01-12 23:42:39 UTC
dev build 200301020100
IBM JDK 1.3.1

    I mount dom4j.jar using the archive FS and its
source code using the directory FS. Notice I used
two separate file systems. The class files
(dom4j.jar) are mounted BEFORE the sources.

    Then I try compiling source code which depends
upon dom4j using the internal compiler. For some
unknown reason, the compiler tries recompiling the
sources even though the class files obviously
already exists in the jar file. Removing the
source code directory and recompiling my
application works flawlessly and it does not try
to recompile the dom4j sources.

    I believe this is a bug in the internal
compiler. It should not be trying to recompile dom4j.
Comment 1 Svata Dedic 2003-02-28 07:11:46 UTC
In the meantime, please verify that the source files are older than
their matching .class files. If they are not, the compiler's timestamp
check fails and the compiler will try to "update" the .class files.
Even then you may set the source's filesystem COMPILE capability to
False, and the compiler won't see the sources at all.
Comment 2 Svata Dedic 2003-02-28 10:05:16 UTC
Seems to work for me (when .class files have the correct timestamp). I
also tried to position the source filesystem before the .jar; tested
on IBM JDK 1.3.0 for Linux.

You may also run into the issue if:
- you make the source filesystem part of the project tab
- you run "Build Project" or "Compile Project" action
In that case, the IDE will discover that .class files for project
contents are not at the place the compiler would put them (depending
on Target property) and tries to compile.