search

eclipse-archived / unide

Eclipse Public License 1.0
29 stars 17 forks source link

Could not find artifact org.eclipse.iot.unide.ppmp:ppmp-java-binding:jar:0.2.0-SNAPSHOT #26

Closed VolITSol closed 6 years ago

VolITSol commented 6 years ago

Hi,

I want to build unide but always get: [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] ppmp-schema ........................................ SUCCESS [ 9.562 s] [INFO] Unide .............................................. SUCCESS [ 0.842 s] [INFO] unide-servers ...................................... SUCCESS [ 0.856 s] [INFO] unide-server ....................................... FAILURE [ 5.429 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 17.035 s [INFO] Finished at: 2018-02-03T21:06:27+01:00 [INFO] Final Memory: 13M/245M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project ppmp-server: Could not resolve dependencies for project org.eclipse.iot.unide.ppmp:ppmp-server:jar:0.2.0-SNAPSHOT: Could not find artifact org.eclipse.iot.unide.ppmp:ppmp-java-binding:jar:0.2.0-SNAPSHOT -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project ppmp-server: Could not resolve dependencies for project org.eclipse.iot.unide.ppmp:ppmp-server:jar:0.2.0-SNAPSHOT: Could not find artifact org.eclipse.iot.unide.ppmp:ppmp-java-binding:jar:0.2.0-SNAPSHOT at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:245) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.eclipse.iot.unide.ppmp:ppmp-server:jar:0.2.0-SNAPSHOT: Could not find artifact org.eclipse.iot.unide.ppmp:ppmp-java-binding:jar:0.2.0-SNAPSHOT at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:211) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195) ... 23 more Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.eclipse.iot.unide.ppmp:ppmp-java-binding:jar:0.2.0-SNAPSHOT at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:205) ... 24 more Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.eclipse.iot.unide.ppmp:ppmp-java-binding:jar:0.2.0-SNAPSHOT at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367) ... 25 more Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.eclipse.iot.unide.ppmp:ppmp-java-binding:jar:0.2.0-SNAPSHOT at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:434) ... 27 more [ERROR] [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/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :ppmp-server

ameinhardt commented 6 years ago

Hi @VolITSol, thanks for pointing that out! Indeed there's a mistake in the documentation for the server: the first necessary dependency is now located in the unide.java repository. The second one (ppmp-schemas) will remain in this main repository. You would have to mvn install both first. Once we finalize a release they shall be available on maven central and you don't have to manually build the repositories. You should be able to successfully build the REST server after, can you?