pom.xml file changes

Required migration steps are slightly different for projects using play-app-default-parent and not using it.

    <properties>
        <play.version>1.3.4</play.version>
    </properties>

        <dependency>
            <groupId>com.google.code.maven-play-plugin.org.playframework.modules.docviewer</groupId>
            <artifactId>play-docviewer</artifactId>
            <version>${play.version}</version>
            <classifier>module-min</classifier> <!-- or <classifier>module</classifier> -->
            <type>zip</type>
            <scope>provided</scope>
        </dependency>

        <dependency>
            <groupId>com.google.code.maven-play-plugin.org.playframework.modules.docviewer</groupId>
            <artifactId>play-docviewer</artifactId>
            <version>${play.version}</version>
            <scope>provided</scope>
        </dependency>

    <properties>
        <play.version>1.3.4</play.version>
    </properties>

        <dependency>
            <groupId>com.google.code.maven-play-plugin.org.playframework.modules.docviewer</groupId>
            <artifactId>play-docviewer</artifactId>
            <version>${play.version}</version>
            <scope>provided</scope>
        </dependency>

    <parent>
        <groupId>com.google.code.maven-play-plugin</groupId>
        <artifactId>play13-app-default-parent</artifactId>
        <version>1.0.0-beta8</version>
    </parent>

module dependencies defined in conf/application.conf file

In Play! 1.1.x modules had to be installed inside PLAY_HOME/modules directory (play install command) and included in conf/application.conf file for example

# Additional modules
# ~~~~~
# A module is another play! application. Add a line for each module you want
# to add to your application. Modules path are either absolutes or relative to
# the application root.
# They get loaded from top to bottom; Syntax: module.{name}={path}
#
# Keep the next line as is to help the play script to manage modules.
# ---- MODULES ----
module.crud=${play.path}/modules/crud

In pom.xml file such dependency has to be defined with provided scope and is extracted to target/play/modules/${modulename} directory.

This method was deprecated (but still working) in Play! 1.2.x. In Play! 1.3.x it was removed.

All dependent modules have to be added to conf/dependencies.yml file and declared with default scope in pom.xml file (remove <scope>provided</scope>).

There is additional automatic, transparent to the users, dependency mechanism in Play! docviewer and testrunner modules are added to every project in runtime without the need to declare them in conf/application.conf or conf/dependencies.yml file. They are declared in pom.xml file (in play-app-default-parent if you are using it) with provided scope. This scope should not be changed.

conf/dependencies.yml file content

conf/dependencies.yml configuration file was introduced in Play! 1.2.x and was used exclusively by play dependencies (or play deps) command. It is ignored in Maven environment. In Play! 1.3.x things changed. Every Play! module dependency must be included in it. This configuration is processed in Play! initialization (application start) phase. Jar-type dependencies on the other hand, are used only by play dependencies command, and are not required when working in Maven environment. They can be added to conf/dependencies.yml configuration file, but will be ignored by Maven plugin.