[JBoss JIRA] (JBIDE-22220) Show in Eclipse status line an item selected in OpenShift explorer
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-22220:
---------------------------------------------
Summary: Show in Eclipse status line an item selected in OpenShift explorer
Key: JBIDE-22220
URL: https://issues.jboss.org/browse/JBIDE-22220
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.4.0.Alpha1
Text labels of nodes in OpenShift explorer may be long so that text is shortened with ellipses. Eclipse status line provides more space and it adjusts shortened text to the available width.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22214) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [BrowserSim]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22214:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [BrowserSim]
Key: JBIDE-22214
URL: https://issues.jboss.org/browse/JBIDE-22214
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: browsersim
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [BrowserSim]: 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-browsersim at https://github.com/jbosstools/jbosstools-browsersim/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "ee7642" is the last common ancestor of jbosstools-4.3.x and master
ee7642 is 17 commits ago in branch master
ee7642 is 15 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-browsersim//commit/21d705cda91a5...
- https://github.com/jbosstools/jbosstools-browsersim//commit/2adc8601840fa...
- https://github.com/jbosstools/jbosstools-browsersim//commit/e3286f743f5a7...
- https://github.com/jbosstools/jbosstools-browsersim//commit/381ad6f797173...
- https://github.com/jbosstools/jbosstools-browsersim//commit/0ba88810356c7...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for BrowserSim 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-22215) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Webservices]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22215:
-----------------------------------
Summary: 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
Priority: Blocker
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-22216) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Arquillian]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22216:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Arquillian]
Key: JBIDE-22216
URL: https://issues.jboss.org/browse/JBIDE-22216
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: arquillian
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [Arquillian]: 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-arquillian at https://github.com/jbosstools/jbosstools-arquillian/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "412c29" is the last common ancestor of jbosstools-4.3.x and master
412c29 is 6 commits ago in branch master
412c29 is 7 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-arquillian//commit/bb785170f5a17...
- https://github.com/jbosstools/jbosstools-arquillian//commit/245349ec53aae...
- https://github.com/jbosstools/jbosstools-arquillian//commit/7190f7b377c51...
- https://github.com/jbosstools/jbosstools-arquillian//commit/0f691ab5997a8...
- https://github.com/jbosstools/jbosstools-arquillian//commit/5095d5b7dcf45...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Arquillian 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-22217) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Freemarker]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22217:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Freemarker]
Key: JBIDE-22217
URL: https://issues.jboss.org/browse/JBIDE-22217
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: freemarker
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [Freemarker]: 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-freemarker at https://github.com/jbosstools/jbosstools-freemarker/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "171cac" is the last common ancestor of jbosstools-4.3.x and master
171cac is 5 commits ago in branch master
171cac 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-freemarker//commit/a68fdbc4e1e29...
- https://github.com/jbosstools/jbosstools-freemarker//commit/75774bb9bb6ab...
- https://github.com/jbosstools/jbosstools-freemarker//commit/4d2c09250a53a...
- https://github.com/jbosstools/jbosstools-freemarker//commit/a0dcd63051033...
- https://github.com/jbosstools/jbosstools-freemarker//commit/d33f8812a72b9...
- https://github.com/jbosstools/jbosstools-freemarker//commit/b4c28ff7b02ec...
- https://github.com/jbosstools/jbosstools-freemarker//commit/283825f4e673a...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Freemarker 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-22218) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22218:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
Key: JBIDE-22218
URL: https://issues.jboss.org/browse/JBIDE-22218
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: maven, project-examples, central
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [Central]: 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-central at https://github.com/jbosstools/jbosstools-central/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "5e1220" is the last common ancestor of jbosstools-4.3.x and master
5e1220 is 41 commits ago in branch master
5e1220 is 35 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-central//commit/52703f5ff4059599...
- https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79...
- https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d...
- https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392...
- https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a...
- https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483...
- https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f010777...
- https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83c...
- https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee...
- https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f0...
- https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe728...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Central 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-22219) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [LiveReload]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22219:
-----------------------------------
Summary: For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [LiveReload]
Key: JBIDE-22219
URL: https://issues.jboss.org/browse/JBIDE-22219
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Reporter: Rob Stryker
Priority: Blocker
For JBIDE 4.4.0.Alpha1 [LiveReload]: 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-livereload at https://github.com/jbosstools/jbosstools-livereload/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "b49e9d" is the last common ancestor of jbosstools-4.3.x and master
b49e9d is 16 commits ago in branch master
b49e9d is 15 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-livereload//commit/bf3ca4c56fe7a...
- https://github.com/jbosstools/jbosstools-livereload//commit/eeaa6e4f032ce...
- https://github.com/jbosstools/jbosstools-livereload//commit/c3748dc829f05...
- https://github.com/jbosstools/jbosstools-livereload//commit/5db3bdee91271...
- https://github.com/jbosstools/jbosstools-livereload//commit/a1dd89ea861e9...
- https://github.com/jbosstools/jbosstools-livereload//commit/bc88160f5bf7d...
- https://github.com/jbosstools/jbosstools-livereload//commit/43ff18a8b49d0...
- https://github.com/jbosstools/jbosstools-livereload//commit/cda733cfa345b...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for LiveReload 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 Rob Stryker (JIRA)
Rob Stryker created JBIDE-22211:
-----------------------------------
Summary: 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: seam2, cdi, cdi-extensions, jsf
Reporter: Rob Stryker
Priority: Blocker
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-22212) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JST]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22212:
-----------------------------------
Summary: 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
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-22213) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Forge]
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-22213:
-----------------------------------
Summary: 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
Priority: Blocker
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