[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6178) releng update site, feature naming conventions

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-6178:
---------------------------------------

    Fix Version/s: 3.1.x
                   3.2.next
         Assignee: Nick Boldt


Good points and I agree if we are sharing "namespace" we should prefix with JBoss for the subparts.

The reason for "All JBoss Tools" is so when using JBoss Tools Update site view that it does not get sorted into the middle of the possible options.

Don't know a good solution for that (beyond creating installable features that groups everything but then doesn't become managable by individual featuers)

> 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