Hi Gianluca, To me, grails-app is just a folder name like webapp, so I don't see the benefit of changing the folder-name, except for a few letters shorter.
If others think the idea is good, I'm not opposed to it, I just don't see a big win. Den fre. 18. apr. 2025 kl. 11.01 skrev Gianluca Sartori <g.sart...@gmail.com >: > I've been thinking about this forever... > > We have the `grails-app` folder containing the conventions over > configuration project structure that is a Grails standard, a different one > from the `src` folder structure. > > The fact it contains `grails` in its name can be useful to immediately > recognise the type of the project by giving a quick look at the directory > tree. But to my eyes that is all it does. > > I think today I finally found the braveness and recklessness to propose we > change it to a more "domain specific" or "technical" name instead of having > the name of the product in it. > > The meaning of that folder should be given by its role in the context > rather than a marketing/communication purpose. > > So I am proposing we change the `grails-app` to `webapp` to indicate it > contains the web part of the application. > > Pros: > - Removes the name of the product from a technical folder > - Gives it a meaning that is immediately intelligible from a developer > point of view (more people know what a `webapp` is that a `grails-app`, no > need to explain further) > - It is a good time to make this change since the move to Apache is a big > change/event > > Cons: > - Breaking change when porting applications from older Grails versions > (must be documented but it's an easy fix) > > Bomb dropped, what is the community opinion? > > Cheers, > Gianluca Sartori > -- Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes.
