[jbosstools-issues] [JBoss JIRA] (JBIDE-15115) No confirmation dialog is reported back to user after embedding cartridges

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JBIDE-15115:
-------------------------------------------------

weiwei jiang <wjiang at redhat.com> made a comment on [bug 980928|https://bugzilla.redhat.com/show_bug.cgi?id=980928]

(In reply to Andre Dietisheim from comment #5)
> (In reply to weiwei jiang from comment #4)
> > test on jbosstool 4.1.0 CR1a and it works, thx
> 
> thanks for confirming weiwei
> 
> > And when add some non-supported cartridges for scalable app, the result of
> > supported cartridge will not display.
> 
> did I read you right, if you try to embed/create unsupported cartridges you
> wont get any report about it?
> Is this expected or should a dialog pop up?

For example, I embed mysql(supported) & phpmyadmin(unsupported) cartridge to a scalable php application, so it will pop up a dialog and display "phpmyadmin unsupported for scalable application", but it wont display the username&password of mysql, so is it expected?
                
> No confirmation dialog is reported back to user after embedding cartridges
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-15115
>                 URL: https://issues.jboss.org/browse/JBIDE-15115
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.1.0.CR1
>            Reporter: Stefan Bunciak
>            Assignee: Max Rydahl Andersen
>            Priority: Blocker
>              Labels: respin-a
>             Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
>
> No error log is put to Error log view neither to workspace log when experiencing this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira