webdevelopersdiary play2-maven-plugin issues

webdevelopersdiary / play2-maven-plugin

Automatically exported from code.google.com/p/play2-maven-plugin

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Mavenize Play! SecureSocial Module v.2.1.2

#18 GoogleCodeExporter closed 9 years ago
1
Improve SBT Compilation mojos

#17 GoogleCodeExporter closed 9 years ago
4
play2:dist

#16 GoogleCodeExporter closed 9 years ago
3
Mavenize Play! WebJars Module v.2.1.0-3 and v2.2.0

#15 GoogleCodeExporter closed 9 years ago
1
Mavenize Play! SecureSocial Module v.2.1.1

#14 GoogleCodeExporter closed 9 years ago
1
Mavenize Play! Deadbolt Module v.2.2-RC1

#13 GoogleCodeExporter closed 9 years ago
2
Mavenize Play! Deadbolt Module v.2.1

#12 GoogleCodeExporter closed 9 years ago
2
Remove tricky mainLang autodetection mechanism

#11 GoogleCodeExporter closed 9 years ago
1
Add "scalacOptions" and "javacOptions" configuration parameters

#10 GoogleCodeExporter closed 9 years ago
1
Add "mainLang" configuration parameter to avoid autodetection

#9 GoogleCodeExporter closed 9 years ago
1
dist goal does not include the project itself in the classpath inside the start script

#8 GoogleCodeExporter closed 9 years ago
6
Make plugin Play 2.1.x and 2.2.x compatible

#7 GoogleCodeExporter closed 9 years ago
4
Play only starts in Prod mode when using the play2:run goal

#6 GoogleCodeExporter opened 9 years ago
9
Need to have the Request Body in onError

#5 GoogleCodeExporter closed 9 years ago
3
Need some configurable file(s) outside the jar with play2-war-plugin

#4 GoogleCodeExporter closed 9 years ago
1
Enable full debug information on compile

#3 GoogleCodeExporter closed 9 years ago
9
unmappable character for encoding Cp1252 even if project.build.sourceEncoding is set to UTF-8

#2 GoogleCodeExporter closed 9 years ago
9
unmanaged dependencies in lib directory not included in classpath during compilation

#1 GoogleCodeExporter closed 9 years ago
2