-
-
Save guillaumebort/768364 to your computer and use it in GitHub Desktop.
| ~/Desktop/scrapbook/coco $ play dependencies | |
| ~ _ _ | |
| ~ _ __ | | __ _ _ _| | | |
| ~ | '_ \| |/ _' | || |_| | |
| ~ | __/|_|\____|\__ (_) | |
| ~ |_| |__/ | |
| ~ | |
| ~ play! 1.1-localbuild, http://www.playframework.org | |
| ~ framework ID is gbo | |
| ~ | |
| ~ Resolving dependencies using /Users/guillaume/Desktop/scrapbook/coco/conf/dependencies.xml, | |
| ~ | |
| ~ commons-cli->commons-cli 1.0 (from mavenCentral) | |
| ~ commons-lang->commons-lang 2.0 (from mavenCentral) | |
| ~ com.google.guava->guava r07 (from mavenCentral) | |
| ~ com.google.code.findbugs->jsr305 1.3.7 (from mavenCentral) | |
| ~ play->strike 0.1 (from playModules) | |
| ~ play->sass 1.2 (from playModules) | |
| ~ commons-cli->commons-cli 1.2 (from mavenCentral) | |
| ~ | |
| ~ WARNING: These dependencies was not found and are ignored (use --verbose for details), | |
| ~ | |
| ~ zenexity->tutu 1.0 | |
| ~ | |
| ~ Some dynamic revisions have been resolved as following, | |
| ~ | |
| ~ play->sass [1.0,) will use version 1.2 | |
| ~ play->play-framework [1.0,) will use version 1.1 | |
| ~ commons-cli->commons-cli [1.0,) will use version 1.2 | |
| ~ | |
| ~ Some dependencies have been evicted, | |
| ~ | |
| ~ commons-logging->commons-logging 1.0 is overriden by commons-logging->commons-logging 1.1.1 | |
| ~ commons-lang->commons-lang 1.0 is overriden by commons-lang->commons-lang 2.0 | |
| ~ commons-lang->commons-lang 2.5 is overriden by commons-lang->commons-lang 2.0 | |
| ~ commons-cli->commons-cli 1.0 is overriden by commons-cli->commons-cli 1.2 | |
| ~ | |
| ~ Installing resolved dependencies, | |
| ~ | |
| ~ modules/strike-0.1 | |
| ~ modules/sass-1.2 | |
| ~ lib/commons-cli-1.2.jar | |
| ~ lib/jsr305-1.3.7.jar | |
| ~ lib/guava-r07.jar | |
| ~ lib/commons-lang-2.0.jar | |
| ~ | |
| ~ Done! | |
| ~ |
Looks great. Nice to see dependency management being integrated into play.
Sounds very good!
This is a very welcome surprise!
I'm curious how this will interact with creating the play war for use in other application servers. For example, I use the GAE module to build a war directory to deploy to GAE. In order to keep my libraries playing well with play (pun intended), I use jars from the play/framework/lib directory as dependencies in sub-projects. I also end up removing some of the jars from the final war that are not necessary in the runtime environment (junit, memcache, etc).
Great news!
how looks dependencies.xml file? is this ivy format?
Yikes. XML. One of the defining features of Play for me is "no *&^%^$&^% XML" ;-).
Yaml maybe?
great news!!!
but i've seen some yaml examples out there...
It rocks !
Thanks for this work Guillaume