• Convert existing logic from software model to current model
• Defines a dedicated source set and task

Note: Calls off to task type in Gradle core including the Play tool chain

• Build code uses Kotlin DSL
• Integration test source set and task
• Integration test fixture live in a separate source set
• Declare necessary dependencies
• Enable build scan

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayTestPlugin.java

• Migrate existing integration tests as much as possible
• Multi-version testing is not supported
• All tests should pass

named, register, etc.

We can fix this when the tasks are migrated over.

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayTwirlPlugin.java

• Migrate existing integration tests as much as possible
• Multi-version testing is not supported
• All tests should pass

• Convert existing logic from software model to current model
• Defines a dedicated source set and task

Note: Calls off to task type in Gradle core including the Play tool chain

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayApplicationPlugin.java

• Convert existing logic from software model to current model
• Applies other plugins
• Configures other plugins as needed (e.g. JavaScript and CoffeeScript plugins)

• Convert existing logic from software model to current model
• Creates and configures task for create distributions
• Creates and configures task for start script
• Creates and configures tasks for creating ZIP files
• Introduces lifecycle tasks

• Migrate existing integration tests as much as possible
• Multi-version testing is not supported
• All tests should pass

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayPlugin.java

• A selection of existing integration tests can be run with multiple versions of Play
• TestKit does not have built-in support for it
• Implement a JUnit rule to allow running tests multiple times

Note: We do not know yet what the supported versions of Play should be. This depends on customers of the plugin giving us the information.

• Convert existing logic from software model to current model
• Configures test source set from Scala plugin
• Configures test task from Scala plugin

• Convert existing logic from software model to current model
• Defines a dedicated source set and task

Note: Calls off to task type in Gradle core including the Play tool chain

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayRoutesPlugin.java

• Move the custom task type (CoffeeScriptCompile) into external plugin implementation
• Instantiates the local custom task type instead of the one in Gradle core
• Make potential changes to implementation to enable lazy evaluation (Provider types)

• Migrate existing integration tests as much as possible
• Multi-version testing is not supported
• All tests should pass

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayCoffeeScriptPlugin.java

This can wait until later, but we should be judicious in the use of afterEvaluate. This has been good so far.

• Convert existing logic from software model to current model
• Only supports IntelliJ IDEA
• Mapping of configurations to IDEA scopes
• Mapping of source/target byte code version
• Mapping of source directories

Note: We should see IntelliJ can just import a Play project without the needs to implement this plugin

• Write publishing code in build script using the Kotlin DSL
• An initial version is available on the Gradle plugin portal
• Individual plugins are mapped on the Gradle plugin portal
• New versions can be published to Gradle plugin portal

• Migrate existing integration tests as much as possible
• Multi-version testing is not supported
• All tests should pass

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/ide-play/src/main/java/org/gradle/play/plugins/ide/PlayIdePlugin.java

• Convert existing logic from software model to current model
• Can compile Java/Scala code
• Can create JAR and assets JAR
• JAR and asset JAR are defined as outgoing artifacts
• Can run a Play application

Note: Calls off to task type in Gradle core including the Play tool chain

• Corresponding tool chain migrated to external plugin (this could potentially involve using the worker API instead)
• Simplify implementation as needed
• Custom task type in external plugin does not call off to Gradle core anymore

• Gradle core integration testing provided functionality for working on a handle of a Gradle test process
• TestKit does not easily support those scenarios
• We'll have to decide how to approach the problem without spending too much time

• Convert existing logic from software model to current model
• Defines a dedicated source set and task

Note: Calls off to task type in Gradle core including the Play tool chain

• Move the custom task type (JavaScriptMinify) into external plugin implementation
• Instantiates the local custom task type instead of the one in Gradle core
• Make potential changes to implementation to enable lazy evaluation (Provider types)

ref: https://docs.travis-ci.com/user/multi-os/

Tests should run on Windows and maybe macOS.

This can wait for later.

• Corresponding tool chain migrated to external plugin (this could potentially involve using the worker API instead)
• Simplify implementation as needed
• Custom task type in external plugin does not call off to Gradle core anymore

• Corresponding tool chain migrated to external plugin (this could potentially involve using the worker API instead)
• This will involve the deployment API
• Simplify implementation as needed
• Custom task type in external plugin does not call off to Gradle core anymore

• Migrate existing integration tests as much as possible
• Multi-version testing is not supported
• All tests should pass

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayDistributionPlugin.java

Existing code in Gradle core: https://github.com/gradle/gradle/blob/master/subprojects/platform-play/src/main/java/org/gradle/play/plugins/PlayJavaScriptPlugin.java

• Corresponding tool chain migrated to external plugin (this could potentially involve using the worker API instead)
• Simplify implementation as needed
• Custom task type in external plugin does not call off to Gradle core anymore

• Corresponding tool chain migrated to external plugin (this could potentially involve using the worker API instead)
• Simplify implementation as needed
• Custom task type in external plugin does not call off to Gradle core anymore

• Expose DSL via extension
• Extension fields use Provider types
• Can configure Play version, Scala version and Java version
• Captures values are used to configure Play application

• Move the custom task type (RoutesCompile) into external plugin implementation
• Instantiates the local custom task type instead of the one in Gradle core
• Make potential changes to implementation to enable lazy evaluation (Provider types)

• Externalize source code snippets
• Import source code snippets in docs
• Add ability to generate HTML from it via Asciidoctor
• Change documentation to reflect different plugin behavior

• Migrate existing integration tests as much as possible
• Multi-version testing is not supported
• All tests should pass

• Move the custom task type (TwirlCompile) into external plugin implementation
• Instantiates the local custom task type instead of the one in Gradle core
• Make potential changes to implementation to enable lazy evaluation (Provider types)

• Move the custom task type (PlayRun) into external plugin implementation
• Instantiates the local custom task type instead of the one in Gradle core
• Make potential changes to implementation to enable lazy evaluation (Provider types)

• Create test cases
• Tests pass on CI
• Potentially use Exemplar

• Migrate existing integration tests as much as possible
• Excludes integration testing for functionality that uses continuous build & running an application (TestKit does not provide proper support to easily implement scenarios)
• Multi-version testing is not supported
• All tests should pass

• Move code samples to dedicated place in external plugin repository

• Provide a Travis CI configuration file
• Enable project on Travis CI
• The plugin source code can be compiled, all tests can be run
• Add build badge to README file of project