-
Notifications
You must be signed in to change notification settings - Fork 746
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
projects lost when merging per-project setting in read-only configuration with active configuration #2147
Comments
One way how to deal with this would be to change the workflow - augment the |
I think this is a fall-out of how XML serialization is done. As a result, merge is not really a merge. |
Possibly as a fix the configuration merge needs to be more intelligent. |
I think some customizations in this code |
This has a workaround so stripping the stopper tag for now. |
Thel workaround needs a tweak for full global (not per project) indexing - I believe the per-project setting in read-only configuration is applied after the projects are discovered however once the initial index is done, the per-project settings have to be removed from read-only configuration and set in the webapp. |
https://github.com/oracle/opengrok/wiki/Per-project-configuration advises to put per-project configuration into read-only configuration file. However when merged with a configuration retrieved from webapp that already contains some projects via:
the resulting
configuration.xml
will only have the projects specified in read-only configuration.The text was updated successfully, but these errors were encountered: