[
https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909141#action_12909141
]
Carsten Ziegeler commented on SLING-1737:
-----------------------------------------
I retried the tests running on Java 5 and Java 6 - and they run each time :(
It seems the -Dpax.exam.log.level=DEBUG test option does not work like I
expected; at least I can't find the relevant log statements in the logs you
provided :(
So maybe could you please rerun the tests and change directly the property
value in the pom.xml?
Please also make sure that you did a "mvn install" on the
installer/osgi/installer project before you run the tests.
@Justin - Are the tests for you failing with both Maven versions or just with
3.0-beta-3? - I'm just speculating here, but as I'm also using OS X with Maven
2.2.1, there must be some difference between our environments.
> 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: ConfigInstallTest-debug.log.gz, debug.zip,
> RemovedResourceDetectionTest-debug.log.gz
>
>
> 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.
