Had a hard fight for restructuring already #1522.

@laoneo is that the correct link?

#15221 is the correct one.

@Bakual has the right one

Still don't like it. feel i'm being outvoted by popular opinion tho. so if you wanna merge @laoneo feel free

Agree with @wilsonge. Still don't like it and i don't see a real benefit or best practice here. Not a PHP application, just overcomplicating all components, modules, plugins for nothing

I also still don't like it.
In the end it's just a bandaid to cope with the lowercase/uppercase issue. We need a proper solution there so we don't have to needless move files around.

I mean we can start the debate again. But I guess #15221 has already all the pros and cons. I still like it when the root folder is not also managed by the classloader.

At least consistent in core would be great.

For me it looks much nicer like

than

Thanks @SharkyKZ!! It is a step into the right direction. Especially for the extensions which do have a vendor folder. So we don't have the the same folder managed by two classloaders.

We need a proper solution there so we don't have to needless move files around.

Yes, regardless of this PR here we need a solution in case if we again have some mistake in case-sensitive file names which later has to be corrected with an update.

Is there anybody out the willing and having the necessary knowledge to work on that? maybe @HLeithner has ideas?

Where do we have that issue @richard67 ?

@laoneo We will have this issue again as soon as someone adds some class file and the file does not have the right case-sensitive name. This happened sometimes in past and was one reason for moving around files. See comments e.g. by @Bakual above.

P.S. Problem was that replacing the files with the new name by unpacking the update package doesn't really work on Windows. When you have e.g. a file "Heinz.php" and find out it should be "heinz.php" and so rename it in the repo, it will be "heinz.php" in the package, which is right, but when unpacking that package and so overwriting "Heinz.php", Windows will keep the old name "Heinz.php" for that file just having been unpacked. That's why we moved files around, because when unpacking the update package, Windows will not find a file to overwrite and so use the case as it is in tha packkage ("heinz.php").

For example:
#23725 (there is also a PoC for the solution)

And here:
#25279 (comment)

@HLeithner Thanks. Will check on weekend if I understand it and if necessary talk with you on Glip about what to be done and if I can do it (in case you don't have time). Maybe we also should discuss on Glip in the maintenance team to see what the opinions are, if such solution would be accepted. I think we need a way to rename "Heinz.php" to "heinz.php" on Windows, and as far as I did read there should be ways to do that with PHP. If that will also work for "Hugo.php" is another question (joking) ;-)