Community
Participate
Working Groups
The aim is first of all to avoid class which physical full path is more than 256 characters. Indeed it leads, on Windows, to issues using git tools such as egit or git bash. Often the rebase interative can't succeed which force to redo manually what should be done which is obviously a loss of time. The second aim is to generate less classes. This second aim could be the subject of another bug.
I'm taking this, it's part of a more general area I've been thinking about. It's clear that the current approach has a lot of issues, but I'm not yet convinced whether it's worth improving the current classes generation piece-by-piece, or drop it and replace it with a better implementation (probably based on the EEF 1.6 runtime).
