[JBoss JIRA] Created: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
3:56 p.m.
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Alexey Kazakov
Fix For: 3.3.0.M1
Attachments: screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:17 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8306:
--------------------------------------
There is another problem. When this node gets selected exception is reported in Error Log
View:
{noformat}org.eclipse.core.runtime.CoreException: No property tester contributes a
property org.eclipse.core.resources.open to type class
org.jboss.tools.jsf.model.pv.JSFProjectsRoot
at
org.eclipse.core.internal.expressions.TypeExtensionManager.getProperty(TypeExtensionManager.java:123)
at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:96)
at
org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29)
at
org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:21)
at
org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29)
at
org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at
org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:53)
at
org.eclipse.ui.internal.navigator.NavigatorPlugin$Evaluator.run(NavigatorPlugin.java:245)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.ui.internal.navigator.NavigatorPlugin.safeEvaluate(NavigatorPlugin.java:260)
at
org.eclipse.ui.internal.navigator.actions.CommonActionProviderDescriptor.isEnabledFor(CommonActionProviderDescriptor.java:235)
at
org.eclipse.ui.internal.navigator.actions.CommonActionDescriptorManager.addProviderIfRelevant(CommonActionDescriptorManager.java:258)
at
org.eclipse.ui.internal.navigator.actions.CommonActionDescriptorManager.findRelevantActionDescriptors(CommonActionDescriptorManager.java:235)
at
org.eclipse.ui.navigator.NavigatorActionService.fillActionBars(NavigatorActionService.java:248)
at
org.eclipse.ui.navigator.CommonNavigatorManager.selectionChanged(CommonNavigatorManager.java:222)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
at
org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2162)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1190)
at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:478)
at
org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1220)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:228)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:222)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:389)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407){noformat}
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.0.M1
Attachments: screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:03 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Dmitry Geraskov updated JBIDE-8306:
-----------------------------------
Component/s: JSF
struts/shale
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.0.M1
Attachments: screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:47 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich updated JBIDE-8306:
-----------------------------------------
Attachment: ProjectExplorer.png
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.0.M1
Attachments: ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-8306:
----------------------------------------------
Our addition to Project Explorer should since long ago look as in ProjectExplorer.png.
However, at some moment, root node of our presentation was made adaptable to IProject, and
after that Eclipse would not call our label provider for that node but used standard
resource lable provider, which made two nodes identical.
The way (2) - Split it in several nodes - is also simple to implement, but it would mix
our artificial nodes with project folders and nodes of third parties in a random way. I
still think that it is good to keep our stuff under specific root node; compare with nodes
'Java Resources' and 'Java Script Resources'.
I agree to hide WebContent from our nodes, but would defend web.xml node since it gives
our own representation of web descriptor which some customers may like better than what is
provided by WTP.
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.0.M1
Attachments: ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:12 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8306:
--------------------------------------
What would be the appropriate name for this node?
JSF/Struts Capabilities
Web Capabilities
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.0.M1
Attachments: ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:16 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8306:
--------------------------------------
Now it is shown like "Web Resources"
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.0.M1
Attachments: ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich updated JBIDE-8306:
-----------------------------------------
Fix Version/s: 3.2.1
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:14 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich resolved JBIDE-8306.
------------------------------------------
Resolution: Done
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Vlado Pakan updated JBIDE-8306:
-------------------------------
Attachment: jsfproject.png
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: jsfproject.png, ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-8306:
----------------------------------
Fix Version/s: 3.3.x
(was: 3.2.1.M1)
(was: 3.3.0.M1)
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.x
Attachments: jsfproject.png, ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-8306:
----------------------------------------------
I think that what Vlado found is another bug/feature added by a third party. We do not add
child 'Web Resources : WebContent' with same content as 'WebContent'.
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.3.x
Attachments: jsfproject.png, ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Alexey Kazakov resolved JBIDE-8306.
-----------------------------------
Fix Version/s: 3.2.1.M1
3.3.0.M1
(was: 3.3.x)
Resolution: Done
Ok. Then let's resolve the issue. We should open a separate issue for that upstream
bug.
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: jsfproject.png, ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:03 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent
[
https://issues.jboss.org/browse/JBIDE-8306?page=com.atlassian.jira.plugin...
]
Vlado Pakan closed JBIDE-8306.
------------------------------
Separated issue https://issues.jboss.org/browse/JBIDE-8839 created.
Project Explorer has child node looking exactly the same as parent
------------------------------------------------------------------
Key: JBIDE-8306
URL: https://issues.jboss.org/browse/JBIDE-8306
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, struts/shale
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Labels: usability
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: jsfproject.png, ProjectExplorer.png, screenshot68.png
Project with Enabled JSF/Struts capabilities contains child node that looks exactly the
same as parent in Project Explorer view
!screenshot68.png!
It contains information about configuration (web deployment descriptor, JSF/Struts
configuration, taglibs, beans and etc) and resources from web root.
We have several way to give it a better look and usability:
1. (simple) find a right name/icon for it to describe content in it and remove redundant
nodes from it (WebContent and web deployment descriptor, for instance, are already present
under project in Projects Explorer)
2. Split it in several nodes to be shown as Project node siblings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5450
days inactive
5541
days old
jbosstools-issues@lists.jboss.org
13 comments
5 participants
participants (5)
-
Alexey Kazakov (JIRA) -
Denis Golovin (JIRA)
-
Dmitry Geraskov (JIRA)
-
Viacheslav Kabanovich (JIRA)
-
Vlado Pakan (JIRA)