[JBoss JIRA] (JBDS-2180) 32/64-bin radio button in installer is ignored when installing with Oracle JDK 1.7 on Mac
by Martin Malina (JIRA)
Martin Malina created JBDS-2180:
-----------------------------------
Summary: 32/64-bin radio button in installer is ignored when installing with Oracle JDK 1.7 on Mac
Key: JBDS-2180
URL: https://issues.jboss.org/browse/JBDS-2180
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 5.0.0.CR1
Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
Reporter: Martin Malina
Fix For: 5.0.0.CR1
I accidentally had my java set to java 1.7 on my mac computer:
vokuro:5.0.0.CR1 rasp$ java -version
java version "1.7.0_04"
Java(TM) SE Runtime Environment (build 1.7.0_04-b21)
Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
When you then launch the installer using
java -jar jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
everything seems ok, you are allowed to select either 32 or 64-bit installation, but regardless of what you choose, the 64-bit version will be installed.
Not sure how this can be handled. At the very least we should disable the radio buttons and preselect 64-bit if that's what must be installed. But the fact is that JBDS will run with java 1.6 anyway. Even if you installed it using 1.7. So wouldn't it be possible to install the 32-bit version even if the installer is run using java 1.7 64-bit?
FYI, on Mac OS X Lion, there are currently these jdk versions:
Apple JDK 1.6 32-bit
Apple JDK 1.6 64-bit
Oracle JDK 1.7 64-bit
I don't expect there will ever be Oracle JDK 1.7 32-bit available.
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBDS-1499) [Migration Guide] Xulrunner plugin error explanation unclear.
by Andrew Ross (JIRA)
[Migration Guide] Xulrunner plugin error explanation unclear.
-------------------------------------------------------------
Key: JBDS-1499
URL: https://issues.jboss.org/browse/JBDS-1499
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: documentation
Affects Versions: 4.0.0.Beta2
Reporter: Andrew Ross
3.2. Visual Editor doesn't start and "XPCOM error -2147467259" appears
"This error shows that you have problems with your buildin XULRunner plugin.To resolve the issue,please: "
"try xulrunner.exe -version or ./xulrunner -version command and you will see what is needed for XULRunner to work "
COMMENT: How does finding the xulrunner version fix this problem? Is there a minimum version?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBDS-2001) Investigate use of egit 1.3 in JBDS 5 and JBoss Central
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2001:
--------------------------------
Summary: Investigate use of egit 1.3 in JBDS 5 and JBoss Central
Key: JBDS-2001
URL: https://issues.jboss.org/browse/JBDS-2001
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central, updatesite
Affects Versions: 5.0.0.M5
Reporter: Fred Bricon
Assignee: Len DiMaggio
Fix For: 5.0.0.Beta1
I've been using native svn 1.7 for a while now, Today while reinstalling a new Eclipse installation from scratch, I installed subclipse from JBoss Central.
After installation, I tried to share my existing projects in eclipse but couldn't, since the 1.7 checkout is not supported by subclipse (based on svn 1.6).
Can we update the subclipse version from central to use the 1.8.x stream?
With svn 1.7, you have only have one .svn folder at the root of your checkout, no more .svn folders crawling everywhere making copying and moving folders a breathe.
--
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
13 years, 9 months
[JBoss JIRA] (JBIDE-10730) Update subclipse version available in JBoss Central
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-10730:
-----------------------------------
Summary: Update subclipse version available in JBoss Central
Key: JBIDE-10730
URL: https://issues.jboss.org/browse/JBIDE-10730
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng, central
Affects Versions: 3.3.0.M5
Reporter: Fred Bricon
Assignee: Nick Boldt
Fix For: 3.3.0.Beta1
I've been using native svn 1.7 for a while now, Today while reinstalling a new Eclipse installation from scratch, I installed subclipse from JBoss Central.
After installation, I tried to share my existing projects in eclipse but couldn't, since the 1.7 checkout is not supported by subclipse (based on svn 1.6).
Can we update the subclipse version from central to use the 1.8.x stream?
With svn 1.7, you have only have one .svn folder at the root of your checkout, no more .svn folders crawling everywhere making copying and moving folders a breathe.
--
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
13 years, 9 months