[
https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pontus Amberg updated SLING-1737:
---------------------------------
Attachment: debug.zip
testSemiRandomInstall still fails for me. Attached output from
mvn -Dtest=org.apache.sling.osgi.installer.it.BundleInstallStressTest
-Dpax.exam.log.level=DEBUG test
as a zip file. The surefire log contains
Java.lang.AssertionError: All bundles should be installed in cycle 5 : Expected
events=[
BundleEvent null, version=null, state=16
BundleEvent null, version=null, state=1
]
received events=[
BundleEvent osgi-installer-testA, version=1.0.0, state=1
BundleEvent osgi-installer-testA, version=1.0.0, state=32
BundleEvent osgi-installer-testA, version=1.0.0, state=128
BundleEvent osgi-installer-testA, version=1.0.0, state=2
]
> Add state management for resources
> ----------------------------------
>
> Key: SLING-1737
> URL: https://issues.apache.org/jira/browse/SLING-1737
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: OSGi Installer 3.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: OSGi Installer 3.0.0
>
> Attachments: debug.zip
>
>
> Currently there is no state management, so it is hard to tell if a resource
> has been installed, should be installed, uninstalled etc.
> In some situations this leads to endless loops where something is tried over
> and over again - although nothing needs to be done anymore or can't be done.
> If we add proper state management to the resources, the installer knows what
> needs to be done and can act accordingly
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
