Suspected the same. Your solution worked. Thanks!
On Tue, Dec 2, 2014 at 11:09 AM, Jonathan Hurley
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
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 resul
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 fi
Excellent! This will speed up the process. Thanks for the quick response.
-Pankaj
On Mon, Nov 17, 2014 at 1:52 PM, John Speidel
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
>
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
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
