[
https://jira.jboss.org/jira/browse/JBIDE-4859?page=com.atlassian.jira.plu...
]
Nick Boldt updated JBIDE-4859:
------------------------------
Summary: Create new categories for JBT/JBDS update sites (was: JBT Update site
has uncategorized features)
Component/s: Build/Releng
Fix Version/s: (was: 3.1.0.M4)
Description: Renamed to capture current thrust of issue: should we have more
categories than we currently do on the update site? Expose more/less features? This is a
branding/marketing/ease of use question, so for now I'm bouncing it over to Max for
comments. (was: Checking the latest JBT 3.1.0.M3 build #H262, I see a number of
uncategorized features. Some of these are acceptable; for example, Freemarker and
JMX's source features are not exposed as categorized features (only their SDKs are).
This is good.
I also see that JBoss Profiler is NOT listed on the categorized site (as it was
deliberately removed from the list - but since it's still being built, it's still
available, just hidden). This too is good.
However, these subfeatures are also not listed under the categorized site:
* Common Tools for jBPM 3 and jBPM 4
* Flow Language Common Tools
* jBPM 4 Graphical Editor and Tools
Should any of those be listed under the main JBT site category?
(Also, "featureName" is most likely the two Maven source features... I'll
fix that.)
)
Assignee: Max Rydahl Andersen (was: Koen Aers)
Create new categories for JBT/JBDS update sites
-----------------------------------------------
Key: JBIDE-4859
URL:
https://jira.jboss.org/jira/browse/JBIDE-4859
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.M3
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Attachments: screenshot-1.jpg, Screenshot-1.png, Screenshot-2.png
Renamed to capture current thrust of issue: should we have more categories than we
currently do on the update site? Expose more/less features? This is a
branding/marketing/ease of use question, so for now I'm bouncing it over to Max for
comments.
--
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