November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-776) VPE don't recognize some Struts tags

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-776?page=com.atlassian.jira.plugin.... ] Konstantin Marmalyukov updated JBIDE-776: ----------------------------------------- Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich) > VPE don't recognize some Struts tags > ------------------------------------ > > Key: JBIDE-776 > URL: https://issues.jboss.org/browse/JBIDE-776 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-templates > Affects Versions: 2.0.0.Beta3 > Environment: WindowsXP SP2 > rhds-win32-1.0.0.ALPHA.jar > Red Hat Developer Studio > Version: 1.0.0 > Build id: 1.0.0 > Reporter: Aliaksey Nis > Assignee: Konstantin Marmalyukov > Fix For: LATER > > Attachments: StrutsOpenOnsTestProjectZ.zip, Strutstags.JPG > > > The tag should display sting from corresponding message bundle. > Example: we have in struts-config.xml following declaration: > <message-resources key="resource" parameter="resource"/> > in file resource.properties: > badlogin=Your password or login is incorrect! > JSP: > <bean:message bundle="resource" key="badlogin"/> > Tag should dispay "Your password or login is incorrect!", but it is shown as unknown tag. > Look at attached screenshot with examples of unrecognized tags. > Test project attached -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6334) Preferences to control DnD markers parameters and captions like Color, What kind of markers to show and what colors should be used

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6334?page=com.atlassian.jira.plugin... ] Konstantin Marmalyukov updated JBIDE-6334: ------------------------------------------ Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich) > Preferences to control DnD markers parameters and captions like Color, What kind of markers to show and what colors should be used > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-6334 > URL: https://issues.jboss.org/browse/JBIDE-6334 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 3.2.0.M1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Optional > Labels: dnd, new_and_noteworthy, vpe > Fix For: 4.2.x > > > DnD markers behavior should have preferences to control at least color, because at first sight I would prefer different color scheme. Red for possible positions and black for position where dropped element is going to be inserted. > Here option candidates: > 1. Show Possible Drop Markers : Yes/No checkbox > 2. Possible Drop Location Marker color: Color Chooser > 3. Drop Location Marker Color > 4. Highlight Drop Target Element: yes/No checkbox > 5. Highlighted element Border color: Color Chooser > 6. Highlighted element Background color: Color Chooser > 7. Highlighting Transparency: 50-100% > In DnD captions (JBIDE-5970) would be good to have preferences to let it be controlled. Something like: > 1. Where to show caption: VPE ,Eclipse Status Line > 2. Where to show if VPE is selected in point 1: Align to Cursor, Highlighted element or have it always at the same fixed place. > 3. Show the code after DnD is finished in caption: Yes/No > 4. Font color: Color chooser -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3816) Separate VPE from xmodel

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3816?page=com.atlassian.jira.plugin... ] Konstantin Marmalyukov updated JBIDE-3816: ------------------------------------------ Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich) > Separate VPE from xmodel > ------------------------ > > Key: JBIDE-3816 > URL: https://issues.jboss.org/browse/JBIDE-3816 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 3.0.0.CR2 > Reporter: Maxim Areshkau > Assignee: Konstantin Marmalyukov > Fix For: LATER > > > Sepatate VPE from xmodel -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4936) Support for static navigation.

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4936?page=com.atlassian.jira.plugin... ] Konstantin Marmalyukov updated JBIDE-4936: ------------------------------------------ Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich) > Support for static navigation. > ------------------------------ > > Key: JBIDE-4936 > URL: https://issues.jboss.org/browse/JBIDE-4936 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 3.1.0.M4 > Reporter: Yura Zhishko > Assignee: Konstantin Marmalyukov > Fix For: LATER > > > As a new Feature for VPE I propose to make a support for static navigation. A simple example can be founded in JSF 1.2 Kick Start project. > 1) Open inputUserName.jsp > 2) One click on button Say Hello on the visual pane > Static navigation assumes, when we make a click on this button, hello.jsp page should be opened with JBT editor, as the navigation-rule describes this in faces-config.xml: > <navigation-rule> > <from-view-id>/pages/inputUserName.jsp</from-view-id> > <navigation-case> > <from-outcome>hello</from-outcome> > <to-view-id>/pages/hello.jsp</to-view-id> > </navigation-case> > </navigation-rule> > The utility of this feature is that the user can see the result of clicking on this button is some cases (the page that will be opened, when he(she) clicks on button). Plus, there is faster navigation. -- 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, 5 months

1
0
0 / 0

[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: ----------------------------------------------- [~maria.beltran], can you clarify your environment? Do you have JBoss Tools with Eclipse indigo or Jboss DevStudio? Anyway, it looks like you have rather old tools/studio. I recommend you to download fresh release:) > 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 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, 5 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: ------------------------------------ Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich) > 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 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15788: ------------------------------------- leave it open for 4.1.2 please > Download runtime wizard shouldn't complain if install folder doesn't exist > -------------------------------------------------------------------------- > > Key: JBIDE-15788 > URL: https://issues.jboss.org/browse/JBIDE-15788 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.1.1.Alpha2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.1.2 > > Attachments: cr1-nonexistent-folder.png, install_folder_must_exist.png > > > If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary) > - assert no EAP/AS7 are installed > - create a new html5 project from central > - click download and install for the server requirement > - enter a non-existing location for the install folder > !install_folder_must_exist.png! -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Maria Beltrán (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Maria Beltrán commented on JBIDE-2720: -------------------------------------- Hi, I have Eclipse Indigo insalled and JBoss 4.2.3.GA Later I had a problem with Visual page editor: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported. This is solved however now I have other issue with this message: Could not open the Visual Page Editor: the version of the bundled XULRunner reference:file:plugins/org.mozilla.xulrunner.win32.win32.x86_64_1.9.2.25/ must be >= 1.9.1.0 and <= 1.9.2.19 Could you help me please? Saludos desde Barcelona > 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.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 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16114) CLONE - Implement a Popup Dialog containing a Table with all the applicable plugin/command combinations

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16114?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-16114. -------------------------------- Resolution: Done > CLONE - Implement a Popup Dialog containing a Table with all the applicable plugin/command combinations > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16114 > URL: https://issues.jboss.org/browse/JBIDE-16114 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.2.0.Alpha1 > > > upon selecting the command, this should be pasted into the forge 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16106) Bump maven-war-plugin version to 2.4 in openshift profile

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16106?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16106: -------------------------------- Assignee: Andre Dietisheim (was: Fred Bricon) > Bump maven-war-plugin version to 2.4 in openshift profile > --------------------------------------------------------- > > Key: JBIDE-16106 > URL: https://issues.jboss.org/browse/JBIDE-16106 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Trivial > Fix For: 4.2.0.Alpha1 > > > We should update maven-war-plugin version to 2.4 for when the openshift profile is added to a pom.xml, whether the project has been added to openshift or while using the openshift profile template in the pom editor (go to <profiles> and ctrl+space) -- 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, 5 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 November 2013