-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scapegoat doesn't like Play #30
Comments
I'm not familiar with play, what is src_managed? On 15 July 2015 at 19:40, Łukasz Sowa [email protected] wrote:
|
Wow, that was quick! I'm not familiar with Play internals but I guess src_managed is a dir that is being created on-the-fly for generated code. You should be able to repro this bug by creating a template Play project and running scapegoat on it. |
can you make me a sample project. On 15 July 2015 at 19:43, Łukasz Sowa [email protected] wrote:
|
https://github.com/luksow/play-scapegoat-bug fire up sbt inside
or
|
Thanks. |
Having same issue here during builds on Jenkins. Any updated on what causes the problem and how to fix it? |
Does this help? https://github.com/danielnixon/sbt-ignore-play-generated (Play 2.5.x only.) |
In my play2.5-project with sbt-ignore-play-generated when I execute
How can I fix it ? |
Hi,
I'm trying to integrate scapegoat with Play 2.3.4 and it turns out that there're some issues with Play's code generation feature. First of all, scapgegoat is desperately trying to go through compiled templates, spitting out enormous number of issues - this however can be with a rule like
scapegoatIgnoredFiles := Seq(".*assets.*", ".*src_managed.*")
. The bigger problem is that it fails (2 out of 3 times) during code generation with some cryptic error messages like:source file '...target/scala-2.11/src_managed/main/assets/controllers/routes.java' could not be found
or similar. Any ideas? Thanks!Łukasz
The text was updated successfully, but these errors were encountered: