Resolution: Cannot Reproduce
Affects Version/s: 2.2.1
Fix Version/s: None
Component/s: View technologies
Grails seems to occasionaly mix up views from different projects if they relate to the sam domain objects. This may manifests as a varitety of errors, when launching the project. In my case I launch one project, and one of the views that is rendered comes from a different project.
I've got a domain module and a frontend and admin backend project using the domain classes as a local plugin in a simple directory structure:
Both backend and frontend have a Controller and Views for the "CourseEvent" domain class. When I run project frontend (Admin is not running),and I invoke the generated "list" View, I'd expect to see the view stored in:
What I get is the view stored under:
So a view of a different project, which is not running is rendered.
Also, when I delete the views in booking/grails-app/views/courseEvent/ ,
then cd to the booking dir and issue:
>grails GenerateViews de.eppleton.cms.CourseEvent
I get this output:
| Generating views for domain class de.eppleton.cms.CourseEvent
> File /grails-app/views/courseEvent/create.gsp already exists. Overwrite?[y,n,a]
If I choose the "a" option the views get generated in the correct (empty) directory. Obviously grails mixes up the two independent projects.
Judging from mailing lists having a admin backend and a frontend sharing the same domain classes in separate projects is a common setup. Using generated views and controllers as a starting point also seems common. So I assume this might be a problem affecting many develpers.