[jbosstools-issues] [JBoss JIRA] (JBIDE-22218) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
Fred Bricon (JIRA)
issues at jboss.org
Tue Apr 19 23:31:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Bricon updated JBIDE-22218:
--------------------------------
Description:
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/52703f5ff40595999fa08639714368259cbec97b version change
- https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79900c5303e82549dc1c97fc0d false positive over https://github.com/jbosstools/jbosstools-central/commit/8c73f3e46437b5f07aaa5714b835a28ed43fab01
- https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d568da68add42514195f19557 version change
- https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392fe3d2baf38ed509916723436 version change
- https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a81f6f11d53b420d1c2406419 version change
- https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483b1678300b3d215894b5f5440 version change
- https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f0107779fac10097a918ecd22903553 version change
- https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83cce84a9b08484e6540b0922c8 version change
- https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee499235e27f46d5dbee9fa12e version change
- https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f072d87f2bf82f70dcaebd24d5 version change
- https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe7285ff6cca75aeb6ca488969542 version change
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22maven%22%2C%22central%22%2C%22project-examples%22%29]
was:
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/52703f5ff40595999fa08639714368259cbec97b
- https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79900c5303e82549dc1c97fc0d
- https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d568da68add42514195f19557
- https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392fe3d2baf38ed509916723436
- https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a81f6f11d53b420d1c2406419
- https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483b1678300b3d215894b5f5440
- https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f0107779fac10097a918ecd22903553
- https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83cce84a9b08484e6540b0922c8
- https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee499235e27f46d5dbee9fa12e
- https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f072d87f2bf82f70dcaebd24d5
- https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe7285ff6cca75aeb6ca488969542
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22maven%22%2C%22central%22%2C%22project-examples%22%29]
> 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: central, maven, project-examples
> Reporter: Rob Stryker
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> 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/52703f5ff40595999fa08639714368259cbec97b version change
> - https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79900c5303e82549dc1c97fc0d false positive over https://github.com/jbosstools/jbosstools-central/commit/8c73f3e46437b5f07aaa5714b835a28ed43fab01
> - https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d568da68add42514195f19557 version change
> - https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392fe3d2baf38ed509916723436 version change
> - https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a81f6f11d53b420d1c2406419 version change
> - https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483b1678300b3d215894b5f5440 version change
> - https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f0107779fac10097a918ecd22903553 version change
> - https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83cce84a9b08484e6540b0922c8 version change
> - https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee499235e27f46d5dbee9fa12e version change
> - https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f072d87f2bf82f70dcaebd24d5 version change
> - https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe7285ff6cca75aeb6ca488969542 version change
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22maven%22%2C%22central%22%2C%22project-examples%22%29]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list