From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Were you able to get the runPlay task debugged?

Hi 
Only with “remote debug” configuration :pensive:
I think this plugin needs an update. 

Yeah I'm wondering how the plugin could be updated to support debugging from intellij

I forked it, and going through but will take me time 

Should be placed in the conf directory, afaik

Hi, folks! :wave:
Could you tell me, how can I rewrite this code (one of example in plugin sources) to Kotlin DSL?
```sourceSets {
    main {
        twirl {
            srcDir 'extra/twirl'
        }
    }
}```

OMG :scream:  I made this variant, that worked
```sourceSets {
    main {
        (conventionPluginOf(this, "twirl") as TwirlSourceSet).twirl {
            srcDir("src/main/twirl")
        }
    }
}```
But it’s ugly :disappointed: Maybe someone know another way?

It doesn’t work :man-shrugging:
```SourceSetContainer#named(String, Class, Action) on SourceSet container cannot be executed in the current context.```

Hi, everyone! :wave:
The Play Team is happy to announce the start of β-testing for our new *Play Gradle Plugin* :wink: 
<https://github.com/orgs/playframework/discussions/12338>

Hello :wave:! Looking for some guidance on how to help my team get to newer versions of Gradle, and I was hoping this group could help out.

I have recently been working on upgrading my team’s build to 8.13, and ran into an issue where the <https://github.com/gradle/playframework|old play plugin> is no longer functioning, running into some weird class failures. This plugin is clearly pretty old, being built on language version 8 and gradle version 6.x. I am not particularly surprised that, given our project is on Java 17 and currently Gradle 8.5, we would eventually see some incompatibilities.

I am aware that there is a <https://github.com/orgs/playframework/discussions/12338|new and upcoming gradle plugin> for Play, but we are not currently in a position where we can upgrade to Play 3.x to make use of it. My main question(s):

• Has anyone run into this bind yet? I don’t see anything on the repo issues, but maybe there’s been some action here.
• Is there guidance on how I could potentially contribute, or work around, this dependency versioning issue?
Thanks in advance!

For additional context, here is the error I get when running `runPlay`, particularly with `0.14` of the Play application plugin:

```java.lang.NoSuchMethodError: 'net.rubygrapefruit.platform.Native net.rubygrapefruit.platform.Native.init(java.io.File)'
        at org.gradle.internal.nativeintegration.services.NativeServices.&lt;init&gt;(NativeServices.java:281)
        at org.gradle.internal.nativeintegration.services.NativeServices.initialize(NativeServices.java:260)
        at org.gradle.internal.nativeintegration.services.NativeServices.initializeOnWorker(NativeServices.java:240)
        at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:99)
        at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:71)
        at worker.org.gradle.process.internal.worker.GradleWorkerMain.run(GradleWorkerMain.java:69)
        at worker.org.gradle.process.internal.worker.GradleWorkerMain.main(GradleWorkerMain.java:74)```

Haven't personally used runPlay in a while, but our legacy play app still builds on Gradle 8.13 with a (mildly) forked version of <https://github.com/gradle/playframework>

If you get a chance, could you try executing that to see if you are running into the same thing? Our app is building too, but devs hit the same issue as me around missing methods effectively.

Also, if you don’t mind me asking, what is within your fork? Primarily a rebuild with a newer version of gradle? I’m considering doing the same thing effectively

I think upstream's fixed it now, but we used to strip comments/source generation dates to avoid cache misses <https://github.com/gradle/playframework/issues/109#issuecomment-1478831982>

Also we have to run the scala compile and twirl generate tasks via java 8, and the plugin doesn't respect javalauncher/toolchain options, so we hacked that in (our main repo runs/builds on 17)

So runPlay fails but that's because my test environment isn't up, I don't see anything around
```java.lang.NoSuchMethodError: 'net.rubygrapefruit.platform.Native net.rubygrapefruit.platform.Native.init(java.io.File)'
        at org.gradle.internal.nativeintegration.services.NativeServices.<init>(NativeServices.java:281)```

Fascinating... what Java flavor are you using?

```java --version
openjdk 21.0.6 2025-01-21 LTS```

Hmm okay this is helpful, thanks for taking a peek. I’m not quite sure what my issue is, but this at least rules out that it’s fundamentally the play gradle plugin, I think :slightly_smiling_face:

Coming back around to this - it turned out there was an implicit Kotlin versioning issue, that somehow only surfaced with the way the Play Plugin is submitting to the work queue with process isolation… Aligning all Kotlin dependencies with the version shipped with Gradle fixed everything!