Hi All, I see that most of current activity is in CPI’s within the modules directory. Can I use this window of time and request for a lock on the airavata-api directory for couple of days? I want to use this time to liberally organize the client and server packages. I just committed a mock of Airavata API client and server and I learnt lot of do’s and don’ts. Changes to airavata-api should not impact any of the development within modules (as of now, since they are not integrated). My goal is to accomplish the following:
* A client distribution which has no transitive dependencies to any server side jars other than the model, logging and client side security. * A simple client distribution at the same time have it modularized so any changes to thrift interfaces and re-generation of stubs/skeltons is seamless * A server deployment package and a shell script to start stop the service. Please let me know if this is hindering anyone’s work. Suresh
