[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22209:
-----------------------------------
Summary: 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
Priority: Blocker
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-22210) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Playground]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22210:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Playground]
Key: JBIDE-22210
URL: https://issues.jboss.org/browse/JBIDE-22210
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: playground
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [Playground]: 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-playground at https://github.com/jbosstools/jbosstools-playground/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "476620" is the last common ancestor of jbosstools-4.3.x and master
476620 is 4 commits ago in branch master
476620 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-playground//commit/c97d38ca3d141...
- https://github.com/jbosstools/jbosstools-playground//commit/c6e3153a43e7c...
- https://github.com/jbosstools/jbosstools-playground//commit/15c2c008ae837...
- https://github.com/jbosstools/jbosstools-playground//commit/c82b4104d8df7...
- https://github.com/jbosstools/jbosstools-playground//commit/16de3723185fd...
- https://github.com/jbosstools/jbosstools-playground//commit/9758d0bfd73a8...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Playground 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-22207) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Hibernate]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22207:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Hibernate]
Key: JBIDE-22207
URL: https://issues.jboss.org/browse/JBIDE-22207
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [Hibernate]: 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-hibernate at https://github.com/jbosstools/jbosstools-hibernate/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "fe17a3" is the last common ancestor of jbosstools-4.3.x and master
fe17a3 is 226 commits ago in branch master
fe17a3 is 14 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-hibernate//commit/40d70e779b0f4e...
- https://github.com/jbosstools/jbosstools-hibernate//commit/470f7350047717...
- https://github.com/jbosstools/jbosstools-hibernate//commit/1aebe78228b378...
- https://github.com/jbosstools/jbosstools-hibernate//commit/e4ef139e682ab0...
- https://github.com/jbosstools/jbosstools-hibernate//commit/4433454f98bcd9...
- https://github.com/jbosstools/jbosstools-hibernate//commit/af17a74daccaf0...
- https://github.com/jbosstools/jbosstools-hibernate//commit/0cfa89c8a3686f...
- https://github.com/jbosstools/jbosstools-hibernate//commit/d30996173ae1a7...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Hibernate 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 Rob Stryker (JIRA)
Rob Stryker created JBIDE-22208:
-----------------------------------
Summary: 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: usage, common/jst/core
Reporter: Rob Stryker
Priority: Blocker
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-22204) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [VPE]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22204:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [VPE]
Key: JBIDE-22204
URL: https://issues.jboss.org/browse/JBIDE-22204
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [VPE]: 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-vpe at https://github.com/jbosstools/jbosstools-vpe/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "5fdde4" is the last common ancestor of jbosstools-4.3.x and master
5fdde4 is 10 commits ago in branch master
5fdde4 is 9 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-vpe//commit/a2b21f1b38c67f967e9a...
- https://github.com/jbosstools/jbosstools-vpe//commit/32507f22347e7a78b46c...
- https://github.com/jbosstools/jbosstools-vpe//commit/614fe8ef79e3e14383e9...
- https://github.com/jbosstools/jbosstools-vpe//commit/342bb8f7a473e668918d...
- https://github.com/jbosstools/jbosstools-vpe//commit/a9273884abd848332359...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for VPE 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 Rob Stryker (JIRA)
Rob Stryker created JBIDE-22205:
-----------------------------------
Summary: 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
Priority: Blocker
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-22206) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22206:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]
Key: JBIDE-22206
URL: https://issues.jboss.org/browse/JBIDE-22206
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [Server]: 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-server at https://github.com/jbosstools/jbosstools-server/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "ecbe98" is the last common ancestor of jbosstools-4.3.x and master
ecbe98 is 50 commits ago in branch master
ecbe98 is 52 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-server//commit/f8d95f7d1465dd60b...
- https://github.com/jbosstools/jbosstools-server//commit/122eb9e528632345c...
- https://github.com/jbosstools/jbosstools-server//commit/b1d95cd1ee50b92c1...
- https://github.com/jbosstools/jbosstools-server//commit/a9a35aee507b59453...
- https://github.com/jbosstools/jbosstools-server//commit/078a82d8f76cb02e3...
- https://github.com/jbosstools/jbosstools-server//commit/c1c87bd10ba0e9a2c...
- https://github.com/jbosstools/jbosstools-server//commit/784c82b35b3843f8e...
- https://github.com/jbosstools/jbosstools-server//commit/648b5425c80e6301d...
- https://github.com/jbosstools/jbosstools-server//commit/fdf66d3515c5f0782...
- https://github.com/jbosstools/jbosstools-server//commit/7d6b1b7e31194bf49...
- https://github.com/jbosstools/jbosstools-server//commit/bbf53cbb92c7cfc10...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server 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] (JBDS-3843) For JBDS 10.0.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master
by Rob Stryker (JIRA)
Rob Stryker created JBDS-3843:
---------------------------------
Summary: For JBDS 10.0.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master
Key: JBDS-3843
URL: https://issues.jboss.org/browse/JBDS-3843
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Rob Stryker
Priority: Blocker
Fix For: 10.0.0.Alpha1
For JBDS 10.0.0.Alpha1: 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.
[Search for all 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-22202) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22202:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master
Key: JBIDE-22202
URL: https://issues.jboss.org/browse/JBIDE-22202
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Rob Stryker
Priority: Blocker
Fix For: 4.4.0.Alpha1
For JBIDE 4.4.0.Alpha1: 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.
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
See also: JBDS-3843
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22203) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Aerogear]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22203:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Aerogear]
Key: JBIDE-22203
URL: https://issues.jboss.org/browse/JBIDE-22203
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid, cordovasim
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [Aerogear]: 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-aerogear at https://github.com/jbosstools/jbosstools-aerogear/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "fbcaf6" is the last common ancestor of jbosstools-4.3.x and master
fbcaf6 is 10 commits ago in branch master
fbcaf6 is 20 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-aerogear//commit/938198c0668e1f5...
- https://github.com/jbosstools/jbosstools-aerogear//commit/c5207dc9e034c51...
- https://github.com/jbosstools/jbosstools-aerogear//commit/b2f26d53504a256...
- https://github.com/jbosstools/jbosstools-aerogear//commit/fd189752b6f5209...
- https://github.com/jbosstools/jbosstools-aerogear//commit/002faaa2701ce0a...
- https://github.com/jbosstools/jbosstools-aerogear//commit/d1776c97ba01bbf...
- https://github.com/jbosstools/jbosstools-aerogear//commit/ec4a1312844e068...
- https://github.com/jbosstools/jbosstools-aerogear//commit/a7686517ded4ef9...
- https://github.com/jbosstools/jbosstools-aerogear//commit/58fbd4aa7342c66...
- https://github.com/jbosstools/jbosstools-aerogear//commit/7c3d92f4e47f85b...
- https://github.com/jbosstools/jbosstools-aerogear//commit/af2dba422b0617a...
- https://github.com/jbosstools/jbosstools-aerogear//commit/b03070aaf0ea89f...
- https://github.com/jbosstools/jbosstools-aerogear//commit/a37e1d0f565e234...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Aerogear 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