Suspected the same. Your solution worked. Thanks! On Tue, Dec 2, 2014 at 11:09 AM, Jonathan Hurley <[email protected]> wrote:
> Hi Pankaj, > > It looks like you have not built the entire project from the root at least > once. This will actually build the dependent modules, like ambari-views.jar > (which is what you’re missing). > > Since ambari-server depends on ambari-views, you’ll need to build > ambari-views and install the resulting JAR so that maven can find it when > building ambari-server. > > Try using “mvn package install” in ambari-views first. > > On Dec 2, 2014, at 12:04 PM, pankaj channe <[email protected]> wrote: > > > Hi John, > > > > When I try to build only ambari-server jar with 'mvn package > -DskipTests', > > I get following dependency exception. Any help on this? > > > > Failed to execute goal on project ambari-server: Could not resolve > > dependencies for project > > org.apache.ambari:ambari-server:jar:1.3.0-SNAPSHOT: Failure to find > > org.apache.ambari:ambari-views:jar:1.3.0-SNAPSHOT in > > https://oss.sonatype.org/content/groups/staging was cached in the local > > repository, resolution will not be reattempted until the update interval > of > > oss.sonatype.org has elapsed or updates are forced -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > > goal on project ambari-server: Could not resolve dependencies for project > > org.apache.ambari:ambari-server:jar:1.3.0-SNAPSHOT: Failure to find > > org.apache.ambari:ambari-views:jar:1.3.0-SNAPSHOT in > > https://oss.sonatype.org/content/groups/staging was cached in the local > > repository, resolution will not be reattempted until the update interval > of > > oss.sonatype.org has elapsed or updates are forced > > at > > > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210) > > at > > > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117) > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258) > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201) > > 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:84) > > at > > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > > at > > > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > > at > > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:622) > > at > > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > > at > > > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > > at > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > > Caused by: org.apache.maven.project.DependencyResolutionException: Could > > not resolve dependencies for project > > org.apache.ambari:ambari-server:jar:1.3.0-SNAPSHOT: Failure to find > > org.apache.ambari:ambari-views:jar:1.3.0-SNAPSHOT in > > https://oss.sonatype.org/content/groups/staging was cached in the local > > repository, resolution will not be reattempted until the update interval > of > > oss.sonatype.org has elapsed or updates are forced > > at > > > org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189) > > at > > > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185) > > ... 22 more > > Caused by: org.sonatype.aether.resolution.DependencyResolutionException: > > Failure to find org.apache.ambari:ambari-views:jar:1.3.0-SNAPSHOT in > > https://oss.sonatype.org/content/groups/staging was cached in the local > > repository, resolution will not be reattempted until the update interval > of > > oss.sonatype.org has elapsed or updates are forced > > at > > > org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375) > > at > > > org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183) > > ... 23 more > > Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: > > Failure to find org.apache.ambari:ambari-views:jar:1.3.0-SNAPSHOT in > > https://oss.sonatype.org/content/groups/staging was cached in the local > > repository, resolution will not be reattempted until the update interval > of > > oss.sonatype.org has elapsed or updates are forced > > at > > > org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538) > > at > > > org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216) > > at > > > org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358) > > ... 24 more > > Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: > Failure > > to find org.apache.ambari:ambari-views:jar:1.3.0-SNAPSHOT in > > https://oss.sonatype.org/content/groups/staging was cached in the local > > repository, resolution will not be reattempted until the update interval > of > > oss.sonatype.org has elapsed or updates are forced > > at > > > org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230) > > at > > > org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204) > > at > > > org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427) > > ... 26 more > > > > On Mon, Nov 17, 2014 at 2:27 PM, pankaj channe <[email protected]> > wrote: > > > >> Excellent! This will speed up the process. Thanks for the quick > response. > >> > >> -Pankaj > >> > >> On Mon, Nov 17, 2014 at 1:52 PM, John Speidel <[email protected] > > > >> wrote: > >> > >>> Hi Pankaj. > >>> > >>> Most of us use vagrant for running ambari on our laptops. You > shouldn't > >>> need to build the rpm, simply do 'mvn package -DskipTests' in the > >>> ambari-server directory when you make changes to produce the > ambari-server > >>> jar. You should share a directory from the host to the vm so that the > vm > >>> can use the updated jar file. Then all you need to do to have ambari > pick > >>> up the change is 'ambari-server restart'. > >>> > >>> You can enable remote debugging by modifying the file' > >>> /usr/sbin/ambari-server.py' on the vm and change the debug property to > >>> true: SERVER_START_DEBUG = True > >>> > >>> This is all described in more detail at: > >>> https://cwiki.apache.org/confluence/display/AMBARI/Quick+Start+Guide > >>> > >>> -John > >>> > >>> On Mon, Nov 17, 2014 at 2:38 PM, pankaj channe <[email protected]> > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> I am working on fixing some of the issues on ambari-server api's. Just > >>>> wondering if there is an easy alternate way of testing changes in the > >>> api > >>>> code without having to go through the path: > >>>> > >>>> Make changes in local -> run tests ->build rpm -> reinstall > >>> ambari-server > >>>> on host > >>>> > >>>> I am currently using local VM's. Any suggestions are welcome. > >>>> > >>>> Thanks, > >>>> Pankaj Channe > >>>> > >>> > >>> -- > >>> CONFIDENTIALITY NOTICE > >>> NOTICE: This message is intended for the use of the individual or > entity > >>> to > >>> which it is addressed and may contain information that is confidential, > >>> privileged and exempt from disclosure under applicable law. If the > reader > >>> of this message is not the intended recipient, you are hereby notified > >>> that > >>> any printing, copying, dissemination, distribution, disclosure or > >>> forwarding of this communication is strictly prohibited. If you have > >>> received this communication in error, please contact the sender > >>> immediately > >>> and delete it from your system. Thank You. > >>> > >> > >> > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
