To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=78807
User cloph changed the following:
What |Old value |New value
================================================================================
Status|VERIFIED |REOPENED
--------------------------------------------------------------------------------
Resolution|FIXED |
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Aug 1 19:45:50 +0000
2007 -------
reopen issue. Breaks.
I wonder why this issue is flagged as verified. Rene surely didn't look at any
other OS than his linux. Probably didn't even try with Sun's JDK :-(
There are several problems with the approach:
*) you're querying the /runtime/ for the path of the /runtime/, not of the
development kit.
*) you're deliberately modifying the path returned (and then complain about that
it doesn't fit
Szenario A)
User has JDK 1.5 installed (javac is pointing to it), and JRE 1.6 (java points
to that) → check will fail, because there is no JDK
Szenario A')
User has both JDK 1.5 and JDK 1.6 installed, javac points to the 1.5 jdk. Now
configure would detect the 1.6JDK and the buid will break, contrary to the
milestones before.
What is the point in querying for a path, when you don't trust it anyway and
chop off parts of it?
As for Apple's Java, it returns a valid path (maybe not the version of the JDK
that the user would expect, but at least a working one) - however, the last
argument of the path is chopped off → breaks of course.
On linux with Sun's JDK, the last part returned is the jre part, that is chopped
of as well, and just by chance you get a valid JDK_HOME in that case.
Not sure whether IBM's java has the same directory structure as the Sun's one,
but all put together, the previous hackery did do a better job in detecting the
right J*DK*, although a bit more lines involved. (blame it on the distros that
they didn't follow Sun's directory layout). The current way is good for checking
a runtime path, but not so useful when building OOo.
(Yes, I'm refering to the comments made in #dev.openoffice.org)
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
