[jboss-jira] [JBoss JIRA] Commented: (AS7-735) Failed OSGi deployments still show as .deployed in hotdeploy folder
[
https://issues.jboss.org/browse/AS7-735?page=com.atlassian.jira.plugin.sy...
]
David Bosschaert commented on AS7-735:
--------------------------------------
{quote}What you are probably looking for is a set of one deployment, with a requirement
that all deployments in the set (i.e. just the one) can be started after all deployments
in the set have been installed.{quote}
Yes, this is _exactly_ what I'm looking for :)
I'm thinking of two use cases:
1. A developer is trying stuff out. He's only doing simple stuff and deploys his
bundles one by one. If a dependency is missing he expects the deployment to show up as
failed (rather than as deployed with a bit resolution stack trace as we have now).
2. For some deployments users may opt to have the deployments folder prepopulated with all
the bundles they want to deploy and then start AS7. In this case all of the bundles in the
folder define a single deployment set.
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