-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to push publish plugins #21568
Comments
This does not work in docker environments. When bundling OSGI plugins, we should use a subfolder of the normal |
Hey team! Please add your planning poker estimate with ZenHub @dsilvam @victoralfaro-dotcms |
Hey guys I have a couple of questions here that maybe we need to take in consideration... Does this work with the OSGI, static ones or both? Also, what should expect in case you already have the plugin in the receiver side, should we have integrity checker for plugins? or just should replace the existing one without confirmation ? Taking in consideration this change can broke some features in case of a wrong configuration, maybe at least we should create a new property to enable/disable permissions to override the configuration. |
Additional ticket: https://dotcms.zendesk.com/agent/tickets/106537 |
…tead. Json serializing instead of xml for OSGi push publish.
…tead. Json serializing instead of xml for OSGi push publish.
…ing, centralizing ObjectMapper and XStream instances to one and addind plugin case to Dependency manager.
Need to test in 5.3.8 series, probably not needed since was introduced with the changes in PP (21.05ish) |
…ing, centralizing ObjectMapper and XStream instances to one and addind plugin case to Dependency manager.
…ing, centralizing ObjectMapper and XStream instances to one and addind plugin case to Dependency manager.
…ing, centralizing ObjectMapper and XStream instances to one and addind plugin case to Dependency manager.
…ing, centralizing ObjectMapper and XStream instances to one and addind plugin case to Dependency manager.
…ing, centralizing ObjectMapper and XStream instances to one and addind plugin case to Dependency manager. (#21974)
Pass Internal QA it was test with this plugins: https://github.com/dotCMS/plugin-seeds/tree/master/OSGi/com.dotcms.rest
Change " PUT!" by " PUT! With changes"
|
About this one: "Taking in consideration this change can broke some features in case of a wrong configuration, maybe at least we should create a new property to enable/disable permissions to override the configuration." This is a bug is not a new issue About this one: "Also, what should expect in case you already have the plugin in the receiver side, should we have integrity checker for plugins? or just should replace the existing one without confirmation ?" This replace the existing one, this have the same behavior in the sender when you change a Plugin and Upload this again, so I think it is right. About this one: "Does this work with the OSGI, static ones or both?" the static plugins are deprecated |
We need some work here, every time you push any plugin we are getting this error in the log: |
Fixed, tested on release-22.06 and now we don't have the error in the log |
Will not be backporting to LTS releases due to changes to bundle manifest files and an upgrade task requirement |
Describe the bug
Attempting to push publish plugins results in an error attempting to generate a directory
Reproduced on: 21.06.6, 22.01
Related Ticket: https://dotcms.zendesk.com/agent/tickets/106313
To Reproduce
Expected behavior
The plugin should push successfully.
discussion #21590
The text was updated successfully, but these errors were encountered: