[jboss-jira] [JBoss JIRA] Commented: (AS7-735) Failed OSGi deployments still show as .deployed in hotdeploy folder

[David Bosschaert (JIRA)]

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

David Bosschaert commented on AS7-735:
--------------------------------------

I think this is not intuitive, because you only really get to know whether there are any issues once the bundle is resolved. Just to compare with EE deployments. If there are any jboss-modules dependencies listed in an EJB-Jar these and these are missing in the deployment of that EJB-Jar is marked as failed - this is much more useful IMHO.

> Failed OSGi deployments still show as .deployed in hotdeploy folder
> -------------------------------------------------------------------
>
>                 Key: AS7-735
>                 URL: https://issues.jboss.org/browse/AS7-735
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: OSGi
>    Affects Versions: 7.0.0.CR1
>            Reporter: David Bosschaert
>            Assignee: Jason Greene
>
> When deploying a bundle in AS7 in the hotdeploy directory that has missing dependencies and therefore fails the OSGi resolution process, the deployment still shows up as deployed successfully (a .deployed file appears). 
> I think it should be marked as .failed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira