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 15585 - Old fastjavac is used after autoupdate
Summary: Old fastjavac is used after autoupdate
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: -FFJ-
Hardware: All Windows ME/2000
: P1 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-18 13:46 UTC by Jan Becicka
Modified: 2007-09-26 09:14 UTC (History)
3 users (show)

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 Jan Becicka 2001-09-18 13:46:48 UTC 
Fastjavac compilation uses {ide.home}{/}bin{/}fastjavac{/}, but autoupdate 
stores new fastjavac into {user.home}{/}bin{/}fastjavac{/}
Comment 1 Ivan Bradac 2001-09-18 14:13:39 UTC 
There is a workaround: Restart Forte once again after the update. However, this workaround is 
unacceptable since updating via the autoupdate is a fundamental feature which must work correctly and if 
this functionality is broken, it leads to a NO-GO for any patch releases including the JP3.1. Therefore I 
have raised the priority.

Reassigning to core since this is a general core problem. It occurs also for a lot of other modules and 
the possible problem could be in the ModuleInstaller which does not recognize new versions of modules 
located in the userdir.
Comment 2 Svata Dedic 2001-09-18 14:27:05 UTC 
Nonono ;-) please leave this bug in Java. There's another bug, which
is in the core -- that javac.jar is loaded from installdir/modules/ext
although the file also exists in userdir/modules/ext.
I'm working on the fix in the main trunk (should be fairly easy though)
Comment 3 Svata Dedic 2001-09-18 14:35:31 UTC 
See also issue #15586
Comment 4 Svata Dedic 2001-09-18 17:12:10 UTC 
Removing keyword JDK_1.4 -- the bug is not specific to JDK-1.4, it's
caused by incorrect search algorithm in the java module.
The bug still lived in NetBeans so -- I've fixed it in trunk,
FastJavacCompilerType.java version 1.28.
Comment 5 Svata Dedic 2001-09-18 17:13:03 UTC 
Ivan, could you please merge the fix in the Forte branch ?
Comment 6 Jan Becicka 2001-09-25 09:20:46 UTC 
Verified in JP3
Comment 7 Jan Becicka 2001-09-25 09:41:05 UTC 
Oops, but it works only on Win.
New fastjavac.linux doesn't have execution permissions.
Comment 8 Jan Chalupa 2001-10-02 09:38:41 UTC 
I think this is fixed in the new version of JP3. I'm marking as 
RESOLVED FIXED. Ivan please comment/reopen if you have something to 
add.
Comment 9 Jan Becicka 2001-10-03 14:23:42 UTC 
[JP3] Verified
[200110031034] Verified
Comment 10 Quality Engineering 2003-07-01 13:19:25 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.