-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
play2 tomcat war not deploying #307
Comments
Play 2.5 is not supported yet. Can you try with Play 2.4.x ? |
Thx very much for your quickly response! so i changed plugins.sbt to versio 2.4.4: // The Play plugin addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.4.4") // Web plugins // Play enhancer - this automatically generates getters/setters for public fields // Play Ebean support, to enable, uncomment this line, and enable in your build.sbt using The error continues localhost.log:
|
When do you have this stacktrace ? When Tomcat shutdowns ? |
when i start the Tomcat, the .war is inside the webapps directory |
so i tried with tomcat 7, but the error persist, y changed the servletVersion to 3.0. This is the error that appears in the Catalina.out when i try to deploy Mar 17, 2016 8:56:12 AM org.apache.catalina.loader.WebappClassLoaderBase validateJarFile |
I have also found the same error, doing the exact same process (initially started with 2.5.x, then downgrading to 2.4.6). Below are the config files and stacktrace: Current stack:
plugins.sbt
build.sbt
application log
Any help or hint will be greatly appreciated :) |
Any news on this issue? I'm facing the same problem as @pawitk |
Sorry, it's been a while, and my memory's fuzzy, but here's a gist of what I did to get it to work. I remember creating a new play 2.4.6 project and moving my code over. From this, i discovered that some classes were using ebean syntax compatible with only 2.5. After another thorough code cleanup, and more debugging, it finally worked. Wish I could be more specific, but due to time constraints, I didn't document my method. Hope you don't have to go through what I did. |
@pawitk thanks! I'll give it a try! |
I figured it out, I was still polluting the project with Play 2.5 specific code. There is a small issue with newly introduced logging in Play 2.5 that is not yet in play2war. See: https://www.playframework.com/documentation/2.5.x/Migration25 My code was also referencing to cached Play 2.5 code that caused more problems. |
Hi i'm having an issue trying to deploy a war file with the war plugin on tomcat 8
parameters:
java play 2.5.x
tomcat 8
java 8
plugins.sbt:
// The Play plugin
addSbtPlugin("com.github.play2war" % "play2-war-plugin" % "1.4-beta1")
addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.5.0")
// Web plugins
addSbtPlugin("com.typesafe.sbt" % "sbt-coffeescript" % "1.0.0")
addSbtPlugin("com.typesafe.sbt" % "sbt-less" % "1.1.0")
addSbtPlugin("com.typesafe.sbt" % "sbt-jshint" % "1.0.3")
addSbtPlugin("com.typesafe.sbt" % "sbt-rjs" % "1.0.7")
addSbtPlugin("com.typesafe.sbt" % "sbt-digest" % "1.1.0")
addSbtPlugin("com.typesafe.sbt" % "sbt-mocha" % "1.1.0")
addSbtPlugin("org.irundaia.sbt" % "sbt-sassify" % "1.4.2")
addSbtPlugin("com.typesafe.sbt" % "sbt-play-ebean" % "3.0.0")
// Play enhancer - this automatically generates getters/setters for public fields
// and rewrites accessors of these fields to use the getters/setters. Remove this
// plugin if you prefer not to have this feature, or disable on a per project
// basis using disablePlugins(PlayEnhancer) in your build.sbt
addSbtPlugin("com.typesafe.sbt" % "sbt-play-enhancer" % "1.1.0")
// Play Ebean support, to enable, uncomment this line, and enable in your build.sbt using
// enablePlugins(PlayEbean).
// addSbtPlugin("com.typesafe.sbt" % "sbt-play-ebean" % "1.0.0")
build.sbt:
import com.github.play2war.plugin._
name := """AuditoriaCip"""
version := "1.0-SNAPSHOT"
Play2WarPlugin.play2WarSettings
Play2WarKeys.servletVersion := "3.1"
lazy val root = (project in file(".")).enablePlugins(PlayJava, PlayEbean)
scalaVersion := "2.11.7"
libraryDependencies ++= Seq(
javaJdbc,
cache,
"mysql" % "mysql-connector-java" % "5.1.38",
"org.avaje.ebeanorm" % "avaje-ebeanorm" % "6.8.1",
javaWs
)
fork in run := true
this is the localhost.log file when i try to start de application:
The text was updated successfully, but these errors were encountered: