Problem with compiling Java classes

Hello,

I have problem with compiler which are not much talkative about error and I don’t know how to debug this issue. Can you please give me some advice?

Java with play framework version: 2.5.16
scalaVersion := “2.11.7”

[info] Compiling 6 Scala sources and 230 Java sources to /home/landsman/projects/api/site/target/scala-2.11/classes...
[info] /home/landsman/projects/api/site/app/actors/security/Sign.java: Some input files use or override a deprecated API.
[info] /home/landsman/projects/api/site/app/actors/security/Sign.java: Recompile with -Xlint:deprecation for details.
[info] /home/landsman/projects/api/site/app/actors/messenger/MessageManager.java: /home/landsman/projects/api/site/app/actors/messenger/MessageManager.java uses unchecked or unsafe operations.
[info] /home/landsman/projects/api/site/app/actors/messenger/MessageManager.java: Recompile with -Xlint:unchecked for details.
java.io.FileNotFoundException: /home/landsman/projects/api/site/target/scala-2.11/classes/messages (Is a directory)
	at java.io.FileOutputStream.open0(Native Method)
	at java.io.FileOutputStream.open(FileOutputStream.java:270)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
	at sbt.Using$$anonfun$fileOutputChannel$1.apply(Using.scala:75)
	at sbt.Using$$anonfun$fileOutputChannel$1.apply(Using.scala:75)
	at sbt.Using$$anon$2.openImpl(Using.scala:65)
	at sbt.OpenFile$class.open(Using.scala:43)
	at sbt.Using$$anon$2.open(Using.scala:64)
	at sbt.Using$$anon$2.open(Using.scala:64)
	at sbt.Using.apply(Using.scala:23)
	at sbt.IO$$anonfun$copyFile$3.apply(IO.scala:653)
	at sbt.IO$$anonfun$copyFile$3.apply(IO.scala:652)
	at sbt.Using.apply(Using.scala:24)
	at sbt.IO$.copyFile(IO.scala:652)
	at sbt.Sync$.copy(Sync.scala:51)
	at sbt.Sync$$anonfun$apply$1$$anonfun$apply$2.apply(Sync.scala:43)
	at sbt.Sync$$anonfun$apply$1$$anonfun$apply$2.apply(Sync.scala:43)
	at scala.Function2$$anonfun$tupled$1.apply(Function2.scala:54)
	at scala.Function2$$anonfun$tupled$1.apply(Function2.scala:53)
	at scala.collection.immutable.Stream.foreach(Stream.scala:547)
	at sbt.Sync$$anonfun$apply$1.apply(Sync.scala:43)
	at sbt.Sync$$anonfun$apply$1.apply(Sync.scala:22)
	at sbt.Defaults$$anonfun$copyResourcesTask$1.apply(Defaults.scala:975)
	at sbt.Defaults$$anonfun$copyResourcesTask$1.apply(Defaults.scala:971)
	at scala.Function4$$anonfun$tupled$1.apply(Function4.scala:35)
	at scala.Function4$$anonfun$tupled$1.apply(Function4.scala:34)
	at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
	at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
	at sbt.std.Transform$$anon$4.work(System.scala:63)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
	at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
	at sbt.Execute.work(Execute.scala:237)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
	at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
	at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Folder in path: /target/scala-2.11/classes exists and there is relevant content I think.

Hi @landsman,

it looks like you have a folder named messages, but that’s a reserved name for messages files with translations. See https://www.playframework.com/documentation/2.8.x/JavaI18N#Externalizing-messages.

Cheers

1 Like

@ignasi35 Wow, you are life-saver! Thank you!

Is there some issue (or is already resolved?) for more clear error messages like that for latest version?

Hmm, I don’t know if there’s such an issue or the message already improved to be honest. I agree with you that it’d be nice to have.

1 Like