[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Steffen Brumm (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Steffen Brumm updated JBIDE-2720:
---------------------------------
Attachment: Unbenannt.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: Konstantin Marmalyukov
> Fix For: 4.2.x, 4.3.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, 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.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Steffen Brumm (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Steffen Brumm commented on JBIDE-2720:
--------------------------------------
Doesnt work with eclipse Mars. Get a
R6034 error. see attached file
> 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: Konstantin Marmalyukov
> Fix For: 4.2.x, 4.3.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, 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.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Steffen Brumm (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Steffen Brumm updated JBIDE-2720:
---------------------------------
Attachment: Unbenannt.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: Konstantin Marmalyukov
> Fix For: 4.2.x, 4.3.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, 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.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective?
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3507:
-----------------------------
CDW qa_ack: ? (was: +)
CDW pm_ack: +
CDW devel_ack: ?
CDW release: ?
CDW docs_ack: ?
> Extra step in opening terminal in git perspective?
> --------------------------------------------------
>
> Key: JBDS-3507
> URL: https://issues.jboss.org/browse/JBDS-3507
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-certification
> Affects Versions: 9.0.0.Beta2
> Reporter: Len DiMaggio
> Fix For: 9.0.0.CR1
>
> Attachments: terminal.png
>
>
> If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective?
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.... ]
Jiri Peterka updated JBDS-3507:
-------------------------------
Fix Version/s: 9.0.0.CR1
CDW qa_ack: +
Target Release: 9.0.0.GA
> Extra step in opening terminal in git perspective?
> --------------------------------------------------
>
> Key: JBDS-3507
> URL: https://issues.jboss.org/browse/JBDS-3507
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-certification
> Affects Versions: 9.0.0.Beta2
> Reporter: Len DiMaggio
> Fix For: 9.0.0.CR1
>
> Attachments: terminal.png
>
>
> If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20470) "Early Access enabled/installed" is hidden even though EA stuff is installed.
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20470?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-20470:
-------------------------------------
Assignee: Fred Bricon (was: Snjezana Peco)
> "Early Access enabled/installed" is hidden even though EA stuff is installed.
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20470
> URL: https://issues.jboss.org/browse/JBIDE-20470
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta2
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.0.CR1
>
> Attachments: earlyaccess.png, earlyaccess2.png
>
>
> In previous version (4.2) the message varied of EA installed, EA enabled, EA enabled/installed.
> Now the message just says that EA is enabled/installed, but only depends on the checkbox on Software/Update page.
> When EA stuff is installed, but the checkbox is unchecked, the message is hidden even though it should be still shown imho.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20466) Generate JAX-RS resource methods inside an editor
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20466?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-20466:
----------------------------------
Fix Version/s: 4.4.x
> Generate JAX-RS resource methods inside an editor
> -------------------------------------------------
>
> Key: JBIDE-20466
> URL: https://issues.jboss.org/browse/JBIDE-20466
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.4.x
>
>
> It would be nice to have generating stub methods inside an editor. E.g. JAX-RS resource CarResource class is opened and there would be some either content assist proposals to generated methods or there could be generating inside context menu Source -> Generate JAX-RS methods (or some different label).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20466) Generate JAX-RS resource methods inside an editor
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20466?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-20466:
---------------------------------------
I full agree with you. I'll see what can be done in 4.4.
> Generate JAX-RS resource methods inside an editor
> -------------------------------------------------
>
> Key: JBIDE-20466
> URL: https://issues.jboss.org/browse/JBIDE-20466
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.4.x
>
>
> It would be nice to have generating stub methods inside an editor. E.g. JAX-RS resource CarResource class is opened and there would be some either content assist proposals to generated methods or there could be generating inside context menu Source -> Generate JAX-RS methods (or some different label).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months