Skip to content
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

Adding the possibility to disable continuous build for the 'runPlay' task #112

Open
PaulFridrick opened this issue Oct 14, 2019 · 1 comment

Comments

@PaulFridrick
Copy link
Contributor

Could we have the possibility to disable the continuous build for the task 'runPlay' ?
In my case, many unnecessary rebuilds are triggered when I change conf files of my Play project, or front source files which are located in a submodule of my Play project...

The same issue is open for the old Gradle Play plugin : gradle/gradle#5026

@PaulFridrick
Copy link
Contributor Author

PaulFridrick commented Nov 19, 2019

If someone has the same issue, I managed to create a new task that does what I need :

task run(type: JavaExec) {
    classpath = sourceSets.main.runtimeClasspath
    main = 'play.core.server.ProdServerStart'

    jvmArgs = ['-Dhttp.port=9000', '-Dconfig.file=./conf/application.conf']
}

The jvmArgs are optional if you use the default port and conf file, this example shows how to override it.

For the devs of the plugin:
As a user of this plugin, I think it could be useful to have the possibility to run Play in this way out of the box. Maybe you could provide an equivalent task in the plugin ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant