[jbosstools-issues] [JBoss JIRA] (JBTIS-396) JBoss Central doesn't recognise that a category item is already installed

[Paul Leacu (JIRA)]

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

Paul Leacu closed JBTIS-396.
----------------------------
    Resolution: Won't Fix


I appreciate the feedback - however this would appear to be a Mylyn enhancement request when all is considered.  There's really nothing that can be done on our end.  Thanks for the input.

> JBoss Central doesn't recognise that a category item is already installed
> -------------------------------------------------------------------------
>
>                 Key: JBTIS-396
>                 URL: https://issues.jboss.org/browse/JBTIS-396
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>          Components: distribution
>            Reporter: Michelle Murray
>            Assignee: Paul Leacu
>         Attachments: dv1.png, dv2.png
>
>
> I have JBDS 8.0.2 installed.
> In JBoss Central Software/Update tab, I enabled Early Access. I then selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. I chose to only install ModeShape Client and followed the install through including restarting JBDS.
> In JBoss Central Software/Update tab, 'JBoss Data Virtualization Developer' was still shown as uninstalled - as expected from JBTIS-363. I selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. ModeShape Client is listed and check box autoselected along with all of the Teiid items as available to install. BUT I just installed it!?
> 1) I chose to only install the ModeShape Client again but then get an error message "Cannot complete the request.  See the error log for details."
> 2) So I chose to install all, including ModeShape Client, and the install proceeds to the next window without the error message but is listing that it will install ModeShape Client again.
> As a user, this looks like a bug to me.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)