[jbosstools-issues] [JBoss JIRA] (JBIDE-22208) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base]

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-22208:
-------------------------------------


ad7ea588f8f0bc32db1631ed6ce92a807eb6a182 - cherry-pick is empty
c80d1a7bfc986f5d210cf4845101e4bad94d6ef1 - cherry-picked with merge errors
3fd35c68512402e60af5266f7e52dcef4a99dd64 - already present with different surrounding data
a05bc5c15b4c29ff4333eb38791b2692427bfeb7- present in master with much longer commit message
b4ab2ba6eace30e17c1aa7163c562b3dc35213ca - cherry-pick is empty, so must have been committed in pieces

> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base]
> ------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22208
>                 URL: https://issues.jboss.org/browse/JBIDE-22208
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: common/jst/core, usage
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Base]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. 
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. 
> If there are no commits listed below, please close (do not resolve) this issue. 
> Otherwise:
>    1) Click on each link below. 
>    2) Evaluate whether the given commit *should* be in master
>    3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. 
>    4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. 
>    5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
>    6) When all complete, please close (do not resolve) this issue.
>    
> Folder: jbosstools-base at https://github.com/jbosstools/jbosstools-base/
> Searching for commits present in jbosstools-4.3.x and missing from master
>  Commit hash  "3921b3" is the last common ancestor of jbosstools-4.3.x and master
>  3921b3 is 58 commits ago in branch master
>  3921b3 is 49 commits ago in branch jbosstools-4.3.x
>    Commits missing from master that are in jbosstools-4.3.x:
>      - https://github.com/jbosstools/jbosstools-base//commit/baca71426ed2a9671af10c130e51c92cb2514650
>      - https://github.com/jbosstools/jbosstools-base//commit/7de9cd6f3f900df915e7283f11a39c03dc8884ed
>      - https://github.com/jbosstools/jbosstools-base//commit/ad7ea588f8f0bc32db1631ed6ce92a807eb6a182
>      - https://github.com/jbosstools/jbosstools-base//commit/436fd3abea851f273a5b7a58b3fcf1185149d363
>      - https://github.com/jbosstools/jbosstools-base//commit/c80d1a7bfc986f5d210cf4845101e4bad94d6ef1
>      - https://github.com/jbosstools/jbosstools-base//commit/3fd35c68512402e60af5266f7e52dcef4a99dd64
>      - https://github.com/jbosstools/jbosstools-base//commit/a05bc5c15b4c29ff4333eb38791b2692427bfeb7
>      - https://github.com/jbosstools/jbosstools-base//commit/b4ab2ba6eace30e17c1aa7163c562b3dc35213ca
>      - https://github.com/jbosstools/jbosstools-base//commit/ccf853567c6a4c21d52418390788a73245e05de4
>      - https://github.com/jbosstools/jbosstools-base//commit/c8452d0c1ae1884777a3520764d5fb20a3c37735
>      - https://github.com/jbosstools/jbosstools-base//commit/f6a2717194354774fcb0db14b5fb1cd3c1c38111
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task], or [Search for Base task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22usage%22%2C%22common%2Fjst%2Fcore%22%29]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)