[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-2720:
--------------------------------------------
Try open a html file (not .xhtml) and open the HTML Preview view.
That is what we are now incorporating into the VPE preview when editing plain html (not jsp/jsf which requires the vpe xulrunner templating/preview).
> 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
>
> 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 was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18133) mark as deployable no longer visible in project explorer, common navigator etc.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18133?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18133:
---------------------------------------------
actually - I don't follow the reasoning in JBIDE-15678 why "Mark as deployable" should not be visible in the context menu. All other resource actions are visible on it.
> mark as deployable no longer visible in project explorer, common navigator etc.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18133
> URL: https://issues.jboss.org/browse/JBIDE-18133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Max Rydahl Andersen
> Priority: Critical
>
> JBIDE-15678 limis mark as deployable to only be in Package Explorer.
> That is bad since Project Explorer that are the main view in JBoss / JavaEE perspectives will then no longer have this.
> This also affects *any* views that shows the context menu for resources.
> On these I would argue mark as deployable should be shown.
> It is not only for package explorer.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-18095.
---------------------------------
Resolution: Done
verified no stupid behavior here. Further testing will be done in the unit test jira
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
> Assignee: Rob Stryker
> Priority: Critical
> Labels: regression
> Fix For: 4.2.0.CR1
>
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18133) mark as deployable no longer visible in project explorer, common navigator etc.
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-18133:
-------------------------------------------
Summary: mark as deployable no longer visible in project explorer, common navigator etc.
Key: JBIDE-18133
URL: https://issues.jboss.org/browse/JBIDE-18133
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.CR1
Reporter: Max Rydahl Andersen
Priority: Critical
JBIDE-15678 limis mark as deployable to only be in Package Explorer.
That is bad since Project Explorer that are the main view in JBoss / JavaEE perspectives will then no longer have this.
This also affects *any* views that shows the context menu for resources.
On these I would argue mark as deployable should be shown.
It is not only for package explorer.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-17701) Display method signature in JAX-RS endpoint subnode
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17701?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17701:
----------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.0.CR1)
Description:
Show the real method signature instead of something like {{name(...)}} to avoid confusion when methods are overloaded in the same type.
See what's doable while keeping the label not too long.
was:Show the real method signature instead of something like {{name(...)}} to avoid confusion when methods are overloaded in the same type.
> Display method signature in JAX-RS endpoint subnode
> ---------------------------------------------------
>
> Key: JBIDE-17701
> URL: https://issues.jboss.org/browse/JBIDE-17701
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.1.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Alpha1
>
>
> Show the real method signature instead of something like {{name(...)}} to avoid confusion when methods are overloaded in the same type.
> See what's doable while keeping the label not too long.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17656:
-----------------------------------------
I cannot seem to reproduce this. Can anyone confirm?
Environment: Windows 8.1 (in a VirtualBox VM), Oracle Java 8 Update 5 (1.8.0_05) 32-bit, Eclipse Luna 32-bit
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18132) Move 'core' validation bits in the 'org.jboss.tools.ws.jaxrs.core' plugin
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18132:
-------------------------------------
Summary: Move 'core' validation bits in the 'org.jboss.tools.ws.jaxrs.core' plugin
Key: JBIDE-18132
URL: https://issues.jboss.org/browse/JBIDE-18132
Project: Tools (JBoss Tools)
Issue Type: Task
Components: webservices
Affects Versions: 4.2.0.Beta3
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Move the validation part in the {{org.jboss.tools.ws.jaxrs.core}} plugin and keep the preferences management (preference pages, etc.) in the {{org.jboss.tools.ws.jaxrs.ui}} plugin.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months