| RE: [wtp-dev] Request PMC approval for 139863 for 1.0.3 |
|
A bit more background on this issue... We rely on being able to accurately determine
the version of the java vm of the server runtime in order to control which
versions of the java facet the user should be able to select. For instance if
the VM version is 1.4, the user can select java facet version 1.3 and 1.4.
Unfortunately, there are cases (as of yet not understood) where JDT fails to
determine the VM version. This behavior has been seen on Mac OS (not sure which
VM) and it has recently started showing up sporadically with BEA’s
JRockit VM. The current code arbitrarily assigns version 1.4 to the VM when the
version cannot be determined. The problem with that is that if the actual
version happens to be 5.0 the user cannot pick version 5.0 of java facet (and
hence the corresponding java compiler level). There is no workaround. It is
going to take some time to understand exactly why version detection fails and
to forward that information to the JDT team. In the meantime we can make this
problem less severe by using the highest known VM version (5.0 in the case of
1.0.x) instead of 1.4. This approach places the least restriction on the user.
With this approach, the user will always be able to compensate for the VM version
detection problem by picking the correct version of the java facet on the
facets selection screen. While not perfect, it’s much better than what we
currently have and I highly recommend that we make this fix for 1.0.3. Does anyone have any comments on this? - Konstantin From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Konstantin Komissarchik See https://bugs.eclipse.org/bugs/show_bug.cgi?id=139863
for details. This bug covers improving our workaround for the case where
java vm cannot be detected. The current behavior is rather bad for people who
hit it and the fix is pretty safe. - Konstantin _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. |