[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Chip Chandler (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Chip Chandler edited comment on JBIDE-2720 at 7/21/16 3:55 PM:
---------------------------------------------------------------
!!screenshot-3.png!!
Eclipse Java EE IDE for Web Developers.
Version: Neon Release (4.6.0)
Build id: 20160613-1800
was (Author: chipoc):
!!screenshot-3.png!!
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Ilya Buziuk
> Fix For: 4.4.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, screenshot-2.png, screenshot-3.png, Unbenannt.PNG, Unbenannt.PNG, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Chip Chandler (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Chip Chandler commented on JBIDE-2720:
--------------------------------------
!!screenshot-3.png!!
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Ilya Buziuk
> Fix For: 4.4.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, screenshot-2.png, screenshot-3.png, Unbenannt.PNG, Unbenannt.PNG, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Chip Chandler (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Chip Chandler updated JBIDE-2720:
---------------------------------
Attachment: screenshot-3.png
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Ilya Buziuk
> Fix For: 4.4.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, screenshot-2.png, screenshot-3.png, Unbenannt.PNG, Unbenannt.PNG, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Chip Chandler (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Chip Chandler updated JBIDE-2720:
---------------------------------
Attachment: screenshot-2.png
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Ilya Buziuk
> Fix For: 4.4.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, screenshot-1.png, screenshot-2.png, Unbenannt.PNG, Unbenannt.PNG, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install
by Robert Terzi (JIRA)
[ https://issues.jboss.org/browse/JBDS-3862?page=com.atlassian.jira.plugin.... ]
Robert Terzi commented on JBDS-3862:
------------------------------------
I'm pretty sure a default installation of Cygwin doesn't alter the Windows path. It's optional because they get a shortcut to launch MinTTY with bash inside which runs the the created profile. So No. 1 would be unreliable.
Not sure about No. 2 - At least on my Windows 7 system, I don't get an uninstall entry in Add/Remove Programs for Cygwin.
As for No. 3. the default location for Cygwin is C:\Cygwin. (or probably %SystemDrive%\Cygwin
To me No.3 / prompting to install cygwin or provide path if it isn't C:\cygwin seems best.
> Platform installer failed to detect existing Cygwin install
> -----------------------------------------------------------
>
> Key: JBDS-3862
> URL: https://issues.jboss.org/browse/JBDS-3862
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit,
> Cygwin 2.5.1 already installed in the detault location C:\cygwin.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.1.0.AM2
>
>
> The installer did not detect the existing Cygwin install in C:\Cygwin.
> What test is used to determine if Cygwin is already installed?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3972) RHDS freezes on opening attached xml file
by Josef Ludvicek (JIRA)
Josef Ludvicek created JBDS-3972:
------------------------------------
Summary: RHDS freezes on opening attached xml file
Key: JBDS-3972
URL: https://issues.jboss.org/browse/JBDS-3972
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Affects Versions: 10.0.0.GA
Reporter: Josef Ludvicek
Attached is single-line xml - rss from Picasa web album with size 348K.
After attempt to open it (double click / open in xml editor) whole RHDS freezes and must be killed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3972) RHDS freezes on opening attached xml file
by Josef Ludvicek (JIRA)
[ https://issues.jboss.org/browse/JBDS-3972?page=com.atlassian.jira.plugin.... ]
Josef Ludvicek updated JBDS-3972:
---------------------------------
Description:
Attached [^rss-content.xml] is single-line xml - rss from Picasa web album with size 348K.
After attempt to open it (double click / open in xml editor) whole RHDS freezes and must be killed.
was:
Attached is single-line xml - rss from Picasa web album with size 348K.
After attempt to open it (double click / open in xml editor) whole RHDS freezes and must be killed.
> RHDS freezes on opening attached xml file
> -----------------------------------------
>
> Key: JBDS-3972
> URL: https://issues.jboss.org/browse/JBDS-3972
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Affects Versions: 10.0.0.GA
> Reporter: Josef Ludvicek
> Attachments: rss-content.xml
>
>
> Attached [^rss-content.xml] is single-line xml - rss from Picasa web album with size 348K.
> After attempt to open it (double click / open in xml editor) whole RHDS freezes and must be killed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3862?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3862 at 7/21/16 2:47 PM:
--------------------------------------------------------------
There is no detection for cygwin yet.
cygwin is installed to get ssh, rsync and scp.
There are several options how to check:
1. If cygwin/bin is in PATH 'where ssh' should do the trick; also it supposed to check rsync and scp
2. Check windows registry if cygwin is in list of installed applications;
3. Ask for location where required utils are installed.
was (Author: dgolovin):
There is mo detection for cygwin yet.
cygwin is installed to get ssh, rsync and scp.
There are several options how to check:
1. If cygwin/bin is in PATH 'where ssh' should do the trick; also it supposed to check rsync and scp
2. Check windows registry if cygwin is in list of installed applications;
3. Ask for location where required utils are installed.
> Platform installer failed to detect existing Cygwin install
> -----------------------------------------------------------
>
> Key: JBDS-3862
> URL: https://issues.jboss.org/browse/JBDS-3862
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit,
> Cygwin 2.5.1 already installed in the detault location C:\cygwin.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.1.0.AM2
>
>
> The installer did not detect the existing Cygwin install in C:\Cygwin.
> What test is used to determine if Cygwin is already installed?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months