[jbosstools-issues] [JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commits that I can publish even though there are none

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787295#comment-12787295 ] 

Andre Dietisheim commented on JBIDE-15059:
------------------------------------------

file 2 new PR's:
MASTER: https://github.com/jbosstools/jbosstools-openshift/pull/187
CR1: https://github.com/jbosstools/jbosstools-openshift/pull/185

                
> Server adapter: tells me that there are local commits that I can publish even though there are none
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15059
>                 URL: https://issues.jboss.org/browse/JBIDE-15059
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.1.0.CR1
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>              Labels: respin-a
>             Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
>         Attachments: already-up-to-date.png, committed-changes-to-publish.png, is-ahead-0.png, is-ahead-1.png
>
>
> 1. EXEC: launch OpenShift Application wizard
> 2. EXEC: create a new application and have it imported to your workspace
> 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so by hitting *Yes*
> !committed-changes-to-publish.png!
> 4. ASSERT: In the Package Explorer: the freshly imported project is decorated with an arrow an a 1 (is ahead of origin by 1)
> !is-ahead-1.png! (*wrong!* since we pushed)
> 5. EXEC: Pick your server adapter and tell it to publish to OpenShift
> Result:
> The adapter tells you that you that there are local commits that you may push. (*wrong!*)
> !committed-changes-to-publish.png!
> Expected:
> We just pushed there cannot be local commits that were not pushed yet
> 6. EXEC: Confirm the dialog and tell it to publish
> Result:
> It tells you that OpenShift is already up-to-date (which is true!)
> !already-up-to-date.png!
> 7. EXEC: pick Team->Fetch from Upstream
> 8 ASSERT:
> The remote "is ahead of" state of the current branch compared to origin is updated. The EGit decorators in the Project Explorer get corrected (the ^1 gets removed). 
> !is-ahead-0.png!
> If you now publish via adapter it'll tell you that there are no local changes that you can push.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira