[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Yahor Radtsevich commented on JBIDE-2720:
-----------------------------------------
For now we know only one way to force eclipse to use its own MSVCRT. It is to remove all software that ships other versions of MSVCRT.
> 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: Yahor Radtsevich
> Fix For: 4.1.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, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Nick Boldt commented on JBIDE-2720:
-----------------------------------
Do the suggestions here help? (I'm not on Windows or I'd try it.)
http://forums.boxee.tv/showthread.php?t=15425
> 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: Yahor Radtsevich
> Fix For: 4.1.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, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15917) Creation of subsystem framework
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-15917:
-----------------------------------
Summary: Creation of subsystem framework
Key: JBIDE-15917
URL: https://issues.jboss.org/browse/JBIDE-15917
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Reporter: Rob Stryker
Assignee: Rob Stryker
ASTools has a requirement for mixin-style behavior. The current similar API is called the BehaviorModel, however it does not allow for mixin-style behavior. The server can be in only 1 mode at any time, and so therefore can have only 1 set of systems at any time, and there are currently only 2 sets: a local set, and an rse set.
The contents of these sets change based on server version, so for example, AS 6 in 'rse' mode may stop with a java command to the shutdown jar launched over a remote shell, while Wildfly 8 will shutdown with a call to management.
A model needs to be created to resolve and load arbitrary systems, even those not declared by ASTools directly, or allow alternate implementations of the common systems for server types such as OpenShift or Teiid Designer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15915) Large-scale refactor to split major functionality into clear systems with public API
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-15915:
-----------------------------------
Summary: Large-scale refactor to split major functionality into clear systems with public API
Key: JBIDE-15915
URL: https://issues.jboss.org/browse/JBIDE-15915
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.2.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Alpha1
ASTools currently suffers from tight coupling, mixing of API and non-API classes, an API that is not clear, a very long unit test run, and other symptoms which stem from the above problems. Several newer use-cases are impossible to solve without making the problem worse.
To solve these issues, ASTools needs to have its major functionality split up and separated. The API for each system needs to be clearly apparent and easy to use, from both core, ui, and other consumers. In general, if UI classes are not using the API and are reaching in to internal classes, then the API is insufficient and needs to be cleaned up.
This large-scale refactor will focus first on the deploy-only server as an example and can eventually be (easily) extended to the other server types.
https://community.jboss.org/wiki/JBossTools-DelegatingServersViaSubsystems
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months