[
https://issues.jboss.org/browse/JBDS-1532?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-1532:
-------------------------------------
Martin, haven't committed yet whole fix because it is little more complex like you
explained.
Features to fix in CR1 are:
1. Support for radio buttons for all platforms to show architecture for selected JVM (they
are going to be disabled because -d is realy works only for mac)
2. Description for every platform what to expect from selected architecture (and like you
suggested 32-bit (recommended) on mac and windows sounds good for me)
And you're right 32-bit and 64-bit are better names for radio buttons
Users should be warned when installing 32 bit JBDS on 64 bit Leopard
--------------------------------------------------------------------
Key: JBDS-1532
URL:
https://issues.jboss.org/browse/JBDS-1532
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: documentation, installer
Affects Versions: 4.0.0.CR1
Environment: Mac OS X 10.5 Leopard
jbdevstudio-product-macosx-cocoa-4.0.0.v201101230948R-H100-CR1.jar
Reporter: Martin Malina
Assignee: Denis Golovin
Fix For: 5.0.0.Beta3
I stumbled upon this when testing JBDS on Leopard:
When you install the Cocoa (32bit) version of JBDS on Leopard, it lets you install it
with no problem even though it's not supported because then it's bound to run with
Java 1.5 (Java 1.6 is 64bit-only on Leopard).
When you start JBDS after the installation at first everything seems ok - the welcome
screen, the menu... But for example the installed EAP runtime is missing and soon you
realize that other plugins are missing too - this is the result of running JBDS running
with Java 1.5 in this case.
If a user installs 32bit version of JBDS on Leopard, it is his fault. But it would be
nice to have some kind of warning - either during the installation. Or when JBDS is
started with Java 1.5.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira