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

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Tue May 10 10:53:21 EDT 2011


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

Thomas Diesler edited comment on AS7-735 at 5/10/11 10:53 AM:
--------------------------------------------------------------

A bundle marked as .deployed reaches Bundle.INSTALLED state
A failure to start the bundle does not mean that the bundle failed to get installed.

      was (Author: thomas.diesler):
    A bundle marked as .deployed reaches Bundle.INSTALLED state 
  
> 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


More information about the jboss-jira mailing list