I get this error message when running Play 2.1.2 and Solr 4.4.0 in IntelliJ. I didn't have this before and don't understand where it comes from. Tried cleaning project many times. Thanks in advance for your help!
[info] Resolving com.googlecode.concurrentlinkedhashmap#concurrentlinkedhashmap-
[warn] module not found: org.restlet.jee#org.restlet;2.1.1
[warn] ==== local: tried
[warn] [...]\Play212\repository\local\org.restlet.jee\org.restlet\2.1.1\iv
ys\ivy.xml
[warn] ==== Typesafe Releases Repository: tried
[warn] http://repo.typesafe.com/typesafe/releases/org/restlet/jee/org.restlet/
2.1.1/org.restlet-2.1.1.pom
[warn] ==== Typesafe Snapshots Repository: tried
[warn] http://repo.typesafe.com/typesafe/snapshots/org/restlet/jee/org.restlet
/2.1.1/org.restlet-2.1.1.pom
[warn] ==== public: tried
[warn] http://repo1.maven.org/maven2/org/restlet/jee/org.restlet/2.1.1/org.res
tlet-2.1.1.pom
[warn] module not found: org.restlet.jee#org.restlet.ext.servlet;2.1.1
[warn] ==== local: tried
[warn] [...]\Play212\repository\local\org.restlet.jee\org.restlet.ext.serv
let\2.1.1\ivys\ivy.xml
[warn] ==== Typesafe Releases Repository: tried
[warn] http://repo.typesafe.com/typesafe/releases/org/restlet/jee/org.restlet.
ext.servlet/2.1.1/org.restlet.ext.servlet-2.1.1.pom
[warn] ==== Typesafe Snapshots Repository: tried
[warn] http://repo.typesafe.com/typesafe/snapshots/org/restlet/jee/org.restlet
.ext.servlet/2.1.1/org.restlet.ext.servlet-2.1.1.pom
[warn] ==== public: tried
[warn] http://repo1.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2
.1.1/org.restlet.ext.servlet-2.1.1.pom
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: org.restlet.jee#org.restlet;2.1.1: not found
[warn] :: org.restlet.jee#org.restlet.ext.servlet;2.1.1: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[error] (*:update) sbt.ResolveException: unresolved dependency: org.restlet.jee#
org.restlet;2.1.1: not found
[error] unresolved dependency: org.restlet.jee#org.restlet.ext.servlet;2.1.1: no
t found
It looks like you are trying to import the Restlet framework as an external dependency.
This won't work, because by default, sbt (the build tool that Play uses) only checks Typesafe's repository and Maven central. I could not find Restlet at Maven central, and indeed, on their download page, they write:
The Maven repository for Restlet is accessible from
http://maven.restlet.org and contains all Restlet JARs and third party
dependencies that aren't available in the main public Maven
repository. [...]
This means that you have to tell SBT somehow where to look for the dependency.
A quick look into Play's documentation reveals that you need to add a line to your project/Build.scala:
resolvers += "Restlet Repository" at "http://maven.restlet.org"
Related
flink cluster version: flink-1.7.2-bin-scala_2.11
And it is a docker cluster.
My project structure:
--lib
+- src/main/scala
+- pom.xml
--job
+- src/main/scala
+- pom.xml
pom.xml
There are two submodules to this project.
Then I made a fat jar , and upload from web UI.Then I got this Exception:
ERROR org.apache.flink.runtime.webmonitor.handlers.JarRunHandler - Exception occurred in REST handler: org.apache.flink.client.program.ProgramInvocationException: The main method caused an error.
without the stack trace.
But Running in IDE is OK.
I am trying to build Apache Zeppelin 0.8 SNAPSHOT using the source on GitHub.
Zeppelin Server build is failing with errors, any idea on the root cause for build failure?
[INFO] Zeppelin: Server ................................... FAILURE [
16.743 s]
[INFO] Zeppelin: Jupyter Support .......................... SKIPPED
[INFO] Zeppelin: Packaging distribution ................... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 26.483 s
[INFO] Finished at: 2017-08-23T05:20:34-07:00
[INFO] Final Memory: 68M/341M
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
(default-compile) on project zeppelin-server: Compilation failure:
Compilation failure: [ERROR]
/home/apache/zeppelin/zeppelin-server/src/main/java/org/apache/zeppelin/server/CorsFilter.java:[86,76]
cannot find symbol
[ERROR] symbol: method getStrictTransport()
[ERROR] location: variable zeppelinConfiguration of type
org.apache.zeppelin.conf.ZeppelinConfiguration
[ERROR]
/home/apache/zeppelin/zeppelin-server/src/main/java/org/apache/zeppelin/server/CorsFilter.java:[88,65]
cannot find symbol
[ERROR] symbol: method getXxssProtection() [ERROR] location:
variable zeppelinConfiguration of type
org.apache.zeppelin.conf.ZeppelinConfiguration
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with
the command
[ERROR] mvn -rf :zeppelin-server
In my sbt project in Scala 2.12 I am using IntelliJ IDEA and want to import scalatest.
In order to install the recommended SuperSafe Community Edition Scala compiler plugin. I followed the instruction here.
My plugin.sbt:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.2")
the error showed by the Intellij import is:
SBT project import
[warn] [FAILED ] com.artima.supersafe#sbtplugin;1.1.2!sbtplugin.jar(src): (0ms)
[warn] ==== typesafe-ivy-releases: tried
[warn] https://repo.typesafe.com/typesafe/ivy-releases/com.artima.supersafe/sbtplugin/scala_2.10/sbt_0.13/1.1.2/srcs/sbtplugin-sources.jar
[warn] ==== sbt-plugin-releases: tried
[warn] https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.artima.supersafe/sbtplugin/scala_2.10/sbt_0.13/1.1.2/srcs/sbtplugin-sources.jar
[warn] ==== local: tried
[warn] /Users/salvob/.ivy2/local/com.artima.supersafe/sbtplugin/scala_2.10/sbt_0.13/1.1.2/srcs/sbtplugin-sources.jar
[warn] ==== public: tried
[warn] https://repo1.maven.org/maven2/com/artima/supersafe/sbtplugin_2.10_0.13/1.1.2/sbtplugin-1.1.2-sources.jar
[warn] ==== Artima Maven Repository: tried
[warn] http://repo.artima.com/releases/com/artima/supersafe/sbtplugin_2.10_0.13/1.1.2/sbtplugin-1.1.2-sources.jar
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: FAILED DOWNLOADS ...
Maybe incompatility with new Scala Version?
Try the following:
When we add the plug-in in projects/build.sbt:
addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.2")
We must not add the above plug-in anywhere else
Add to ~/.sbt/0.13/global.sbt
resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
Do not add this resolver anywhere else
Make sure you have an empty line before and after each of the sbt lines
HTHs
I'm getting this error when running my web application that use GWT, GWT-Platform and App engine:
Generator 'com.google.gwt.inject.rebind.GinjectorGenerator' threw an
exception while rebinding 'com.myapp.client.gin.ClientGinjector'
My application have these jars in the WEB-INF/lib folder:
guice-3.0.jar
gin-1.5-post-gwt-2.2.jar
guice-servlet-3.0.jar
gwtp-all-0.7.jar
Here's the detailed error log of Development Mode:
[DEBUG] [app] - Validating newly compiled units [DEBUG] [app] -
Rebinding com.myapp.client.gin.ClientGinjector [DEBUG] [app] -
Invoking generator com.google.gwt.inject.rebind.GinjectorGenerator
[ERROR] [app] - Generator
'com.google.gwt.inject.rebind.GinjectorGenerator' threw an exception
while rebinding 'com.myapp.client.gin.ClientGinjector'
[ERROR] [app] - Deferred binding failed for
'com.myapp.client.gin.ClientGinjector'; expect subsequent failures
[ERROR] [app] - Failed to create an instance of
'com.myapp.client.MainAppEntryPoint' via deferred binding
[ERROR] [app] - Unable to load module entry point class
com.myapp.client.MainAppEntryPoint (see associated exception for
details)
[ERROR] [app] - Failed to load module 'app' from user agent
'Mozilla/5.0 (Windows NT 6.1) AppleWebKit/536.11 (KHTML, like Gecko)
Chrome/20.0.1132.57 Safari/536.11' at 127.0.0.1:53782
I've been trying to figure out what could have been missing in my application but I still can't find the fix? What is causing this kind of error?
Often times this is due to adding non gwt supported types or imports such as java.net.* etc in your client folders of a gwt project. Only java types that are supported in the gwt white list are supported and can be searialized. the rebinding errors mask those errors. So comb through your project and see if you have those types and imports included in either client or shared folders
When i try to build (mvn) the slide-show plugin, i get error:
(see detaied stdout below)
mvn -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[WARNING] POM for 'org.kohsuke.stapler:maven-stapler-plugin:pom:1.15:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: org.kohsuke.stapler:maven-stapler-plugin
POM Location: /home/kahmed/.m2/repository/org/kohsuke/stapler/maven-stapler-plugin/1.15/maven-stapler-plugin-1.15.pom
Reason: Not a v4.0.0 POM. for project org.kohsuke.stapler:maven-stapler-plugin at /home/kahmed/.m2/repository/org/kohsuke/stapler/maven-stapler-plugin/1.15/maven-stapler-plugin-1.15.pom
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project for plugin 'org.kohsuke.stapler:maven-stapler-plugin': Not a v4.0.0 POM. for project org.kohsuke.stapler:maven-stapler-plugin at /home/kahmed/.m2/repository/org/kohsuke/stapler/maven-stapler-plugin/1.15/maven-stapler-plugin-1.15.pom
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1599)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeHandlersInPlugins(DefaultLifecycleExecutor.java:1468)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:222)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:178)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build project for plugin 'org.kohsuke.stapler:maven-stapler-plugin': Not a v4.0.0 POM. for project org.kohsuke.stapler:maven-stapler-plugin at /home/kahmed/.m2/repository/org/kohsuke/stapler/maven-stapler-plugin/1.15/maven-stapler-plugin-1.15.pom
at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:293)
at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184)
at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1626)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582)
... 15 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. for project org.kohsuke.stapler:maven-stapler-plugin at /home/kahmed/.m2/repository/org/kohsuke/stapler/maven-stapler-plugin/1.15/maven-stapler-plugin-1.15.pom
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1599)
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1571)
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:562)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:277)
... 19 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Mon Apr 16 00:32:26 EDT 2012
[INFO] Final Memory: 15M/182M
[INFO] ------------------------------------------------------------------------
I am getting this too (although its for the akuma artifact) and can explain why, but have not yet found a good solution. Both define a parent POM and a new repo:
<parent>
<groupId>org.kohsuke</groupId>
<artifactId>pom</artifactId>
<version>2</version>
</parent>
<repositories>
<repository>
<id>m.g.o-public</id>
<url>http://maven.glassfish.org/content/groups/public/</url>
</repository>
</repositories>
The URL for this glassfish maven repo gives a 301 to https://maven.glass... and for some reason, maven decides to download the body of that response as the POM. If you look in your ~/.m2/repository/org/kohsuke/pom/2/pom-2.pom, you should see something like:
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/0.6.39</center>
</body>
</html>
Manually looking at the glassfish repo, I do not even see the desired parent POM (at this time).
I hope this helps. If you are able to figure it out, please post back as this is as far as I have gotten so far!
I had this problem also, with a different POM from another project, and I was attempting to build with Maven 3.X. The simple solution was to install the most recent 2.X version of Maven. After that, it built fine. Being a Maven novice, It appears the URI format for REPOS differs between the 2 versions.
Simply install Maven 2.X (I used 2.2.1), and put it's "bin" directory first in your PATH env variable, and you should be good to go.