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 25756 - jdk.home argument is improperly set
Summary: jdk.home argument is improperly set
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Other OpenVMS
: P1 blocker (vote)
Assignee: mgarrison
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-17 18:51 UTC by mgarrison
Modified: 2009-11-07 13:34 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Patch for 25756 *and* 25591 (3.69 KB, patch)
2002-07-17 19:06 UTC, mgarrison 		Details | Diff
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 mgarrison 2002-07-17 18:51:34 UTC 
The jdk.home property does not always get set correctly on 
the command linein the OpenVMS launcher.

When it fails, compiles don't work, neither does debugger.
Hence the P1 rating.

Fix is to convert to UNIX file syntax before issuing Java 
command.

Will post patch shortly.
Comment 1 mgarrison 2002-07-17 19:06:15 UTC 
Created attachment 6765 [details]
Patch for 25756 *and*  25591
Comment 2 Jesse Glick 2002-07-17 20:41:03 UTC 
In general please provide diffs for only the bug reported, not
compounded with other bugs, though in this case it is easy to see
which is which.

I assume that the VM internally uses Unix-style paths for
java.io.File, hence jdk.home needing translation. If so, as a code
reviewer I approve the patch, after the customary 24 hours of course.
Comment 3 mgarrison 2002-07-17 20:59:39 UTC 
Sort of...internally, the VM will use either.   There are 
switches to tell it you'll be using one or the other (or 
even both, believe it or not).  We tell it we'll be using 
UNIX-style.

Can I check this in on Monday when I return from vacation 
and still expect it to make it into the next Beta?
Comment 4 _ ttran 2002-07-18 07:34:00 UTC 
next is Release Candidate 1, not Beta!  We're going final
Comment 5 Jesse Glick 2002-07-19 15:23:38 UTC 
Specifically

http://www.netbeans.org/devhome/docs/releases/34/index.html

shows that this Wednesday is the release candidate, by which time all
fixes for 3.4 should be committed, excepting only trivial last-minute
docs tweaks. To get into RC1 you ought to commit on Tuesday (exact
time to be posted soon to nbdev).
Comment 6 Marek Grummich 2002-07-22 08:15:29 UTC 
Target milestone was changed from not determined to TBD
Comment 7 Marek Grummich 2002-07-22 08:42:55 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 8 Marek Grummich 2002-07-22 08:46:15 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 9 Marek Grummich 2002-07-22 08:54:27 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 10 Marek Grummich 2002-07-22 08:57:42 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 11 Marek Grummich 2002-07-22 09:06:44 UTC 
Set terget milestone to TBD
Comment 12 Marek Grummich 2002-07-22 09:13:00 UTC 
Set terget milestone to TBD
Comment 13 mgarrison 2002-07-22 15:47:57 UTC 
Checked into trunk (1.15) and then merged into release34 
(1.14.10.2)
Comment 14 Jesse Glick 2002-07-22 18:45:47 UTC 
Fixing target milestone.
Comment 15 Marian Mirilovic 2002-07-24 11:21:18 UTC 
Meg, can you download RC1 build and verify the fix? 
Thanks in advance.
Comment 16 mgarrison 2002-07-25 14:24:01 UTC 
I've downloaded RC1 and verified the fix.
Comment 17 Quality Engineering 2003-07-01 16:15:08 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.