Created attachment 783408 [details] clone exception response Description of problem: I'm currently unable to perform following scenario that is important for test automation: as a test setup I need to delete a repository and clone it again to get it into clean state. I perform these steps: 1. delete the repository using DELETE rest/repositories/$REPO 2. rm -rf .niogit/$REPO.git 3. clone again using POST rest/repositories/ + JSON data containing repo URL and name On the first run steps 1. and 2. have no effect and step 3. is successful, repo is cloned. Tests work with $REPO and create some commits. When the sequence is carried out again, step 1. removes $REPO from system.git, but doesn't touch .niogit/$REPO.git. That is done in step 2. After that, a fresh clone of $REPO should be created but the REST call throws exception this time. Version-Release number of selected component (if applicable): CR1 (community) How reproducible: always Steps to Reproduce: 1. clone a repository as $REPO 2. delete it 3. clear .niogit/$REPO.git 4. clone it again Actual results: XML response with exception stack trace Expected results: JSON data with successful status Additional info: 1. REST clone 2. REST delete 3. stop server 4. rm -rf 5. start server 6. REST clone Works.
FROM PORCELLI: ================= Bug fixed on master, pushing now to 6.0.x and 0.3.x http://github.com/droolsjbpm/kie-commons/commit/ceb906f0e http://github.com/droolsjbpm/uberfire/commit/a23f013be
Marked as requiring a release note for the beta release. Please add relevant information we need customers to be aware of to the doc text box above. Thanks Lee
Works perfect now.