[
https://jira.jboss.org/jira/browse/JBIDE-6178?page=com.atlassian.jira.plu...
]
Darryl Miles commented on JBIDE-6178:
-------------------------------------
Just to be clear here. I am simply requesting the addition of the word "JBoss"
at the front of the existing feature/plugins description name, this would be affect those
things added into the "Maven Support" and "Data Services" tree.
I have no complaint with the "All JBoss Tools" heading, as it is clear when
using all views, that the vendor is JBoss.
I am not even requesting you re-group or change the groupings of the items. Only a simple
clarification to on lookers that this item has been contributed (into an existing group)
from the vendor JBoss. As per the defacto guidelines in the original bug comment, if you
are creating your own grouping, then that group name would be prefixed with the word
"JBoss" and there would not be any need to also put the word JBoss
releng update site, feature naming conventions
----------------------------------------------
Key: JBIDE-6178
URL:
https://jira.jboss.org/jira/browse/JBIDE-6178
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: updatesite
Affects Versions: 3.1.0.GA
Reporter: Darryl Miles
Assignee: Nick Boldt
Priority: Minor
Fix For: 3.1.x, 3.2.next
Attachments: 20100413_jboss_example1.PNG
Please consider the impact of users using the "All Update Site" view when
installing JBoss plugins.
Some rules to consider:
1) If JBoss creates a new top-level group (which consists entirely of JBoss features)
then that top-level name should begin with the word "JBoss".
2) If JBoss reuses a top-level group which belongs to another vendor (for which JBT is
built on top of, for example BIRT/Maven/DTP) then you can reuse the top-level group name
of the outside vendor, but ensure your features underneath are prefixed with the word
"JBoss"."
In enclose a screen grab from 3.1.0.GA which indicates the discrepancy; BIRT is following
the above rules, but "Maven Support" is not (and also "Data Services"
top level group is not).
The "All in one JBoss" top-level group doesn't really need to follow this
convention, since the top level group clearly indicates it is from JBoss and entirely
contains JBoss features and those features are a duplicated entrypoint for installation
(i.e. each feature also exist somewhere else in the "features to install" tree
view). The ambigiouty is over such names as "Maven Support" and "Data
Services" in the context of the "all update site view" from the drop-down
filter at the top of the page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira