[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, 2 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, 2 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, 2 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, 2 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, 2 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, 2 months
[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20004:
----------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> OpenShift v3 resources names should be camelcasized or splitted by space character
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-20004
> URL: https://issues.jboss.org/browse/JBIDE-20004
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
>
> Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format.
> Affected resources:
> * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs"
> * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs"
> * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams"
> * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers"
> I would suggest to use capitalized separated wording but I leave it up to decision of developer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-20521) Show In - Web Browser is enabled and do nothing when there are no routes
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20521:
-------------------------------------
Summary: Show In - Web Browser is enabled and do nothing when there are no routes
Key: JBIDE-20521
URL: https://issues.jboss.org/browse/JBIDE-20521
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.CR1
Reporter: Marián Labuda
Priority: Minor
When I am having a project with an application without any route, the Show In - Web Browser context menu of a project is enabled for this project and it does not do anything (after click nothing happens). Context menu should be disable if there are no routes for an application.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19335:
-------------------------------------
As I wrote in comment above: "Tested with JBDS 9.0.0.Beta2 B67"
It had fix version "4.3.0.Beta2" at the time I was verifying it therefore I was testing it with JBDS 9.0.0.Beta2 B67
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19335
> URL: https://issues.jboss.org/browse/JBIDE-19335
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'.
> Steps to tests the issue:
> 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify)
> 2. Run JBT and try to download WildFly using Runtime Download dialog;
> 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one
> 4. Close eclipse
> 5. Install libwebkit
> 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-20520) Project tree item in New OpenShift Application wizard disappear after click on a template
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20520:
-------------------------------------
Summary: Project tree item in New OpenShift Application wizard disappear after click on a template
Key: JBIDE-20520
URL: https://issues.jboss.org/browse/JBIDE-20520
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.CR1
Reporter: Marián Labuda
Attachments: after.png, before.png
Click on a template on the first wizard page In a New OpenShift Application wizard makes disappear the project tree item having the template. See following screenshots:
before click on a template
!before.png!
after click on a template
!after.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months