[jbosstools-issues] [JBoss JIRA] (JBDS-2059) Confusing Mylyn features names and descriptions

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676798#comment-12676798 ] 

Nick Boldt edited comment on JBDS-2059 at 3/14/12 11:57 AM:
------------------------------------------------------------

com.jboss.jbds.mylyn.feature/feature.xml - "Mylyn (Selected)":
{code}
Contains Mylyn 3.6 including support for Bugzilla, CVS, SVN, JIRA, Bamboo, Crucible, Fisheye, Java Development, Plug-In Development and Wikitext (Selected).
Features selected by Red Hat for use with JBoss Developer Studio.
{code}

com.jboss.jbds.git.feature/feature.xml - "Git Integration (Selected)":
{code}
Contains eGit, including integration for Mylyn and GitHub (Selected).
Features selected by Red Hat for use with JBoss Developer Studio.
{code}
and includes/requires the mylyn feature:
{code}
      <import feature="com.jboss.jbds.mylyn.feature" version="1.0.0" match="greaterOrEqual"/>
{code}

Does that make it more clear what's what and what's included? Is this new approach a more obvious install path? 

eg1., user wants Mylyn: user selects the Mylyn feature.
eg2., user wants Git: user selects the Git feature (which now includes Mylyn too).


                
      was (Author: nickboldt):
    com.jboss.jbds.mylyn.feature/feature.xml:
{code}
Contains Mylyn 3.6 including support for Bugzilla, CVS, SVN, JIRA, Bamboo, Crucible, Fisheye, Java Development, Plug-In Development and Wikitext (Selected).
Features selected by Red Hat for use with JBoss Developer Studio.
{code}

com.jboss.jbds.git.feature/feature.xml:
{code}
Contains eGit, including integration for Mylyn and GitHub (Selected).
Features selected by Red Hat for use with JBoss Developer Studio.
{code}
and includes/requires the mylyn feature:
{code}
      <import feature="com.jboss.jbds.mylyn.feature" version="1.0.0" match="greaterOrEqual"/>
{code}

Does that make it more clear what's what and what's included? Is this new approach a more obvious install path? 

eg1., user wants Mylyn: user selects the Mylyn feature.
eg2., user wants Git: user selects the Git feature (which now includes Mylyn too).


                  
> Confusing Mylyn features names and descriptions
> -----------------------------------------------
>
>                 Key: JBDS-2059
>                 URL: https://issues.jboss.org/browse/JBDS-2059
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Build
>    Affects Versions: 5.0.0.Beta1
>            Reporter: Lucia Jelinkova
>            Assignee: Nick Boldt
>             Fix For: 5.0.0.Beta2
>
>
> When I want to install Mylyn from extras and I click on the Mylyn feature, there is the following description:
> {quote}
> Contains Mylyn 3.6 including support for Bugzilla, CVS, eGit, SVN, JIRA, Bamboo, Crucible, Fisheye, Java Development, Plug-In Development and Wikitext (Selected). 
> Features selected by Red Hat for use with JBoss Developer Studio.
> {quote}
> However, installing the feature does not install the eGit integration as promised. One needs to install one more feature called _Git integration_. The name is confusing because it does not suggest that it is integration with Mylyn. Moreover, the description says the following:
> {quote}
> Contains Mylyn and GitHub integration (Selected).
> Features selected by Red Hat for use with JBoss Developer Studio.
> {quote}
> This is confusing - is it the integration with Git or GitHub? Actually, both. 
> Suggestions:
> # Change the description of Mylyn feature so that it reflects real connectors installed
> # Change the name of _Git integration_ to _Mylyn integration with Git and GitHub_ or something similar
> # Change the description of _Git integration_ to _Contains Mylyn integration with Git and GitHub_ or something similar

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira