Stash apply result in conflicts even there are no conflicts different from command line [message #1729444] |
Thu, 14 April 2016 08:43 |
kishore routhu Messages: 4 Registered: March 2014 |
Junior Member |
|
|
I am using the jgit api versioned 3.6.0.201411121045-m1.
I have some local changes im my repository and doing the following steps.
1. Stage the all local changes.
2. Stash these changes.
3. Pull the remote changes to local.
4. And made some local changes ( ex: pom.xml ) which doesn't result in any conflict.
5. Stash apply the changes on latest commit.
Results : Applying stashed changes resulted in a conflict
org.eclipse.jgit.api.errors.StashApplyFailureException: Applying stashed changes resulted in a conflict
But it doesn't show any conflicts and stash is not applying.
If i do the 5th step manually through (git stash apply) it is successfull and showing all changes from the stash also.
Why these difference between COMMAND and API ?
Is the version 3.6.0.201411121045-m1 should be changed in my dependency section ?
If version needs to be upgraded then what is the suggested version for this fix ?
Any suggestions will be appreciated
Thank You
[Updated on: Thu, 14 April 2016 08:44] Report message to a moderator
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04185 seconds