Skip to content

Commit e54479e

Browse files
committed
updated notes and readme for 0.7.1
1 parent fd0fd17 commit e54479e

File tree

2 files changed

+16
-22
lines changed

2 files changed

+16
-22
lines changed

README.md

Lines changed: 11 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -38,25 +38,9 @@ How to use it?
3838
addSbtPlugin("com.tuplejump" % "sbt-yeoman" % "play-compatible-version")
3939
4040
```
41-
play-compatible-version = 0.7.0 for Play 2.3.0 and 0.6.4 for Play 2.2.x
41+
play-compatible-version = 0.7.1 for Play 2.3.0 and 0.6.4 for Play 2.2.x
4242

43-
If you are really impatient or are using Scala 2.11, you can use the 0.7.1-SNAPSHOT using the following code.
44-
45-
```
46-
47-
resolvers += Resolver.sonatypeRepo("snapshots")
48-
49-
addSbtPlugin("com.tuplejump" % "sbt-yeoman" % "0.7.1-SNAPSHOT")
50-
51-
```
52-
53-
You will also have to add the snapshot resolver to build (project/Build.scala orr build.sbt) file too,
54-
55-
```
56-
57-
resolvers += Resolver.sonatypeRepo("snapshots")
58-
59-
```
43+
Note: support for Scala 2.11 is available from version 0.7.1
6044

6145

6246
3) Import Yeoman classes in the project build adding the following import to `project/Build.scala`,
@@ -80,7 +64,7 @@ Using 0.6.4
8064
```
8165

8266

83-
Using 0.7.0
67+
Using 0.7.1
8468

8569
```scala
8670
val appSettings = Seq(version := appVersion, libraryDependencies ++= appDependencies) ++
@@ -171,7 +155,7 @@ user yo-demo> sbt
171155
172156
```
173157

174-
Note: If you are using Scala Templates support in play-yeoman 0.7.0, ensure that "htmlmin" task is not called during the "build" since it does not understand Scala templates. This can be done by updating the build task in Gruntfile.js,
158+
Note: If you are using Scala Templates support in play-yeoman 0.7.1, ensure that "htmlmin" task is not called during the "build" since it does not understand Scala templates. This can be done by updating the build task in Gruntfile.js,
175159

176160
```
177161
grunt.registerTask('build', [
@@ -226,7 +210,7 @@ Using 0.6.4
226210
227211
```
228212

229-
Using 0.7.0
213+
Using 0.7.1
230214

231215
```
232216
val appSettings = Seq(version := appVersion, libraryDependencies ++= appDependencies) ++
@@ -244,7 +228,7 @@ Using 0.7.0
244228

245229
* Look at the yo-demo project for details!
246230

247-
Note: In 0.7.0, play-yeoman supports compilation of views from the yeoman directory but cannot recompile them when they are modified with the server running. You will need to stop the server and start it again.
231+
Note: In 0.7.1, play-yeoman supports compilation of views from the yeoman directory but cannot recompile them when they are modified with the server running. You will need to stop the server and start it again.
248232

249233
* If you use scala template support, you need to run grunt prior to compile else the template code will not be generated. This is not required if you execute run or stage directly since they have a dependency on grunt.
250234

@@ -264,6 +248,11 @@ For this purpose play-yeoman provides 2 settings that you can use in you play pr
264248
2) yeoman.devDirs - This is a List of String that takes a list of locations where play-yeoman should look for files in development mode i.e. when run using sbt run.
265249

266250

251+
Note: Starting from 0.7.1, it is possible to disable force option on execution of grunt tasks. This can be done by adding the following to the application build settings,
252+
253+
```
254+
Yeoman.forceGrunt := false
255+
```
267256

268257
Licence
269258
=======

notes/0.7.1.markdown

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
New in this release -
2+
3+
+ Support for Scala 2.11
4+
+ fixes #50
5+
+ a setting to disable --force option on grunt tasks (fixes #40)

0 commit comments

Comments
 (0)