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.
