1) I did resolve this error for most artifacts, except for the autoconf processors. I cannot retrieve these artifacts using the client nor delete them, so I cannot verify if they have been uploaded before.

2) Removed the fileinstall and management bundles from the distributions

3) Fixed the error by using hard coded PIDs for the tenant and config processors

After resolving the errors above and adding demo-core and demo-web distributions, I could successfully push the demo-core distribution to the AMA. Also de-associating the demo-core distribution from the AMA seems to work, but when I re-associate demo-core with the AMA again, the target status displays "failed". Nothing seems to happen on the AMA, there are no errors in the AMS log, but the LogViewer of the AMA shows these errors:

type: org.osgi.framework.BundleException
msg: Unresolved constraint in bundle org.amdatu.deployment.autoconf [8]: Unable to resolve 8.0: missing requirement [8.0] package; (&(package=org.osgi.service.cm)(version>=1.3.0)(!(version>=2.0.0)))
id: 8

type: org.osgi.framework.BundleException
msg: Unresolved constraint in bundle org.amdatu.tenant.conf.rp [11]: Unable to resolve 11.0: missing requirement [11.0] package; (&(package=org.amdatu.tenant)(version>=1.0.0)(!(version>=2.0.0)))
id: 11
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
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to