Issue #47580: Push ModuleProxy-based patches to separate branch - 389-ds-base

389-ds-base

#47580 Push ModuleProxy-based patches to separate branch

Closed: wontfix Opened Oct 31, 2013 by jrusnack.

ModuleProxy based approach is largely incompatible with DSAdmin. Therefore I would like to create new branch design-proposal, to which all ModuleProxy related stuff would be pushed. From there, I will be easy to cherry-pick to master.

jrusnack commented Oct 31, 2013

attachment
0001-Enhancing-DSModuleProxy-to-work-with-classes.patch

jrusnack commented Oct 31, 2013

attachment
0002-Adding-methods-to-repl-module.patch

jrusnack commented Oct 31, 2013

attachment
0003-Adding-suffix-module.patch

jrusnack commented Oct 31, 2013

attachment
0004-Cleaning-DSModuleProxy-from-ds_instance.patch

jrusnack commented Nov 1, 2013

ModuleProxy obsolete.

spichugi commented Sep 13, 2020

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/917

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

Sep 13, 2020

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Priority

Normal

origin

389-ds-base

#47580 Push ModuleProxy-based patches to separate branch Closed: wontfix Opened Oct 31, 2013 by jrusnack.

Metadata

#47580 Push ModuleProxy-based patches to separate branch

Closed: wontfix Opened Oct 31, 2013 by jrusnack.