比起play官方推荐的Activator, 作为从java转过来的开发者, 本来想用 maven 不过由于 play console 本身就是基于 sbt 开发的所以只能用sbt了
sbt
sbt 底层是基于 ivy 的, ivy 是和 maven 类似的 jar包 依赖管理, 不过他们存放的目录结构有差异
所以使用 sbt 要解决2个问题:
如何复用原来 maven 本地仓库的jar
修改远程仓库地址
上面两个问题都可以通过修改sbt的默认配置解决.
sbt 默认读取的配置是 sbt/bin/sbt-launch.jar:/sbt/sbt.boot.properties
sbt提供了2个方式修改其默认配置
- 不读取原来的配置
SBT_OPTS增加 -Dsbt.override.build.repos=true 并创建一个 ~/.sbt/repositories 文件, 并修改其配置, 后面有我配置的内容
- 重新指定配置
SBT_OPTS增加 -Dsbt.repository.config=<path-to-your-repo-file> 指定配置路径
比如 -Dsbt.repository.config=~/.sbt/repositories 达到和上面一样的效果
怎么修改SBT_OPTS
linux/macox 的话 直接
1
| $ env SBT_OPTS="-Dsbt.override.build.repos=true" sbt
|
或者配置在 .bashrc/.bash_profile 里面
或者参考这里
附上我的配置~/.sbt/repositories
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
| [scala]
version: ${sbt.scala.version-auto}
[app]
org: ${sbt.organization-org.scala-sbt}
name: sbt
version: ${sbt.version-read(sbt.version)[0.13.8]}
class: ${sbt.main.class-sbt.xMain}
components: xsbti,extra
cross-versioned: ${sbt.cross.versioned-false}
resources: ${sbt.extraClasspath-}
[repositories]
local
local-Maven-Repository: file:///~/.m2/repository/jar, [organization]/[module]/[revision]/[type]s/[artifact](-[classifier]).[ext]
# oschina-nexus: http://maven.oschina.net/content/groups/public/
maven-central
typesafe-ivy-releases: https://repo.typesafe.com/typesafe/ivy-releases/, [organization]/[module]/[revision]/[type]s/[artifact](-[classifier]).[ext], bootOnly
[boot]
directory: ${sbt.boot.directory-${sbt.global.base-${user.home}/.sbt}/boot/}
[ivy]
ivy-home: ${sbt.ivy.home-${user.home}/.ivy2/}
checksums: ${sbt.checksums-sha1,md5}
override-build-repos: ${sbt.override.build.repos-false}
repository-config: ${sbt.repository.config-${sbt.global.base-${user.home}/.sbt}/repositories}
|
oschina 有点坑, 由于最新的jar没同步, 所以各种超时
play
然后等他下载依赖, 创建play 目录结构
因为原本的play-console就是sbt, 所以可以直接在sbt里面敲play 官方的所有命令
比如 playGenerateSecret
source
用maven的话, 如果在ide里面就勾上 auto download source 就可以让他自己下源码了.
可是这个规则在sbt里面行不通了, 并不是说sbt 不能下载源码而是play的依赖是com.typesafe.play" % "sbt-plugin % "2.3.8" 这个插件下载的. 貌似没办法设置让他里面下载jar的时候顺便下载源码.
后来看到这篇blog想到个变通的方式
直接在 build.sbt 里面对需要看源码的jar 手动加dependence
1
2
3
4
5
| libraryDependencies ++= Seq(
// "group" % "artifact" % "version"
"com.typesafe.play" % "play_2.11" % "2.3.8",
"com.typesafe.play" % "play-java-ebean_2.11" % "2.3.8"
)
|
可是这样其实还有问题, 我自己测试下来 play-java-ebean_2.11 能吧源码下载下来, 但是 play_2.11 还是下载不下来, 没有任何报错信息
这种时候只能再手动强制加上 withSource() 官方出处
于是变成了这样
1
2
3
4
5
| libraryDependencies ++= Seq(
// "group" % "artifact" % "version"
"com.typesafe.play" % "play_2.11" % "2.3.8" withSources(),
"com.typesafe.play" % "play-java-ebean_2.11" % "2.3.8"
)
|
然后源码下载下来了, 看了报错信息, 原来是javadoc下载不下来 = =
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
| [test-project] $ updateClassifiers
[info] Updating {file:/home/caorong/workspace_scala/pic-share/}pic-share...
[info] Resolving jline#jline;2.12 ...
[warn] [FAILED ] com.typesafe.play#play_2.11;2.3.8!play_2.11.jar(doc): (0ms)
[warn] ==== local: tried
[warn] /home/caorong/.ivy2/local/com.typesafe.play/play_2.11/2.3.8/docs/play_2.11-javadoc.jar
[warn] ==== local-Maven-Repository: tried
[warn] /~/.m2/repository/jar/com.typesafe.play/play_2.11/2.3.8/docs/play_2.11-javadoc.jar
[warn] ==== typesafe-ivy-releases: tried
[warn] https://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.play/play_2.11/2.3.8/docs/play_2.11-javadoc.jar
[warn] ==== typesafe-maven-release: tried
[warn] http://repo.typesafe.com/typesafe/maven-releases/com/typesafe/play/play_2.11/2.3.8/play_2.11-2.3.8-javadoc.jar
[warn] ==== typesafe-release: tried
[warn] http://repo.typesafe.com/typesafe/releases/com/typesafe/play/play_2.11/2.3.8/play_2.11-2.3.8-javadoc.jar
[warn] ==== public: tried
[warn] https://repo1.maven.org/maven2/com/typesafe/play/play_2.11/2.3.8/play_2.11-2.3.8-javadoc.jar
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: FAILED DOWNLOADS ::
[warn] :: ^ see resolution messages for details ^ ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.typesafe.play#play_2.11;2.3.8!play_2.11.jar(doc)
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[trace] Stack trace suppressed: run last *:update for the full output.
[error] (*:update) sbt.ResolveException: download failed: com.typesafe.play#play_2.11;2.3.8!play_2.11.jar(doc)
[error] Total time: 4 s, completed 2015-5-2 16:19:55
|
列一下 本地cache
1
2
3
4
5
6
7
8
9
10
11
12
| caorong@caorong-ub2 ~/.ivy2/cache/com.typesafe.play/play_2.11
$ tree
.
├── ivy-2.3.8.xml
├── ivy-2.3.8.xml.original
├── ivydata-2.3.8.properties
├── jars
│ └── play_2.11-2.3.8.jar
└── srcs
└── play_2.11-2.3.8-sources.jar
2 directories, 5 files
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
| caorong@caorong-ub2 ~/.ivy2/cache/com.typesafe.play/play-java-ebean_2.11
$ tree
.
├── 2.3.8
│ ├── ivys
│ │ ├── ivy.xml
│ │ ├── ivy.xml.md5
│ │ └── ivy.xml.sha1
│ └── jars
│ ├── play-java-ebean_2.11.jar
│ ├── play-java-ebean_2.11.jar.md5
│ └── play-java-ebean_2.11.jar.sha1
├── ivy-2.3.8.xml
├── ivy-2.3.8.xml.original
├── ivydata-2.3.8.properties
├── jars
│ └── play-java-ebean_2.11-2.3.8.jar
└── srcs
└── play-java-ebean_2.11-2.3.8-sources.jar
|
javadoc 果然没下载下来
查了下远程仓库
确实就是没有javadoc
可是为什么我 updateClassifiers 的时候不直接帮我静默把 source下载下来呢
而是这样错也不报, 也不知道到底哪里的问题
这方面感觉 maven 更好用
idea
最后导入 idea 选择 SBT project, 因为本地已经装了sbt, 修改下自己的sbt的path, 以及添加 idea 的env 就是上面的 SBT_OPTS="-Dsbt.override.build.repos=true 不然在idea里面 他又会走默认的地址了
debug
由于 play 是由 sbt 启动的, 所以调试也就只能通过启动参数加上远程调试的参数(顺便把 sbt 也一起调试了). 通过看 sbt 的脚本发现, SBT_OPTS 和 JAVA_OPTS 都可以设置, 或者直接 sbt 自带 -jvm-debug 原理都一样
1
2
3
4
5
| $ env SBT_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=9999" sbt
$ env JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=9999" sbt
$ sbt -jvm-debug 9999
|
总结
sbt 没 maven 好用 = =
reference
http://stackoverflow.com/questions/3868863/how-to-specify-jvm-maximum-heap-size-xmx-for-running-an-application-with-run
http://www.scala-sbt.org/release/docs/Proxy-Repositories.html
http://stackoverflow.com/questions/22794149/scala-play-sbt-change-order-of-resolvers
http://www.plotprojects.com/create-an-intellij-idea-project-with-library-sources-attached/
http://www.scala-sbt.org/0.13.5/docs/Detailed-Topics/Library-Management.html
