August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17896) Show selection tag bar property is ignored

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17896?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-17896: ------------------------------------------------ don't think so, afair preview doesn't touch any of vpe options, it only reuse some VPE stuff > Show selection tag bar property is ignored > ------------------------------------------ > > Key: JBIDE-17896 > URL: https://issues.jboss.org/browse/JBIDE-17896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3-v20140712-0200-B178 > Fedora 18 KDE > SWT_GTK3=0 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > 1. Create JSF1.2 Kick Start project > 2. Open inputUserName.jsp > 3. Click on some element within page source do not select any text > ERROR: Empty selection tag bar is shown > 4. Select some text > ASSERT: Proper selection is displayed within selection tag bar > 5. Click on Toggle Selection Tag Bar > ASSERT: Selection tag bar is hidden > 6. Click on Preferences toolitem > ASSERT: Property Show selection tag bar property is unchecked > 7. Reopen page > ERROR: VPE is in the same state as after step 3. Selection tag bar is visible and empty. > 8.Click on Preferences toolitem > ASSERT: Property Show selection tag bar property is unchecked -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17707) Selection tag bar is always hidden when switching from Source to Visual

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17707?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17707: ---------------------------------------- Priority: Critical (was: Major) > Selection tag bar is always hidden when switching from Source to Visual > ------------------------------------------------------------------------ > > Key: JBIDE-17707 > URL: https://issues.jboss.org/browse/JBIDE-17707 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Alexey Kazakov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.CR1 > > > 1. Open any html5 file with JBoss HTML Editor. > 2. Switch to the Visual/Source tab. > 3. Click on "Toggle selection tag bar" button to show the selection tag bar. > 4. Switch to the "Source" tab. > 5. Switch to the Visual/Source tab again. > 6. FAILURE: The selection bar is hidden despite of enabled "Toggle selection tag bar" button. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17896) Show selection tag bar property is ignored

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17896?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17896: --------------------------------------------- sounds like regression bug after preview was introduced ? > Show selection tag bar property is ignored > ------------------------------------------ > > Key: JBIDE-17896 > URL: https://issues.jboss.org/browse/JBIDE-17896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3-v20140712-0200-B178 > Fedora 18 KDE > SWT_GTK3=0 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > 1. Create JSF1.2 Kick Start project > 2. Open inputUserName.jsp > 3. Click on some element within page source do not select any text > ERROR: Empty selection tag bar is shown > 4. Select some text > ASSERT: Proper selection is displayed within selection tag bar > 5. Click on Toggle Selection Tag Bar > ASSERT: Selection tag bar is hidden > 6. Click on Preferences toolitem > ASSERT: Property Show selection tag bar property is unchecked > 7. Reopen page > ERROR: VPE is in the same state as after step 3. Selection tag bar is visible and empty. > 8.Click on Preferences toolitem > ASSERT: Property Show selection tag bar property is unchecked -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18112) vpe version should be 3.6, not 3.5.100

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18112?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-18112: ------------------------------------------------ {quote}this must be done for CR1 imo.{quote} of course, will do it during codefreeze > vpe version should be 3.6, not 3.5.100 > -------------------------------------- > > Key: JBIDE-18112 > URL: https://issues.jboss.org/browse/JBIDE-18112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.2.0.CR1 > > > As VPE for Luna includes new features/plugins [1] it should be upversioned to 3.6, not left as a maintenance version 3.5.100. > [1] http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... > New IUs include: > * org.jboss.tools.vpe.browsersim.debugger > * org.jboss.tools.vpe.browsersim.javafx.mock > * org.jboss.tools.vpe.preview > * org.jboss.tools.vpe.preview.core > * org.jboss.tools.vpe.preview.editor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18112) vpe version should be 3.6, not 3.5.100

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18112?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18112: ---------------------------------------- Priority: Blocker (was: Major) > vpe version should be 3.6, not 3.5.100 > -------------------------------------- > > Key: JBIDE-18112 > URL: https://issues.jboss.org/browse/JBIDE-18112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.2.0.CR1 > > > As VPE for Luna includes new features/plugins [1] it should be upversioned to 3.6, not left as a maintenance version 3.5.100. > [1] http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... > New IUs include: > * org.jboss.tools.vpe.browsersim.debugger > * org.jboss.tools.vpe.browsersim.javafx.mock > * org.jboss.tools.vpe.preview > * org.jboss.tools.vpe.preview.core > * org.jboss.tools.vpe.preview.editor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18112) vpe version should be 3.6, not 3.5.100

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18112?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18112: --------------------------------------------- this must be done for CR1 imo. trivial to do with mvn tycho version plugin. > vpe version should be 3.6, not 3.5.100 > -------------------------------------- > > Key: JBIDE-18112 > URL: https://issues.jboss.org/browse/JBIDE-18112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.2.0.CR1 > > > As VPE for Luna includes new features/plugins [1] it should be upversioned to 3.6, not left as a maintenance version 3.5.100. > [1] http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... > New IUs include: > * org.jboss.tools.vpe.browsersim.debugger > * org.jboss.tools.vpe.browsersim.javafx.mock > * org.jboss.tools.vpe.preview > * org.jboss.tools.vpe.preview.core > * org.jboss.tools.vpe.preview.editor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16067) [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16067?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-16067. ---------------------------------- Resolution: Out of Date The restorable plugins feature now always adds a record to the config.xml so this request is no longer valid > [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16067 > URL: https://issues.jboss.org/browse/JBIDE-16067 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.0.CR1 > > > Invoking the plugin discovery dialog on the feature Add button creates the impression that every plugin must modify config.xml. We should move add plugin functionality elsewhere on the config.xml editor such as a tool bar or a section on its own and let the add/remove buttons do only xml manipulation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16067) [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16067?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16067: --------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.3.x) > [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16067 > URL: https://issues.jboss.org/browse/JBIDE-16067 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Priority: Minor > Fix For: 4.2.0.CR1 > > > Invoking the plugin discovery dialog on the feature Add button creates the impression that every plugin must modify config.xml. We should move add plugin functionality elsewhere on the config.xml editor such as a tool bar or a section on its own and let the add/remove buttons do only xml manipulation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16067) [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16067?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-16067: ------------------------------------ Assignee: Gorkem Ercan > [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16067 > URL: https://issues.jboss.org/browse/JBIDE-16067 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.0.CR1 > > > Invoking the plugin discovery dialog on the feature Add button creates the impression that every plugin must modify config.xml. We should move add plugin functionality elsewhere on the config.xml editor such as a tool bar or a section on its own and let the add/remove buttons do only xml manipulation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16067) [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16067?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16067: --------------------------------- Summary: [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button (was: Plug-in Discovery dialog should not be invoked through Feature Add button) > [Config Editor] Plug-in Discovery dialog should not be invoked through Feature Add button > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16067 > URL: https://issues.jboss.org/browse/JBIDE-16067 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Priority: Minor > Fix For: 4.3.x > > > Invoking the plugin discovery dialog on the feature Add button creates the impression that every plugin must modify config.xml. We should move add plugin functionality elsewhere on the config.xml editor such as a tool bar or a section on its own and let the add/remove buttons do only xml manipulation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 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 August 2014