[JBoss JIRA] (JBIDE-22215) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Webservices]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22215?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22215:
--------------------------------------
Assignee: Xavier Coulon
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Webservices]
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-22215
> URL: https://issues.jboss.org/browse/JBIDE-22215
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Rob Stryker
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Webservices]: 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-webservices at https://github.com/jbosstools/jbosstools-webservices/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "6aa98d" is the last common ancestor of jbosstools-4.3.x and master
> 6aa98d is 6 commits ago in branch master
> 6aa98d is 8 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-webservices//commit/22de6f979a60...
> - https://github.com/jbosstools/jbosstools-webservices//commit/0e9928f3f5ca...
> - https://github.com/jbosstools/jbosstools-webservices//commit/6a071b8e9bb6...
> - https://github.com/jbosstools/jbosstools-webservices//commit/ff6841f2dac9...
> - https://github.com/jbosstools/jbosstools-webservices//commit/ce92ff639574...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Webservices task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22209?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22209:
--------------------------------------
Assignee: Fred Bricon
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22209
> URL: https://issues.jboss.org/browse/JBIDE-22209
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Rob Stryker
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [OpenShift]: 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-openshift at https://github.com/jbosstools/jbosstools-openshift/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "8e29d0" is the last common ancestor of jbosstools-4.3.x and master
> 8e29d0 is 409 commits ago in branch master
> 8e29d0 is 394 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-openshift//commit/9f74be7e9e62b7...
> - https://github.com/jbosstools/jbosstools-openshift//commit/e0f8e68a563905...
> - https://github.com/jbosstools/jbosstools-openshift//commit/009dcba545a46a...
> - https://github.com/jbosstools/jbosstools-openshift//commit/fcdfc9a8da1d94...
> - https://github.com/jbosstools/jbosstools-openshift//commit/087f63953adebe...
> - https://github.com/jbosstools/jbosstools-openshift//commit/55c161d3adf09e...
> - https://github.com/jbosstools/jbosstools-openshift//commit/2b7e853f34533c...
> - https://github.com/jbosstools/jbosstools-openshift//commit/2aa9125ab7f7e9...
> - https://github.com/jbosstools/jbosstools-openshift//commit/36cb020dbdb0f6...
> - https://github.com/jbosstools/jbosstools-openshift//commit/7a2589b5e1f43f...
> - https://github.com/jbosstools/jbosstools-openshift//commit/e77a887a382e2c...
> - https://github.com/jbosstools/jbosstools-openshift//commit/eb65cd687d0002...
> - https://github.com/jbosstools/jbosstools-openshift//commit/39492ed2137579...
> - https://github.com/jbosstools/jbosstools-openshift//commit/6873d3b22fc734...
> - https://github.com/jbosstools/jbosstools-openshift//commit/5c09968cfb3e07...
> - https://github.com/jbosstools/jbosstools-openshift//commit/4f729326a186d0...
> - https://github.com/jbosstools/jbosstools-openshift//commit/760a1f971fc17d...
> - https://github.com/jbosstools/jbosstools-openshift//commit/7dffff362b99f4...
> - https://github.com/jbosstools/jbosstools-openshift//commit/e7dde4151339ab...
> - https://github.com/jbosstools/jbosstools-openshift//commit/1605d63e6d7e51...
> - https://github.com/jbosstools/jbosstools-openshift//commit/26a1d1e7d91801...
> - https://github.com/jbosstools/jbosstools-openshift//commit/5968aa42fac7ed...
> - https://github.com/jbosstools/jbosstools-openshift//commit/95dac28be51c0e...
> - https://github.com/jbosstools/jbosstools-openshift//commit/e4ecf6ff5ea331...
> - https://github.com/jbosstools/jbosstools-openshift//commit/6c0cb8049b291e...
> - https://github.com/jbosstools/jbosstools-openshift//commit/d6a2d2effd2a73...
> - https://github.com/jbosstools/jbosstools-openshift//commit/8620c1caeeed74...
> - https://github.com/jbosstools/jbosstools-openshift//commit/9b6e8d60ff1bf6...
> - https://github.com/jbosstools/jbosstools-openshift//commit/f539d2ef0bee63...
> - https://github.com/jbosstools/jbosstools-openshift//commit/2e3c64ced3c923...
> - https://github.com/jbosstools/jbosstools-openshift//commit/201a855cc5cac7...
> - https://github.com/jbosstools/jbosstools-openshift//commit/14b05efeef623a...
> - https://github.com/jbosstools/jbosstools-openshift//commit/8c5a7ead1fa835...
> - https://github.com/jbosstools/jbosstools-openshift//commit/213f368d88d215...
> - https://github.com/jbosstools/jbosstools-openshift//commit/61a9b842a5c34a...
> - https://github.com/jbosstools/jbosstools-openshift//commit/4206c33ba53c6f...
> - https://github.com/jbosstools/jbosstools-openshift//commit/bd9c728c6c3a75...
> - https://github.com/jbosstools/jbosstools-openshift//commit/f51830888169e7...
> - https://github.com/jbosstools/jbosstools-openshift//commit/951590f4f5cf8d...
> - https://github.com/jbosstools/jbosstools-openshift//commit/17da52cb6d9651...
> - https://github.com/jbosstools/jbosstools-openshift//commit/2578624c74b744...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for OpenShift task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22213) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Forge]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22213?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22213:
--------------------------------------
Assignee: George Gastaldi
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Forge]
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-22213
> URL: https://issues.jboss.org/browse/JBIDE-22213
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Rob Stryker
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Forge]: 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-forge at https://github.com/jbosstools/jbosstools-forge/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "0b5f88" is the last common ancestor of jbosstools-4.3.x and master
> 0b5f88 is 23 commits ago in branch master
> 0b5f88 is 24 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-forge//commit/ee1e4d2b7ddc8545cb...
> - https://github.com/jbosstools/jbosstools-forge//commit/e699c29351401a15a1...
> - https://github.com/jbosstools/jbosstools-forge//commit/89e1a098136c5c6f24...
> - https://github.com/jbosstools/jbosstools-forge//commit/6ef52ee18de7740fe5...
> - https://github.com/jbosstools/jbosstools-forge//commit/11f1a8cd60495c3dee...
> - https://github.com/jbosstools/jbosstools-forge//commit/1f03e7f5edff62053b...
> - https://github.com/jbosstools/jbosstools-forge//commit/29c215d98fe0450bbe...
> - https://github.com/jbosstools/jbosstools-forge//commit/6652db2d6d1e398764...
> - https://github.com/jbosstools/jbosstools-forge//commit/bbae2fdf4b9d051753...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Forge task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22208) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22208?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22208:
----------------------------------------
Suspicious commits (all belongs to [~rob.stryker]):
https://github.com/jbosstools/jbosstools-base//commit/ad7ea588f8f0bc32db1...
https://github.com/jbosstools/jbosstools-base//commit/c80d1a7bfc986f5d210...
https://github.com/jbosstools/jbosstools-base//commit/3fd35c68512402e60af...
https://github.com/jbosstools/jbosstools-base//commit/a05bc5c15b4c29ff433...
https://github.com/jbosstools/jbosstools-base//commit/b4ab2ba6eace30e17c1...
> 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/baca71426ed2a9671af...
> - https://github.com/jbosstools/jbosstools-base//commit/7de9cd6f3f900df915e...
> - https://github.com/jbosstools/jbosstools-base//commit/ad7ea588f8f0bc32db1...
> - https://github.com/jbosstools/jbosstools-base//commit/436fd3abea851f273a5...
> - https://github.com/jbosstools/jbosstools-base//commit/c80d1a7bfc986f5d210...
> - https://github.com/jbosstools/jbosstools-base//commit/3fd35c68512402e60af...
> - https://github.com/jbosstools/jbosstools-base//commit/a05bc5c15b4c29ff433...
> - https://github.com/jbosstools/jbosstools-base//commit/b4ab2ba6eace30e17c1...
> - https://github.com/jbosstools/jbosstools-base//commit/ccf853567c6a4c21d52...
> - https://github.com/jbosstools/jbosstools-base//commit/c8452d0c1ae1884777a...
> - https://github.com/jbosstools/jbosstools-base//commit/f6a2717194354774fcb...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Base task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22205) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Discovery]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22205?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22205:
--------------------------------------
Assignee: Nick Boldt
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Discovery]
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22205
> URL: https://issues.jboss.org/browse/JBIDE-22205
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Discovery]: 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-discovery at https://github.com/jbosstools/jbosstools-discovery/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "9ad468" is the last common ancestor of jbosstools-4.3.x and master
> 9ad468 is 22 commits ago in branch master
> 9ad468 is 26 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-discovery//commit/0287cfbb7ba3bd...
> - https://github.com/jbosstools/jbosstools-discovery//commit/5e6fe574836e26...
> - https://github.com/jbosstools/jbosstools-discovery//commit/54c7d078d4457d...
> - https://github.com/jbosstools/jbosstools-discovery//commit/5583661a5d4324...
> - https://github.com/jbosstools/jbosstools-discovery//commit/2465d0c3e5d411...
> - https://github.com/jbosstools/jbosstools-discovery//commit/3b46e9d67efb62...
> - https://github.com/jbosstools/jbosstools-discovery//commit/2f3afda514dcfb...
> - https://github.com/jbosstools/jbosstools-discovery//commit/c5ee5345fc4583...
> - https://github.com/jbosstools/jbosstools-discovery//commit/ad8de6ee6b9af8...
> - https://github.com/jbosstools/jbosstools-discovery//commit/12568a875d10f0...
> - https://github.com/jbosstools/jbosstools-discovery//commit/56751d5fcc1816...
> - https://github.com/jbosstools/jbosstools-discovery//commit/5dd62f01020764...
> - https://github.com/jbosstools/jbosstools-discovery//commit/5c72ceaf88efb8...
> - https://github.com/jbosstools/jbosstools-discovery//commit/61f5c5a7bb1ec9...
> - https://github.com/jbosstools/jbosstools-discovery//commit/39b63626333010...
> - https://github.com/jbosstools/jbosstools-discovery//commit/90668d7f93d840...
> - https://github.com/jbosstools/jbosstools-discovery//commit/df214c5bb0c9fa...
> - https://github.com/jbosstools/jbosstools-discovery//commit/ed4031bed09e4e...
> - https://github.com/jbosstools/jbosstools-discovery//commit/aa7a93a5b354bc...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Discovery task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22212) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22212?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22212:
----------------------------------------
Suspicious commits:
https://github.com/jbosstools/jbosstools-jst//commit/a8fbc1875782258c207b...
https://github.com/jbosstools/jbosstools-jst//commit/3d30634f05154f895ae9...
https://github.com/jbosstools/jbosstools-jst//commit/e9f70fb64d801715c607...
https://github.com/jbosstools/jbosstools-jst//commit/50d6b9f93516ef3aaa8f...
https://github.com/jbosstools/jbosstools-jst//commit/5ece87d8e385e99b76af...
https://github.com/jbosstools/jbosstools-jst//commit/333c9a71aca9b449b5ba...
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JST]
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22212
> URL: https://issues.jboss.org/browse/JBIDE-22212
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [JST]: 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-jst at https://github.com/jbosstools/jbosstools-jst/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "850b5b" is the last common ancestor of jbosstools-4.3.x and master
> 850b5b is 35 commits ago in branch master
> 850b5b is 24 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-jst//commit/571f69e92999ec7efb39...
> - https://github.com/jbosstools/jbosstools-jst//commit/60e28ed0b405ceca2923...
> - https://github.com/jbosstools/jbosstools-jst//commit/090e37f543ea9f3268b7...
> - https://github.com/jbosstools/jbosstools-jst//commit/80b09a2bae9520fbe4a7...
> - https://github.com/jbosstools/jbosstools-jst//commit/a8fbc1875782258c207b...
> - https://github.com/jbosstools/jbosstools-jst//commit/cb4c2a43064b65bf92bc...
> - https://github.com/jbosstools/jbosstools-jst//commit/1e6b426c8c203e6b789a...
> - https://github.com/jbosstools/jbosstools-jst//commit/3d30634f05154f895ae9...
> - https://github.com/jbosstools/jbosstools-jst//commit/e9f70fb64d801715c607...
> - https://github.com/jbosstools/jbosstools-jst//commit/40e71e7e78b3bf6ec0c7...
> - https://github.com/jbosstools/jbosstools-jst//commit/50d6b9f93516ef3aaa8f...
> - https://github.com/jbosstools/jbosstools-jst//commit/795628f2cd9bc72065bc...
> - https://github.com/jbosstools/jbosstools-jst//commit/5ece87d8e385e99b76af...
> - https://github.com/jbosstools/jbosstools-jst//commit/333c9a71aca9b449b5ba...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JST task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22212) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22212?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22212:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JST]
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22212
> URL: https://issues.jboss.org/browse/JBIDE-22212
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Rob Stryker
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [JST]: 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-jst at https://github.com/jbosstools/jbosstools-jst/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "850b5b" is the last common ancestor of jbosstools-4.3.x and master
> 850b5b is 35 commits ago in branch master
> 850b5b is 24 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-jst//commit/571f69e92999ec7efb39...
> - https://github.com/jbosstools/jbosstools-jst//commit/60e28ed0b405ceca2923...
> - https://github.com/jbosstools/jbosstools-jst//commit/090e37f543ea9f3268b7...
> - https://github.com/jbosstools/jbosstools-jst//commit/80b09a2bae9520fbe4a7...
> - https://github.com/jbosstools/jbosstools-jst//commit/a8fbc1875782258c207b...
> - https://github.com/jbosstools/jbosstools-jst//commit/cb4c2a43064b65bf92bc...
> - https://github.com/jbosstools/jbosstools-jst//commit/1e6b426c8c203e6b789a...
> - https://github.com/jbosstools/jbosstools-jst//commit/3d30634f05154f895ae9...
> - https://github.com/jbosstools/jbosstools-jst//commit/e9f70fb64d801715c607...
> - https://github.com/jbosstools/jbosstools-jst//commit/40e71e7e78b3bf6ec0c7...
> - https://github.com/jbosstools/jbosstools-jst//commit/50d6b9f93516ef3aaa8f...
> - https://github.com/jbosstools/jbosstools-jst//commit/795628f2cd9bc72065bc...
> - https://github.com/jbosstools/jbosstools-jst//commit/5ece87d8e385e99b76af...
> - https://github.com/jbosstools/jbosstools-jst//commit/333c9a71aca9b449b5ba...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JST task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22211) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22211?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22211:
----------------------------------------
I see one missing commit - https://github.com/jbosstools/jbosstools-javaee//commit/4065cbff5708de0f7...
The rest is expected.
[~scabanovich] could you please take a look?
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-22211
> URL: https://issues.jboss.org/browse/JBIDE-22211
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [JavaEE]: 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-javaee at https://github.com/jbosstools/jbosstools-javaee/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "e96264" is the last common ancestor of jbosstools-4.3.x and master
> e96264 is 23 commits ago in branch master
> e96264 is 19 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-javaee//commit/2d520a947a6ecd802...
> - https://github.com/jbosstools/jbosstools-javaee//commit/ab8ac4c4f0e8f477d...
> - https://github.com/jbosstools/jbosstools-javaee//commit/f21505be773e27a92...
> - https://github.com/jbosstools/jbosstools-javaee//commit/4065cbff5708de0f7...
> - https://github.com/jbosstools/jbosstools-javaee//commit/e1e0ef7c4bfdd6eda...
> - https://github.com/jbosstools/jbosstools-javaee//commit/529f2e4ae943cf425...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JavaEE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22211) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22211?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22211:
--------------------------------------
Assignee: Viacheslav Kabanovich
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-22211
> URL: https://issues.jboss.org/browse/JBIDE-22211
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Rob Stryker
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [JavaEE]: 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-javaee at https://github.com/jbosstools/jbosstools-javaee/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "e96264" is the last common ancestor of jbosstools-4.3.x and master
> e96264 is 23 commits ago in branch master
> e96264 is 19 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-javaee//commit/2d520a947a6ecd802...
> - https://github.com/jbosstools/jbosstools-javaee//commit/ab8ac4c4f0e8f477d...
> - https://github.com/jbosstools/jbosstools-javaee//commit/f21505be773e27a92...
> - https://github.com/jbosstools/jbosstools-javaee//commit/4065cbff5708de0f7...
> - https://github.com/jbosstools/jbosstools-javaee//commit/e1e0ef7c4bfdd6eda...
> - https://github.com/jbosstools/jbosstools-javaee//commit/529f2e4ae943cf425...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JavaEE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22208) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22208?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22208:
--------------------------------------
Assignee: Rob Stryker
> 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/baca71426ed2a9671af...
> - https://github.com/jbosstools/jbosstools-base//commit/7de9cd6f3f900df915e...
> - https://github.com/jbosstools/jbosstools-base//commit/ad7ea588f8f0bc32db1...
> - https://github.com/jbosstools/jbosstools-base//commit/436fd3abea851f273a5...
> - https://github.com/jbosstools/jbosstools-base//commit/c80d1a7bfc986f5d210...
> - https://github.com/jbosstools/jbosstools-base//commit/3fd35c68512402e60af...
> - https://github.com/jbosstools/jbosstools-base//commit/a05bc5c15b4c29ff433...
> - https://github.com/jbosstools/jbosstools-base//commit/b4ab2ba6eace30e17c1...
> - https://github.com/jbosstools/jbosstools-base//commit/ccf853567c6a4c21d52...
> - https://github.com/jbosstools/jbosstools-base//commit/c8452d0c1ae1884777a...
> - https://github.com/jbosstools/jbosstools-base//commit/f6a2717194354774fcb...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Base task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months