Benjamin Muschko

@aaronlijie @ymwang1984 Thanks for reporting. Could you please put together a very simple project that reproduces the issue as requested here https://github.com/gradle/playframework/issues/90#issuecomment-478677674? You likely have two different implementations of SLF4J...

@aaronlijie Optimally, we'd trim down your example to minimal dependency that produces the issue. I have not seen the issue one some of the sample projects. Any chance you can...

I didn't fully understand the purpose of assets to be honest. Maybe we can briefly chat about why it is necessary.

Could you put together a sample project that reproduces the issue?

I could reproduce the issue by adding the dependency to the build script's classpath. ``` buildscript { repositories { mavenCentral() } dependencies { classpath 'io.swagger.codegen.v3:swagger-codegen-cli:3.0.7' } } plugins { id...

@ymwang1984 I think if you shaded transitive dependencies in your fat JAR with a different package then there's a good likelihood that you will not run into the reported issue....

The error message would have to be handled by Gradle core. I am going to close this issue for now.

@ymwang1984 The software model Play plugin uses deep and complex Gradle core-internal infrastructure to execute external tools in a forked JVM process e.g. Twirl or for running the Play application....

Implementing these tests will be hard with the capabilities provided by TestKit at the moment. For verifying a running Play application the following functionality is needed: 1. TestKit can start...

@big-guy Any news here?