#137 - Improve multi-module projects support - small improvement in logging, when "play" dependency found in the reactor.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11745 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - "run", "test" and "start" mojos improved; when invoked in Maven reactor with one "play" application and one or many "play" dependencies (modules) skip execution for modules ("play" module has empty "application.conf" file, empty or not present "routes" file).

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11746 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
maven-parent - ".project" and ".settings" added to svn:ignore.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11747 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
plugin - ".classpath", ".project" and ".settings" added to svn:ignore.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11748 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
Top level "pom.xml" file removed, it wasn't used for a long time, all modules are being built and released separately.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11749 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - multi-module test project added.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11750 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - multi-module test project added - cont.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11751 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
Copyright headers updated - "Copyright 2010-2013" -> "Copyright 2010-2014".

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11752 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
play-maven-plugin - M2Eclipse configuration (avoiding warnings during importing this plugin into Eclipse).

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11753 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - a little trick, but huge improvement form reactor builds.
Any lifecycle phase or any play:xxx mojo requiring dependency resolution (for example: "play:dependencies" or "play:run") can be executed for Maven reactor (multi-module build) with at least two "play" modules, where one "play" module depends on another, without the need to execute "compiler:compile" (or "compile" phase) before it.
Setting project artifact's file to project's base directoy should have no side effects because "play" packaging module artifact's file is not being added to classpaths of other reactor modules depending on it (see "<addedToClasspath>false</addedToClasspath>" in "src/main/resources/META-INF/plexus/components.xml" file).

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11754 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
play-maven-plugin - use PlayServerBooter.class.getName() instead of "com.google.code.play.PlayServerBooter". This adds a little better dependency control.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11755 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - support Play! module dependencies implemented as "pom" or "jar" projects with "-module" (and/or "-module-min") zip type assemblies generated and attached (like all standard Play! modules mavenized by me (http://code.google.com/p/maven-play-plugin/wiki/MavenizedModules). Test project will be added soon to show this case.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11756 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - check for potential reactor with "jar" module dependency in play:dependencies mojo.

In a reactor (multi-module) build if "play" module depends on "jar" module, "jar" module artifact's file can be a directory instead of a file.
This happens when "compile" lifecycle phase or any phase between "compile" and "package" has ben executed before "play:dependencies" mojo (for example "mvn compile play:dependencies").

How to solve this problem?
Dependency "jar" artifact has to be installed first ("mvn install" for "jar" module only) or at least "package" phase has to be executed for the whole reactor before "play:dependencies" ("mvn package play:dependencies").

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11757 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - temporary solution to distinguish real Play! application from Play! modules used by application inside a reactor (multi-module) build.

If there is one (ONLY ONE allowed for now) real Play! application and some Play! modules (having "play" packaging as well) inside a reactor, only for this one application following mojos: "play:generate-selenium-junit4-sources", "play:precompile", "play:start", "play:stop", "play:run", "play:test", "play:start-server" and "play:stop-server" will be executed.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11758 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - temporary solution to distinguish real Play! application from Play! modules used by application inside a reactor (multi-module) build - cont.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11759 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - multi-module test project (added in rev.11750) improved.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11760 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - multi-module test project with "play" application and dependent "jar" module added.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11761 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
test-projects/multimodule/play-module-dependency - small fixes.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11762 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
#137 - Improve multi-module projects support - multi-module test project with "play" application and dependent Play! module implemented as "pom" module with assembly added.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11763 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0
test-projects/packagings/default/inter-app-dependency - actualized (simplified) packaging instructions in "readme.txt" file, possible after recent multi-module (reactor) build improvements.

git-svn-id: http://maven-play-plugin.googlecode.com/svn/trunk@11764 9c2ad861-7886-cb7c-dcd7-2b8d41cd5de0