When I try running showcase sample via maven (using "mvn test" and "mvn test -Ptest-java") I get:
[INFO] Scanning for projects...
[ERROR]
[ERROR] The project com.googlecode.playn:playn-showcase:1.0-SNAPSHOT (E:\Desarrollo\Git\playn-samples\showcase\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact com.googlecode.playn:playn-project:pom:1.4-SNAPSHOT and 'parent.relativePath' points at wrong local POM # line 6, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of errors, re-run Maven with the -e switch.
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
I can create projects via Maven but when I try to create a new playn 1.3.1 project via Eclipse I get:
'Creating playn-archetype' has encountered a problem.
Unable to create project from archetype
[com.googlecode.playn:playn-archetype:1.3.1]
Details: Unable to create project from archetype [com.googlecode.playn:playn-archetype:1.3.1]
The defined artifact is not an archetype
(The same happens with playn 1.4)
When I try to import a playn 1.3.1 or 1.4 project to Eclipse (created via Maven) I get the next error:
'Importing Maven projects' has encountered a problem.
An internal error ocurred during: "Importing Maven projects".
Details: An internal error occurred during: "Importing Maven projects".
com/android/io/StreamException
So I cannot run any project via Eclipse.
I use Eclipse Indigo 3.7, maven 3.0.4 and JDK 7u5; and I follow all the steps that shows playn getting started.
I think it is related to this bug: https://github.com/rgladwell/m2e-android/issues/89
You might try the master update site (http://rgladwell.github.com/m2e-android/updates/master/), till the new version is released from m2e-android.
Related
I am trying to run a "maven test" and I get this error in the console:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project gpdb-dispomap: Compilation failure
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[ERROR] -> [Help 1]
However, when I run a "clean install" it works and I don't get this message.
How can I resolve this?
This is my JDK settings:
Am trying to build Apache Spark 2.1.0 source, but get these errors below that baffle me...
Hadoop 2.8.0 was installed and is working
Scala 2.12.1 was installed in advance of executing the Spark install (Which seems to auto install Scala 2.11.8 ?!?)
My build line is:
build/mvn -Pyarn -Phadoop-2.7 -Dhadoop.version=2.7.0 -DskipTests clean package
Does anybody know why I get:
user#server:/usr/local/share/spark/spark-2.1.0$ sudo /usr/local/share/spark/spark-2.1.0/build/mvn -Pyarn -Phadoop-2.7 -Dhadoop.version=2.7.0 -DskipTests clean package
[sudo] password for user:
exec: curl --progress-bar -L https://downloads.typesafe.com/zinc/0.3.9/zinc-0.3.9.tgz
######################################################################## 100.0%
exec: curl --progress-bar -L https://downloads.typesafe.com/scala/2.11.8/scala-2.11.8.tgz
######################################################################## 100.0%
exec: curl --progress-bar -L https://www.apache.org/dyn/closer.lua?action=download&filename=/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
######################################################################## 100.0%
Using `mvn` from path: /usr/local/share/spark/spark-2.1.0/build/apache-maven-3.3.9/bin/mvn
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
[INFO] Scanning for projects...
Downloading: https://repo1.maven.org/maven2/org/apache/apache/14/apache-14.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.apache.spark:spark-parent_2.11:2.1.0: Could not transfer artifact org.apache:apache:pom:14 from/to central (https://repo1.maven.org/maven2): repo1.maven.org: Name or service not known and 'parent.relativePath' points at wrong local POM # line 22, column 11
#
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.apache.spark:spark-parent_2.11:2.1.0 (/usr/local/share/spark/spark-2.1.0/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.apache.spark:spark-parent_2.11:2.1.0: Could not transfer artifact org.apache:apache:pom:14 from/to central (https://repo1.maven.org/maven2): repo1.maven.org: Name or service not known and 'parent.relativePath' points at wrong local POM # line 22, column 11: Unknown host repo1.maven.org: Name or service not known -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
I tested downloading manually (To see if that was causing the errors), which downloads without issues:
https://repo1.maven.org/maven2/org/apache/apache/14/apache-14.pom
I also tested accessing the URL below, which also shows content:
https://repo1.maven.org/maven2
Hope somebody smart knows how to solve this...
I found out what the issue was:
I had to configure our proxy settings in the SETTINGS.XML in the directory:
/usr/local/share/spark/spark-2.1.0/build/apache-maven-3.3.9/conf
After editing the file, the build went without any issues :)
Hope this helps someone else running into the same issue...
EDIT: Just to be extra clear, having a working proxy configuration in bash only is NOT SUFFICIENT for the Maven Build to succeed. I was able to download all files from bash manually, but Maven needed the proxy configuration in the SETTINGS.XML file present as well...
I have a very simple web project in Eclipse that uses JSF and runs with a JBoss 4.2.3. I have 'Mavenized' the project and a pom.xml is generated. The pom.xml is empty with no dependencies, but I can install this maven project and I see my web page when I run the JBoss from eclipse. All fine till here.
Now I need to extend the logic of the java code and I need to add a new artifact generated from another project, and here is where my problem starts. When I add a dependency to this new artifact and I try the make a 'install' I am getting this error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project MyTest: Compilation failure: Compilation
failure:
[ERROR]
/home/daniel/workspace/valais/voba-switch/src/ch/steria/scada/sw/web/controller/SwitchController.java:[7,24]
package javax.faces.model does not exist
[ERROR]
/home/daniel/workspace/valais/voba-switch/src/ch/steria/scada/sw/web/controller/SwitchController.java:[45,13]
cannot find symbol
[ERROR] symbol : class SelectItem
I see the libraries missing are in the jboss-web.deployer directory of the JBoss. How can I link this libraries in the pom.xml or how can I get the right ones from the jboss maven repository for my jboss vesion?
Thanks,
Dani.
I just had to set the artifacts from JBoss as 'provided'.
Hello I'm very new to yang, I tried getting used to it and followed this tutorial page on : http://sdntutorials.com/yang-to-java-conversion-how-to-create-maven-project-in-eclipse/#comment-21958.
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.opendaylight.controller.model:Yang-03:0.0.1-SNAPSHOT (/home/shrenik/workspace/Yang-03/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact org.opendaylight.controller.model:model-parent:pom:1.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM # line 6, column 11 -> [Help 2]
I'm unable to resolve this issue. Any help would be appreciated.
Remove the <parent> section from your POM.
I'm pretty sure you neither have a POM org.opendaylight.controller.model:model-parent:pom:1.1-SNAPSHOT in your local Maven repository (~/.m2/repository) nor in your Eclipse workspace.
Don't ask me why the blog post insists on adding this without explaining why and how to establish it.
my problem is the following. I have Eclipse Kepler SR1 and imported an maven project out of the following git: http://git.eclipse.org/c/bpmn2/.git/
This is a metamodel for the BPMN 2.0. After that i wanted to do a maven install but when i do this the following Error pops up
[ERROR] Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.0.3:sign (sign) on project org.eclipse.bpmn2: Could not sign artifact org.eclipse.bpmn2:org.eclipse.bpmn2:eclipse-plugin:0.7.0-SNAPSHOT: Connection to http://build.eclipse.org:31338 refused: Connection timed out: connect -> [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/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :org.eclipse.bpmn2
Maven is correctly installed and i checked the superpom. There is no mistake in my opinion. I also updated the pluginRepository for plugin signin to https://repo.eclipse.org/content/repositories/cbi-releases/. Is there anyone who knows the mistake and can help me?
Best Regards
The first line of your error message contains a timeout for http://build.eclipse.org:31338 - that seems to me an internal address.
If I am not mistaken, this is used by the jar signer plug-in mentioned in the build script that is an eclipse.org-only service (for obvious reasons). Search for the followi
<groupId>org.eclipse.cbi.maven.plugins</groupId>
<artifactId>eclipse-jarsigner-plugin</artifactId>
As signing is an internal service, we in the EMF-IncQuery project execute signing only when a specific profile is selected, thus allowing building our project outside eclipse.org servers.