Hello DImuthu, The maven build is successful on develop-jupyter merge. Right now, the merge branch has workflow based functions that are in jupyter-integ. Is that okay or not.
And I'm interested to know how you were able to test File API's and what steps to follow in order to use them. I did push the changes to mergeJupyter branch on my fork-repo: https://github.com/Keerthi4308/airavata/tree/mergeJupyter Thank you, Keerthi On Wed, Apr 24, 2019 at 11:02 AM Keerthi N <[email protected]> wrote: > Hello DImuthu, > > As you suggested I did merge jupyter-integration branch on to develop > branch and fixed merge conflicts and almost all maven build issues except > one, which is symbol not found error for some classes say > getParser,..uploadFiletoStorage in RegistryService.java. The same functions > are not identified in RegistryServerHandler and AiravatServiceHandler.java. > I tried checking maven dependencies of registry-api-server (pom.xml) but > that didn't resolve. Please guide me how to resolve this issue. > > In general also, on my local develop branch where Airavta build is > successful, the RegistryServerHandler.java and AiravataServerHandler.java > have Airavata, RegistryService import statements marked in red. > > Apart from this, I attempted to generate Airavata and RegistryService.java > files using airvata_api.thrift, registry-api.thrift but they have issues > related to thrift.annotations to be resolved. > > Thanks, > Keerthi > > > >
