Drop dependency on zendframework/zend-loader

[acelaya]

This removes the dependency on the zendframework/zend-load package, as suggested in #185

The HeaderLoader class has been removed and replaced by a simple class map in the Headers class.

However, I have also removed the getPluginClassLoader and setPluginClassLoader methods. Since they are public, this might be a BC break. What do you think?

[acelaya]

Builds are failing with latest dependencies, but they are failing in master too.

I'll try to figure out how to fix them, but it might take me time.

[Xerkus]

Please rebase onto develop

[Xerkus]

There is a PR with fix, I will merge it shortly

[acelaya]

Perfect then. Thanks.

[acelaya]

I have rebased develop. I'll do it again once you merge the other PR.

[Xerkus]

Just a heads up: there is a big ongoing effort going for next major versions for zend-expressive and related packages as well as for zend-mvc. This change will require a next major version, and I do not expect to get to it until february.

[acelaya]

Ok, no rush :-)

[Xerkus]

This is not configurable.
Please move this into a variable in separate class with methods get($name), has($name), add($name, $class), remove($name)

[acelaya]

I didn't realize it had to be configurable. I'll fix it right away.

[acelaya]

If we move the logic to a class, should it be handled as the HeaderLoader used to?

Do we want to keep exposing it via public getter?

[weierophinney]

This repository has been moved to laminas/laminas-mail. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

• Squash all commits in your branch (git rebase -i origin/{branch})
• Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
• Run the laminas/laminas-migration tool on the code.
• Clone laminas/laminas-mail to another directory.
• Copy the files from the second bullet point to the clone of laminas/laminas-mail.
• In your clone of laminas/laminas-mail, commit the files, push to your fork, and open the new PR.
  We will be providing tooling via laminas/laminas-migration soon to help automate the process.

[michalbundyra]

This repository has been closed and moved to laminas/laminas-mail; a new issue has been opened at laminas/laminas-mail#39.