You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Evolutions generated in wrong place in PlayService project #12266
@mkurz seems like this issue should have been "fixed" by #11917, but in fact directoryName method still returns hardcoded conf folder for default config value
@PromanSEW#11917 was not about fixing the hardcoded conf folder, but about to allow the evolution folder to be placed outside the application's root folder. I just kept the hardcoded conf folder for now, so by default it's the same "wrong" behaviour. The intention of #11917 was not to fix the hardcoded conf folder.
Activity
mkurz commentedon Dec 12, 2023
This is known, there are other places where we still hardcode the
conffolder, seePromanSEW commentedon Dec 12, 2023
Fix: add to
build.sbtinsettingssectionmkurz commentedon Dec 12, 2023
Be aware this is just for dev mode.
PromanSEW commentedon Dec 12, 2023
@mkurz I know. This is for updating script while development
PromanSEW commentedon Dec 12, 2023
@mkurz seems like this issue should have been "fixed" by #11917, but in fact
directoryNamemethod still returns hardcodedconffolder for default config valuemkurz commentedon Dec 12, 2023
@PromanSEW #11917 was not about fixing the hardcoded
conffolder, but about to allow the evolution folder to be placed outside the application's root folder. I just kept the hardcodedconffolder for now, so by default it's the same "wrong" behaviour. The intention of #11917 was not to fix the hardcodedconffolder.PromanSEW commentedon Oct 23, 2026
@mkurz I think this issue was resolved by playframework/play-ebean#931 and can be closed
EDIT: No, playframework/play-ebean#934 fixes this issue, not 931