[JBoss JIRA] (JBDS-3126) For JBDS 8.0.0.CR1: Code Freeze + Branch
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3126?page=com.atlassian.jira.plugin.... ]
Mickael Istria reassigned JBDS-3126:
------------------------------------
Assignee: Mickael Istria
> For JBDS 8.0.0.CR1: Code Freeze + Branch
> ----------------------------------------
>
> Key: JBDS-3126
> URL: https://issues.jboss.org/browse/JBDS-3126
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 8.0.0.CR1
>
>
> For JBDS 8.0.0.CR1: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3126) For JBDS 8.0.0.CR1: Code Freeze + Branch
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3126?page=com.atlassian.jira.plugin.... ]
Mickael Istria resolved JBDS-3126.
----------------------------------
Resolution: Done
> For JBDS 8.0.0.CR1: Code Freeze + Branch
> ----------------------------------------
>
> Key: JBDS-3126
> URL: https://issues.jboss.org/browse/JBDS-3126
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 8.0.0.CR1
>
>
> For JBDS 8.0.0.CR1: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18293) New seam with new version is not selected as a default runtime envirnment for its version
by Radoslav Rábara (JIRA)
Radoslav Rábara created JBIDE-18293:
---------------------------------------
Summary: New seam with new version is not selected as a default runtime envirnment for its version
Key: JBIDE-18293
URL: https://issues.jboss.org/browse/JBIDE-18293
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: seam2
Affects Versions: 4.2.0.CR1
Reporter: Radoslav Rábara
Fix For: 4.2.0.CR1
If there is a seam runtime environment, then there has to be also defined a default runtime environment for its version.
However, when a new seam is being added, which has a version that has not defined runtime environment, then the seam will be added but it will not be checked (marked as default for its version).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18292) HTML5 Kitchesink database is not expandable in Hibernate Configuration Console
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-18292:
------------------------------------
Summary: HTML5 Kitchesink database is not expandable in Hibernate Configuration Console
Key: JBIDE-18292
URL: https://issues.jboss.org/browse/JBIDE-18292
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.2.0.CR1
Environment: JBDS 8.0.0.CR1a
Reporter: Jiri Peterka
There is no connection defined in JPA project
but in persistence.xml there is
<jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source>
which is defined in kitchensink-quickstart-ds.xml
as
<connection-url>jdbc:h2:mem:jboss-as-kitchensink-html5-mobile-quickstart;DB_CLOSE_ON_EXIT=FALSE;DB_CLOSE_DELAY=-1</connection-url>
{code}
org.hibernate.HibernateException: HHH000152: JDBC URL was not specified by property hibernate.connection.url
at org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl.configure(DriverManagerConnectionProviderImpl.java:122)
at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:208)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:85)
at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:71)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2270)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2262)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:214)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:127)
at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-14662) Hibernate configuration view should gracefully handle error caused by multiple persistence.xml
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14662?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-14662.
--------------------------------
Verified with JBDS 8.0.0.CR1a
> Hibernate configuration view should gracefully handle error caused by multiple persistence.xml
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-14662
> URL: https://issues.jboss.org/browse/JBIDE-14662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, hibernate
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1a,64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.2.0.CR1
>
>
> When importing HTML5 project form Central, Hibernate console isn't properly configured and cannot be expanded and used without errors.
> {code}
> javax.persistence.PersistenceException: No name provided and several persistence units found
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:337)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.hibernate.console.ConfigurationFactory.buildJPAConfiguration(ConfigurationFactory.java:218)
> at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:161)
> at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:96)
> at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:240)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
> at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:237)
> at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:188)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:42)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18291) Null Pointer Exception when opening HTML5 project's persistence.xml
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18291?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-18291:
---------------------------------
Affects Version/s: 4.2.0.CR1
> Null Pointer Exception when opening HTML5 project's persistence.xml
> -------------------------------------------------------------------
>
> Key: JBIDE-18291
> URL: https://issues.jboss.org/browse/JBIDE-18291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.CR1
> Reporter: Jiri Peterka
>
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.getImage(AbstractItemStructuredStateProviderManager.java:158)
> at org.eclipse.jpt.common.ui.internal.navigator.NavigatorLabelProvider.getImage(NavigatorLabelProvider.java:65)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.findImage(NavigatorContentServiceLabelProvider.java:197)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getColumnImage(NavigatorContentServiceLabelProvider.java:105)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getImage(NavigatorContentServiceLabelProvider.java:98)
> at org.eclipse.ui.internal.navigator.resources.workbench.TabbedPropertySheetTitleProvider.getImage(TabbedPropertySheetTitleProvider.java:65)
> at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.refreshTitleBar(TabbedPropertySheetPage.java:850)
> at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.setInput(TabbedPropertySheetPage.java:754)
> at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.selectionChanged(TabbedPropertySheetPage.java:556)
> at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:365)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:218)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:122)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$1(SelectionService.java:112)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService$3.selectionChanged(SelectionService.java:80)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:166)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:163)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:160)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:272)
> at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:269)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:338)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:352)
> at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:126)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1217)
> at org.eclipse.ui.navigator.CommonViewer.handlePostSelect(CommonViewer.java:470)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1243)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17707) Selection tag bar is always hidden when switching from Source to Visual
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17707?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-17707.
--------------------------------------------
Resolution: Done
> 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: Ilya Buziuk
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR2
>
>
> 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, 7 months