July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13833) BrowserSim: zoom webpage for truncated devices

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13833?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13833: ------------------------------------- Issue Type: Feature Request (was: Bug) > BrowserSim: zoom webpage for truncated devices > ---------------------------------------------- > > Key: JBIDE-13833 > URL: https://issues.jboss.org/browse/JBIDE-13833 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Alpha2 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: zoom.png, zoom2.png, zoom2.png > > > When using ipad and others we currently resize the canvas, would be good if we could show the true rendering -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14943) Enable deletion of multiple servers selection in server view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14943?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14943: ------------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=409475 > Enable deletion of multiple servers selection in server view > ------------------------------------------------------------ > > Key: JBIDE-14943 > URL: https://issues.jboss.org/browse/JBIDE-14943 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Martin Malina > Fix For: 4.1.x, 4.2.x > > > When you select multiple servers in server view, it is not possible to delete them all at once. It would be nice to be able to do that - select multiple servers and then hit Delete (or right-click -> Delete). > Requested by [~rawagner] ;) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14943) Enable deletion of multiple servers selection in server view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14943?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-14943: ----------------------------------- Assignee: Rob Stryker > Enable deletion of multiple servers selection in server view > ------------------------------------------------------------ > > Key: JBIDE-14943 > URL: https://issues.jboss.org/browse/JBIDE-14943 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.x, 4.2.x > > > When you select multiple servers in server view, it is not possible to delete them all at once. It would be nice to be able to do that - select multiple servers and then hit Delete (or right-click -> Delete). > Requested by [~rawagner] ;) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14925) OutOfMemory during javaee build

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14925?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14925: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/117 (was: https://github.com/jbosstools/jbosstools-javaee/pull/97) Thanks for the feedback Alexey. Here is a rebased PR that you should be able to apply directly on master: https://github.com/jbosstools/jbosstools-javaee/pull/117 > OutOfMemory during javaee build > ------------------------------- > > Key: JBIDE-14925 > URL: https://issues.jboss.org/browse/JBIDE-14925 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, Seam 2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.2.0.Alpha1 > > > Because of this bug in maven-download-plugin: https://github.com/maven-download-plugin/maven-download-plugin/issues/15 , build of javaee component, which consume a lot this maven-download-plugin fail with an OutOfMemory. > download-maven-plugin 1.2.0-SNAPSHOT should fix that, we should give it a try. -- 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, 10 months

1
0
0 / 0

[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 updated JBIDE-2720: ------------------------------------ Description: 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. was: If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load. We should look into providing a xulrunner for windows 64 bit. *Update:* Now XULRunner is provided > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10939) OpenShift Express Console: Should have "Edit Connection" in the context menu

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10939?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-10939: --------------------------------------- Just my 2c: why not putting an hyperlink as in the server views ? > OpenShift Express Console: Should have "Edit Connection" in the context menu > ---------------------------------------------------------------------------- > > Key: JBIDE-10939 > URL: https://issues.jboss.org/browse/JBIDE-10939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: edit-connection.png, new-connection.png, Screen Shot 2013-07-29 at 11.35.23 AM.png > > > it's not obvious how one would edit the user entries in the OpenShift Express console. The most user friendly and obvious way would be to offer *Edit Connection* in the context menu to an entry in the *OpenShift Express Console* -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10939) OpenShift Express Console: Should have "Edit Connection" in the context menu

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10939?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-10939: ---------------------------------- Attachment: Screen Shot 2013-07-29 at 11.35.23 AM.png Screenshot of Server Views with Hyperlink to create a server when none already exists > OpenShift Express Console: Should have "Edit Connection" in the context menu > ---------------------------------------------------------------------------- > > Key: JBIDE-10939 > URL: https://issues.jboss.org/browse/JBIDE-10939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: edit-connection.png, new-connection.png, Screen Shot 2013-07-29 at 11.35.23 AM.png > > > it's not obvious how one would edit the user entries in the OpenShift Express console. The most user friendly and obvious way would be to offer *Edit Connection* in the context menu to an entry in the *OpenShift Express Console* -- 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, 10 months

1
0
0 / 0

[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 updated JBIDE-2720: ------------------------------------ Description: If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load. We should look into providing a xulrunner for windows 64 bit. *Update:* Now XULRunner is provided was: If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load. We should look into providing a xulrunner for windows 64 bit. > 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 jdk, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for windows 64 bit. > *Update:* > Now XULRunner is provided -- 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, 10 months

1
0
0 / 0

[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: ----------------------------------------- [~foretribe] thanks for reporting this! Do you have Intel OpenCL SDK installed? If yes, then uninstalling should help. If no, then could you please [use these steps|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277225...] to find where is dll conflict using Process Explorer? Or you may just disable Visual Editor by adding the option {{–Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio). > 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 jdk, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for windows 64 bit. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15291: ------------------------------------- Priority: Major (was: Blocker) > xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ... > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15291 > URL: https://issues.jboss.org/browse/JBIDE-15291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core, XULRunner > Affects Versions: 4.1.0.Final > Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux > IcedTea JDK 7.2.4.1 > eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz > Reporter: Jochen Buchholz > Fix For: 4.1.x > > Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, m2e-connectors.png > > > I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors." > I cant Use the Marketplace anymore, because he is frozen while load the content. > In the error log I found this line: > Caused by: java.io.IOException: /mnt/usb/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so) > like in the old issue JBIDE-10628 reported also by me > Developer Studio is unusable under 64bit Linux. -- 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2013