1:55 p.m.
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.jboss.org/browse/JBIDE-6368
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 3.2.next
Reporter: John Verhaeg
Assignee: Nick Boldt
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:25 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://jira.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin.s...
]
Nick Boldt updated JBIDE-6368:
------------------------------
Attachment: nested-categories-p2-update-site.png
Nested categories are now technically possible. Proof in attached screenshot from WTP
update site.
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.jboss.org/browse/JBIDE-6368
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 3.2.next
Reporter: John Verhaeg
Assignee: Nick Boldt
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:50 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://jira.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6368:
---------------------------------------
Fix Version/s: 3.2.0.M2
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.jboss.org/browse/JBIDE-6368
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 3.2.x
Reporter: John Verhaeg
Assignee: Nick Boldt
Fix For: 3.2.0.M2
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:58 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://jira.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin.s...
]
Denis Golovin updated JBIDE-6368:
---------------------------------
Fix Version/s: 3.2.0.Beta
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.jboss.org/browse/JBIDE-6368
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 3.2.x
Reporter: John Verhaeg
Assignee: Nick Boldt
Fix For: 3.2.0.M2, 3.2.0.Beta
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:02 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://jira.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin.s...
]
Denis Golovin updated JBIDE-6368:
---------------------------------
Fix Version/s: (was: 3.2.0.M2)
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.jboss.org/browse/JBIDE-6368
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 3.2.x
Reporter: John Verhaeg
Assignee: Nick Boldt
Fix For: 3.2.0.Beta
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://jira.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin.s...
]
Nick Boldt updated JBIDE-6368:
------------------------------
Priority: Optional (was: Major)
Bump down to optional as this arguably doesn't provide BETTER service, only
DIFFERENT.
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.jboss.org/browse/JBIDE-6368
Project: Tools (JBoss Tools)
Issue Type: Task
Components: updatesite
Affects Versions: 3.2.x
Reporter: John Verhaeg
Assignee: Nick Boldt
Priority: Optional
Fix For: 3.2.0.Beta
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://jira.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-6368:
--------------------------------
Fix Version/s: 3.2.0.Beta2
(was: 3.2.0.Beta1)
Priority: Critical (was: Optional)
should be looked at before CR/GA.
Could be done with different catgories/uncategorized items or by creating proper
"uber" features. Find advantages/disadvantages of the two.
i.e. Uber Features apparently forces upgrades to only be done via the uber feature not
subfeature - true/false ?
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.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: Critical
Fix For: 3.2.0.Beta2
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:14 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://jira.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-6368:
--------------------------------
Fix Version/s: 3.2.0.CR1
(was: 3.2.0.Beta2)
Priority: Blocker (was: Critical)
Should nest categories in update site
-------------------------------------
Key: JBIDE-6368
URL: https://jira.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
3:12 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-6368:
-----------------------------------
True. If you install a feature A which contains B and C, and C bring in feature D, then
you cannot just update feature B, C, or D without also updating A. The whole stack must be
uninstalled as a unit, or updated as a unit.
(You can uninstall the stack then install just B, C, or D, if you want, but if you as soon
as you then install A, you cannot update it without also updating its children, nor can
you update its children independently of the parent, because the parent depends on a
specific set of versioned children.)
Uberfeatures are BAD.
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
8:02 p.m.
New subject: [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
8:17 p.m.
New subject: [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:
--------------------------------------
using p2.inf I guess we can create any hierarchy in update site see as example p2.inf for
product build. I haven't tried that yet but here is an example of category I defined
for JBDS Product root feature
units.1.id=com.jboss.jbds.all.category
units.1.version=$version$
units.1.provides.1.namespace=org.eclipse.equinox.p2.iu
units.1.provides.1.name=com.jboss.jbds.all.category
units.1.provides.1.version=$version$
units.1.properties.1.name=org.eclipse.equinox.p2.type.category
units.1.properties.1.value=true
units.1.properties.2.name=org.eclipse.equinox.p2.name
units.1.properties.2.value=JBoss Developer Studio 4
units.1.requires.1.namespace=org.eclipse.equinox.p2.iu
units.1.requires.1.name=com.jboss.jbds.all
units.1.requires.1.range=[$version$,$version$]
units.1.requires.1.greedy=true
It is just a awkward way to define xml structure. I guess if you can look at content.xml
for attached example we can figure out how to define hierarchy of categories
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
10:17 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-6368:
---------------------------------------
Fix Version/s: LATER
(was: 3.2.0.CR1)
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 Rydahl Andersen
Priority: Blocker
Fix For: LATER
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
10:17 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6368:
--------------------------------------------
I don't really see any way of handling this well in eclipse p2.
Plugins need to be in several categories since there are plugins that falls into multiple
i.e. Hibernate Tools is both relevant for JEE and for Data Services but if we only put it
in Data Services then it becomes a maze to actually figure out what features to install
for our major use case (JEE/Web developement) since they would not need/want to install
i.e. all of Teiid....and vice versa.
I'm pushing is off for now unless someone got a great idea on how to fix it.
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 Rydahl Andersen
Priority: Blocker
Fix For: LATER
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
12:33 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-6368:
-----------------------------------
Rather than worrying about nesting, why don't we look at creating a discovery UI like
what Mylyn has to present users with a collection of useful "Bundles of
Functionality" with icons and descriptive text... and a cleaner/simpler install
experience.
http://wiki.eclipse.org/Mylyn/Discovery#Discovery_UI
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 Rydahl Andersen
Priority: Blocker
Fix For: LATER
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
2:35 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6368:
--------------------------------------------
those still seem to relate to individual features and not group of features - and how does
that help Eclipse users wanting to install jboss tools ?
they wont have any discovery UI to use beyond P2...
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 Rydahl Andersen
Priority: Blocker
Fix For: LATER
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
2:53 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-6368:
-----------------------------------
You could provide the categories as installable chunks:
App Development
Data Services
Test & Performance
Maven
Cloud
SOA
Web
Reporting
Then, each can be clearly articulated w/ an icon & description.
We can also expose the features which provide their own branding icon already (Teiid,
Hibernate, Seam, etc.) and have those as installable chunks too. (My assumption being that
if they have unique branding they had a user community already before being collected into
JBT, and therefore some people may only want to install that piece of functionality,
without getting a bunch of other stuff along for the ride.)
The point is simply to provide a *prettier* UI which simplifies the experience / reduces
the # of clicks / categorizes user stories into useful (and reasonably fine- or
coarse-grained buckets).
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 Rydahl Andersen
Priority: Blocker
Fix For: LATER
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
2:56 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6368:
--------------------------------------------
again - how do you do that on a base eclipse ? you would still need to install some
"Jboss tools discovery"-plugin for this to work...,right?
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 Rydahl Andersen
Priority: Blocker
Fix For: LATER
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
3:50 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6368) Should nest categories in update site
[
https://issues.jboss.org/browse/JBIDE-6368?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-6368:
-----------------------------------
Good point - I think you have to provide a plugin which exploits the discovery UI, install
that, THEN be able to "discover" more stuff to add to your Eclipse.
If we bundled the usage tracker w/ such a plugin and called it the JBoss Tools
"installer", we could then have everyone after that point installing using a
prettier UI.
Otherwise... I guess this isn't really doable unless this plugin gets bundled in with
Fedora 15's Eclipse 3.6.2 spin. It could also provide items on the Eclipse Help menu
for reporting issues in JIRA or opening support forums. *shrug*
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 Rydahl Andersen
Priority: Blocker
Fix For: LATER
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
5045
days inactive
5281
days old
jbosstools-issues@lists.jboss.org
17 comments
5 participants
participants (5)
-
Denis Golovin (JIRA) -
John Verhaeg (JIRA)
-
Max Andersen (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)