[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21201:
-----------------------------------
Fix Version/s: (was: 4.3.1.Beta2)
> TernError: No type found at the given position.
> -----------------------------------------------
>
> Key: JBIDE-21201
> URL: https://issues.jboss.org/browse/JBIDE-21201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: tern 1.1.0
> Reporter: Pavol Srna
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Click on 'user' text within <h:inputText> tag
> 4. Press F3 key
> {code}
> tern.TernException: TernError: No type found at the given position.
> at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43)
> at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.TernException: TernError: No type found at the given position.
> at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21201:
----------------------------------------
[~vrubezhny] please file this issue to tern.java and post the link here.
> TernError: No type found at the given position.
> -----------------------------------------------
>
> Key: JBIDE-21201
> URL: https://issues.jboss.org/browse/JBIDE-21201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: tern 1.1.0
> Reporter: Pavol Srna
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Click on 'user' text within <h:inputText> tag
> 4. Press F3 key
> {code}
> tern.TernException: TernError: No type found at the given position.
> at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43)
> at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.TernException: TernError: No type found at the given position.
> at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20797) CCE on first start on clean install of CR1
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20797?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-20797:
----------------------------------------
This issues is fixed upstream. We are waiting for JBDS/JBT Target Platform update to include Mars.2 RC1 to resolve this issue for 4.3.1.Beta2.
> CCE on first start on clean install of CR1
> ------------------------------------------
>
> Key: JBIDE-20797
> URL: https://issues.jboss.org/browse/JBIDE-20797
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> clean install of eclipse JEE + CR1 jbosstools for mars.
> Get this error on startup on a clean workspace:
> {code}
> java.lang.ClassCastException: [Lorg.eclipse.swt.graphics.FontData; cannot be cast to java.lang.String
> at org.eclipse.ui.internal.themes.Theme$1.propertyChange(Theme.java:124)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:351)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:347)
> at org.eclipse.jface.preference.PreferenceConverter.setValue(PreferenceConverter.java:463)
> at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.ensurePreferenceStoreBackwardsCompatibility(JavaScriptPlugin.java:395)
> at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.start(JavaScriptPlugin.java:336)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
> at org.eclipse.osgi.container.Module.doStart(Module.java:571)
> at org.eclipse.osgi.container.Module.start(Module.java:439)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
> at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.editorOpened(JavaEditorTracker.java:157)
> at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.partOpened(JavaEditorTracker.java:152)
> at org.eclipse.ui.internal.WorkbenchPage$18.run(WorkbenchPage.java:4939)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartOpened(WorkbenchPage.java:4936)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$2.handleEvent(CompatibilityPart.java:121)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.basic.impl.PartImpl.setObject(PartImpl.java:410)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:131)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:99)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:494)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:458)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:724)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:396)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1166)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3234)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3149)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3131)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3126)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3090)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3071)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:436)
> at org.jboss.tools.central.JBossCentralActivator$6$1.run(JBossCentralActivator.java:411)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3281) Screencasts: Git
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3281?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3281:
---------------------------------
Fix Version/s: 9.1.0.CR1
(was: 9.1.0.Beta2)
> Screencasts: Git
> ----------------
>
> Key: JBDS-3281
> URL: https://issues.jboss.org/browse/JBDS-3281
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, requirements
> Reporter: Burr Sutter
> Assignee: Martin Malina
> Priority: Minor
> Fix For: 9.1.0.CR1
>
>
> As a Java EE developer, new to Eclipse + Git, I need educational, 5 minute screencasts on the most common uses of Git inside of Eclipse.
> Use cases include:
> 1) as a new member of the team, just having only installed JBDS, I need to add an element to the project
> assume a clone, add (or modify), commit, push workflow
> a- Getting started as a new member of an existing git project (I need to clone a repo, import the project, insure my facets/Maven are set correctly)
> b- navigate/browse an existing repository
> c- git add - for a newly added class or file
> d- git commit -a
> e- git push
> as a new member of the team, just having only installed JBDS, I need to resolve a pull request.
> 2) other scenarios
> - git init a current project that I have in my workspace (and should I move it outside of my workspace first)
> - git checkout for a specific branch - getting Maven and Eclipse Facets to properly recognize my newly checked out branch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3280) Screencasts: Java EE
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3280?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3280:
---------------------------------
Fix Version/s: 9.1.0.CR1
(was: 9.1.0.Beta2)
> Screencasts: Java EE
> --------------------
>
> Key: JBDS-3280
> URL: https://issues.jboss.org/browse/JBDS-3280
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, requirements
> Reporter: Burr Sutter
> Assignee: Martin Malina
> Priority: Minor
> Fix For: 9.1.0.CR1
>
>
> As a new Eclipse+Java EE developer, I need educational screencasts, around 5 minutes each that educate me on a specific Java EE development capabilities of JBDS.
> Use cases include:
> - JPA - how to add one, content-assist, relationships
> - database reverse engineering via DTP vs Forge
> - JAX-RS: creation of new endpoints, content-assist, tester - including the GET/POST/PUT/DELETE with JSON payloads
> - JAX-WS: creation of new endpoints, content-assist, tester
> - CDI special features
> - Servlets
> - JSF
> - deployment to localhost EAP
> - deployment to remove EAP
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3251) Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3251?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3251:
---------------------------------
Fix Version/s: 9.1.0.CR1
(was: 9.1.0.Beta2)
> Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3251
> URL: https://issues.jboss.org/browse/JBDS-3251
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: documentation, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Martin Malina
> Fix For: 9.1.0.CR1
>
>
> suggestions from F2F:
> |Maven Top 10 Use Cases| Import, multi-module, run on server, package vs install, update, adjust profiles, dependencies adds/removes|
> |Java EE Top 10 Use Cases JPA, db reveng, JAX-RS (including testing), CDI, content assist, Servlets, JSF, etc
> HTML5/Hybrid Mobile|
> |OpenShift v3| start, stop, deploy apps
> |eGit Top Use Cases|
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TOOLSDOC-703) Release Notes for 9.0.0 contain duplication and wrong text for known issue
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-703?page=com.atlassian.jira.plug... ]
Misha Ali resolved TOOLSDOC-703.
--------------------------------
Resolution: Done
> Release Notes for 9.0.0 contain duplication and wrong text for known issue
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-703
> URL: https://issues.jboss.org/browse/TOOLSDOC-703
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Affects Versions: 9.0.0
> Environment: Build Name: 23115, 9.0.0 Release Notes-9.0
> Build Date: 06-10-2015 14:28:25
> Topic ID: 44858-771229 [Latest]
> Reporter: Mustafa Musaji
> Assignee: Misha Ali
> Priority: Blocker
>
> Title: Known Issues
> Describe the issue:
> JBDS-3470: Toolbars + Icons unusable on UHD screens. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly.
> JBIDE-19633: Not able to create 'non-bare' repository in JBDS 8.1. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly.
> Suggestions for improvement:
> JBIDE-19633 has nothing to do with UHD and the line should be removed
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TOOLSDOC-703) Release Notes for 9.0.0 contain duplication and wrong text for known issue
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-703?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-703:
------------------------------------
Fixed and published: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu...
Thanks for reporting the issue, Mus!
> Release Notes for 9.0.0 contain duplication and wrong text for known issue
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-703
> URL: https://issues.jboss.org/browse/TOOLSDOC-703
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Affects Versions: 9.0.0
> Environment: Build Name: 23115, 9.0.0 Release Notes-9.0
> Build Date: 06-10-2015 14:28:25
> Topic ID: 44858-771229 [Latest]
> Reporter: Mustafa Musaji
> Assignee: Misha Ali
> Priority: Blocker
>
> Title: Known Issues
> Describe the issue:
> JBDS-3470: Toolbars + Icons unusable on UHD screens. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly.
> JBIDE-19633: Not able to create 'non-bare' repository in JBDS 8.1. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly.
> Suggestions for improvement:
> JBIDE-19633 has nothing to do with UHD and the line should be removed
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months