Community
Participate
Working Groups
In the old metadata generator code it is creating mkdir and rmdir configure/unconfigure actions for the reconciler bundle. We currently have clients who are still using the metadata generator (instead of the publisher) and this metadata will cause problems in shared installed scenarios. We should change the metadata generator code in R3.6.x to not do this. I'm sure not if we need to make the code change in HEAD since we plan on removing the generator soon. (in the 3.7 release I believe?)
Created attachment 184795 [details] patch Patch to remove the rmdir command from the unconfigure action for the reconciler bundle. We've left the mkdir as-is.
To give more background, in the metadata generator these actions were hard-coded as instructions on the p2.reconciler.dropins bundle. In the publisher, this hard-coding was removed entirely, and instead the mkdir action is done at the product level (whether dropins should exist, and where it should go, is a product-level concern). The rmdir action for dropins was removed entirely when we switched to the publisher.
Released to R36x branch.
