[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-6368:
--------------------------------------
I wouldn't say so, nick. You cannot update only A because all included features gonna
be updated, but you sure can update children without updating parent. To make that happen
children should be available as root features in eclipse configuration. I your case if you
have A installed as root feature and D installed as root you sure can update D without
updating A depends on version restriction.
Because you would have in eclipse configuration details hierarchy like this:
A
B
C
D
D
If you have C installed as root feature you can update only D or only C and D, and your
hierarchy in eclipse configuration would be
A
B
C
D
C
D
D
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://issues.jboss.org/browse/JBIDE-6368
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 3.2.x
Reporter: John Verhaeg
Assignee: Max Andersen
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: nested-categories-p2-update-site.png
As discussed somewhat in JBIDE-4859, it seems like we should nest our categories in our
update site. So, instead of having lots of sibling categories for the various tools in
JBT alongside a sibling "All JBoss Tools" category, the latter should be
promoted to a parent category for the others (dropping the "All" prefix). For
example:
- JBoss Tools
- SOA Development
- JBoss ESB Tools
- Drools Core
...
- Data Services
- Hibernate
- ModeShape
- Smooks
- Teiid Data Tools Connectivity
- Teiid Designer Design-Time
- Teiid Designer Runtime
BTW, IMO having features in multiple categories blows. I don't like seeing this with
other Eclipse projects either. Just my 2 cents.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira