[jboss-jira] [JBoss JIRA] (AS7-5857) OSGi Resolution failure should be logged as an error
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Tue Nov 6 17:12:18 EST 2012
[ https://issues.jboss.org/browse/AS7-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler resolved AS7-5857.
---------------------------------
Resolution: Rejected
It is perfectly ok for a bundle to not resolve. The MODULE phase is deferred and the bundle deployment can be triggered to continue through the phases when the condition is resolved that caused the resolution failure.
> OSGi Resolution failure should be logged as an error
> ----------------------------------------------------
>
> Key: AS7-5857
> URL: https://issues.jboss.org/browse/AS7-5857
> Project: Application Server 7
> Issue Type: Feature Request
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Reporter: David Bosschaert
> Assignee: Thomas Diesler
>
> When deploying an OSGi bundle that fails to resolve, currently only a warning is logged, this should really be an ERROR.
> {code}13:21:31,275 WARN [org.jboss.as.osgi] (MSC service thread 1-13) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=javax.servlet, version=[2.1.0,3.0.0)},[TestOSGiHttpService:1.0.0]]]
> 13:21:31,275 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015970: Defer FIRST_MODULE_USE for TestOSGiHttpService_1.0.0.jar making it NEVER
> 13:21:31,305 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "TestOSGiHttpService_1.0.0.jar"{code}
> Additionally, the deployment is marked as 'deployed'. It would be better if it could be marked as 'failed'
--
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
More information about the jboss-jira
mailing list