[JBoss JIRA] (JBTIS-301) Move Fuse server manipulation from fuse into runtime plugin
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-301?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík reassigned JBTIS-301:
----------------------------------
Assignee: Tomáš Sedmík (was: Andrej Podhradsky)
> Move Fuse server manipulation from fuse into runtime plugin
> -----------------------------------------------------------
>
> Key: JBTIS-301
> URL: https://issues.jboss.org/browse/JBTIS-301
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: QE
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> It will be very useful to move fuse/karaf server manipulation (add server runtime, server, deploying, ...) from _org.jboss.tools.fuse.reddeer_ into _org.jboss.tools.runtime.reddeer_.
> Consequently, other plugins/tests can use it.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBTIS-301) Move Fuse server manipulation from fuse into runtime plugin
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-301:
----------------------------------
Summary: Move Fuse server manipulation from fuse into runtime plugin
Key: JBTIS-301
URL: https://issues.jboss.org/browse/JBTIS-301
Project: JBoss Tools Integration Stack
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QE
Reporter: Tomáš Sedmík
Assignee: Andrej Podhradsky
It will be very useful to move fuse/karaf server manipulation (add server runtime, server, deploying, ...) from _org.jboss.tools.fuse.reddeer_ into _org.jboss.tools.runtime.reddeer_.
Consequently, other plugins/tests can use it.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Axel Wathne (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Axel Wathne updated JBIDE-18095:
--------------------------------
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 (was: 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, JBoss EAP 5.2.0 (nightly/luna repo) on Oracle Java 1.7.0_45)
> 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
>
> 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, 9 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Axel Wathne (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Axel Wathne updated JBIDE-18095:
--------------------------------
Description:
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.
was:
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.
> 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, JBoss EAP 5.2.0 (nightly/luna repo) on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
>
> 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, 9 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Axel Wathne (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Axel Wathne updated JBIDE-18095:
--------------------------------
Summary: Server adapter fails to publish modules with non-ASCII class names (was: Server adapter publishes EAR incompletely on EAP5)
Description:
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.
was:
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 is that I can't see any significant differences between one that work normally and those that fail to publish.
I realize that this is a meager bug report, but I don't know where to get more details. There is nothing in the Eclipse error log, no popups, and the server console log just reports the ClassNotFoundException. Any suggestions on how to find more details are welcome.
Steps to Reproduce: EAR project with dependency plain java "Utility module", deploy to EAP 5.2.0, a Java class with a non-ASCII name. (was: EAR project with dependency plain java "Utility module", deploy to EAP 5.2.0 , however the behaviour is only seen with two of a larger number of modules. )
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, JBoss EAP 5.2.0 (nightly/luna repo) on Oracle Java 1.7.0_45 (was: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140808-0027-B565, JBoss EAP 5.2.0 (nightly/luna repo) on Oracle Java 1.7.0_45)
Updated title and description
> 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, JBoss EAP 5.2.0 (nightly/luna repo) on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
>
> 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, 9 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov commented on JBIDE-2720:
-----------------------------------------------
{quote}Besides that I had to manually enable BrowserSim command group in perspective customization in order to get BrowserSim icon. {quote}
BrowserSim icon by default is available under JBoss, Web Development and CSS Editing perspectives, we decide not to include it to all perspectives.
Thanks for your feedback!
> 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, 9 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov commented on JBIDE-2720:
-----------------------------------------------
We generate preview for HTML pages with default system SWT browser(ie on Win, WebKit on Mac, on Linux - depends on GTK version). Unfortunately, javafx browser doesn't work for us cuase Oracle java is not officially supported on some Linux distors, so we cannot make it a requirement.
> 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, 9 months