[JBoss JIRA] (JBIDE-24397) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [build-sites]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24397:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [build-sites]
Key: JBIDE-24397
URL: https://issues.jboss.org/browse/JBIDE-24397
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Jeff MAURY
Priority: Blocker
For JBIDE 4.4.4.Final [build-sites]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
6) When all complete, please close (do not resolve) this issue.
Folder: jbosstools-build-sites at https://github.com/jbosstools/jbosstools-build-sites
Searching for commits present in master and missing from jbosstools-4.4.x
Commit hash "8a0ffd" is the last common ancestor of master and jbosstools-4.4.x
8a0ffd is 7 commits ago in branch jbosstools-4.4.x
8a0ffd is 6 commits ago in branch master
Commits missing from jbosstools-4.4.x that are in master:
* missing: JBIDE-24240-EBZ-511793-add-org.eclipse.wst.common.modulecore-patch-feature-to-JBT-Abridged-category-CoreTools-and-WebTools-too https://github.com/jbosstools/jbosstools-build-sites/commit/a1fd4ed0f5a95...
** possible match: https://github.com/jbosstools/jbosstools-build-sites/commit/fefbbbf29ca0c...
*** Inspect the difference between the two patches: http://sprunge.us/iaPA
* missing: bump-master-to-4.5.0 https://github.com/jbosstools/jbosstools-build-sites/commit/d1fd2abdaf3e0...
* missing: JBIDE-23960-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-build-sites/commit/d859d58008d12...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for build-sites task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24394) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Central]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24394?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24394:
----------------------------------
Assignee: Fred Bricon
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Central]
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-24394
> URL: https://issues.jboss.org/browse/JBIDE-24394
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Jeff MAURY
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
>
> For JBIDE 4.4.4.Final [Central]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 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 master and missing from jbosstools-4.4.x
> Commit hash "27a46b" is the last common ancestor of master and jbosstools-4.4.x
> 27a46b is 6 commits ago in branch jbosstools-4.4.x
> 27a46b is 8 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: bump-maven-examples-and-central-from-x.y.3-to-x.y.100-to-fix-build-breakages-in-master-branch-seriously-is-no-one-test-building-locally-w.t.f https://github.com/jbosstools/jbosstools-central/commit/d5ce47d7e02ded9d5...
> * missing: features-too-because-4.4.x-branch-has-2.1.4-and-1.8.4-bump-master-to-2.1.100-and-1.8.100 https://github.com/jbosstools/jbosstools-central/commit/1b6f259eee3d6733b...
> * missing: because-4.4.x-branch-has-2.1.4-and-1.8.4-bump-master-to-2.1.100-and-1.8.100 https://github.com/jbosstools/jbosstools-central/commit/df726ac172345423b...
> * missing: JBIDE-24133-org.jboss.tools.runtime.reddeer.-396 https://github.com/jbosstools/jbosstools-central/commit/6a40e1fa413dbc8a6...
> * missing: JBIDE-23948-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-central/commit/1e09f6561099ec443...
> [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
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24393) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [versionwatch]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24393:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [versionwatch]
Key: JBIDE-24393
URL: https://issues.jboss.org/browse/JBIDE-24393
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: versionwatch
Reporter: Jeff MAURY
Priority: Blocker
For JBIDE 4.4.4.Final [versionwatch]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
6) When all complete, please close (do not resolve) this issue.
Folder: jbosstools-versionwatch at https://github.com/jbosstools/jbosstools-versionwatch
Searching for commits present in master and missing from jbosstools-4.4.x
Commit hash "832992" is the last common ancestor of master and jbosstools-4.4.x
832992 is 17 commits ago in branch jbosstools-4.4.x
832992 is 19 commits ago in branch master
Commits missing from jbosstools-4.4.x that are in master:
* missing: Add-support-for-report-files-based-on-IU-filter-and-optional-suffix https://github.com/jbosstools/jbosstools-versionwatch/commit/2cc0c226bdc5...
** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/1a37467f940d...
*** Inspect the difference between the two patches: http://sprunge.us/bEJX
* missing: move-report_-.html-files-into-target-folder-where-they-belong https://github.com/jbosstools/jbosstools-versionwatch/commit/7adb5fbf4000...
** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/f4c06a2a9803...
*** Inspect the difference between the two patches: http://sprunge.us/NVda
** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/1db868970e1f...
*** Inspect the difference between the two patches: http://sprunge.us/OcQM
* missing: bump-to-0.5.0-in-master https://github.com/jbosstools/jbosstools-versionwatch/commit/6f9564edab00...
* missing: bump-up-to-maven-3.3.9-and-add-check-for-M2_HOME https://github.com/jbosstools/jbosstools-versionwatch/commit/8662ee0ad83a...
* missing: remove-spaces https://github.com/jbosstools/jbosstools-versionwatch/commit/ef31001ee83f...
* missing: update-versionwatch-run.jenkins.job.sh-to-run-on-CCI-Jenkins-JBDS-4286 https://github.com/jbosstools/jbosstools-versionwatch/commit/18ab37874bce...
** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/4b8b6138d1fe...
*** Inspect the difference between the two patches: http://sprunge.us/XVQC
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for versionwatch task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24394) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Central]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24394:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Central]
Key: JBIDE-24394
URL: https://issues.jboss.org/browse/JBIDE-24394
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: maven, project-examples, central
Reporter: Jeff MAURY
Priority: Blocker
For JBIDE 4.4.4.Final [Central]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
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 master and missing from jbosstools-4.4.x
Commit hash "27a46b" is the last common ancestor of master and jbosstools-4.4.x
27a46b is 6 commits ago in branch jbosstools-4.4.x
27a46b is 8 commits ago in branch master
Commits missing from jbosstools-4.4.x that are in master:
* missing: bump-maven-examples-and-central-from-x.y.3-to-x.y.100-to-fix-build-breakages-in-master-branch-seriously-is-no-one-test-building-locally-w.t.f https://github.com/jbosstools/jbosstools-central/commit/d5ce47d7e02ded9d5...
* missing: features-too-because-4.4.x-branch-has-2.1.4-and-1.8.4-bump-master-to-2.1.100-and-1.8.100 https://github.com/jbosstools/jbosstools-central/commit/1b6f259eee3d6733b...
* missing: because-4.4.x-branch-has-2.1.4-and-1.8.4-bump-master-to-2.1.100-and-1.8.100 https://github.com/jbosstools/jbosstools-central/commit/df726ac172345423b...
* missing: JBIDE-24133-org.jboss.tools.runtime.reddeer.-396 https://github.com/jbosstools/jbosstools-central/commit/6a40e1fa413dbc8a6...
* missing: JBIDE-23948-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-central/commit/1e09f6561099ec443...
[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
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24393) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [versionwatch]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24393?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24393:
----------------------------------
Assignee: Nick Boldt
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [versionwatch]
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-24393
> URL: https://issues.jboss.org/browse/JBIDE-24393
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: versionwatch
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
>
> For JBIDE 4.4.4.Final [versionwatch]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-versionwatch at https://github.com/jbosstools/jbosstools-versionwatch
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "832992" is the last common ancestor of master and jbosstools-4.4.x
> 832992 is 17 commits ago in branch jbosstools-4.4.x
> 832992 is 19 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: Add-support-for-report-files-based-on-IU-filter-and-optional-suffix https://github.com/jbosstools/jbosstools-versionwatch/commit/2cc0c226bdc5...
> ** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/1a37467f940d...
> *** Inspect the difference between the two patches: http://sprunge.us/bEJX
> * missing: move-report_-.html-files-into-target-folder-where-they-belong https://github.com/jbosstools/jbosstools-versionwatch/commit/7adb5fbf4000...
> ** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/f4c06a2a9803...
> *** Inspect the difference between the two patches: http://sprunge.us/NVda
> ** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/1db868970e1f...
> *** Inspect the difference between the two patches: http://sprunge.us/OcQM
> * missing: bump-to-0.5.0-in-master https://github.com/jbosstools/jbosstools-versionwatch/commit/6f9564edab00...
> * missing: bump-up-to-maven-3.3.9-and-add-check-for-M2_HOME https://github.com/jbosstools/jbosstools-versionwatch/commit/8662ee0ad83a...
> * missing: remove-spaces https://github.com/jbosstools/jbosstools-versionwatch/commit/ef31001ee83f...
> * missing: update-versionwatch-run.jenkins.job.sh-to-run-on-CCI-Jenkins-JBDS-4286 https://github.com/jbosstools/jbosstools-versionwatch/commit/18ab37874bce...
> ** possible match: https://github.com/jbosstools/jbosstools-versionwatch/commit/4b8b6138d1fe...
> *** Inspect the difference between the two patches: http://sprunge.us/XVQC
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for versionwatch task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24392) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Aerogear]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24392?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24392:
----------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Aerogear]
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-24392
> URL: https://issues.jboss.org/browse/JBIDE-24392
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
>
> For JBIDE 4.4.4.Final [Aerogear]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 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 master and missing from jbosstools-4.4.x
> Commit hash "4661c6" is the last common ancestor of master and jbosstools-4.4.x
> 4661c6 is 6 commits ago in branch jbosstools-4.4.x
> 4661c6 is 8 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: Revert-JBIDE-24341-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-aerogear/commit/eef2e4ae44a04d11...
> * missing: JBIDE-24341-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-aerogear/commit/b854b2e8d7fec03a...
> * missing: because-1.4.4-is-in-4.4.x-branch-must-be-1.4.100-in-master https://github.com/jbosstools/jbosstools-aerogear/commit/9243fb2668400215...
> * missing: JBIDE-24126-use-latest-thym-2.1.0.201703221647-in-master-branch https://github.com/jbosstools/jbosstools-aerogear/commit/f77fd94c5fe8cf16...
> * missing: JBIDE-23944-Prepare-for-4.5.0.AM1-11.0.0.AM1-aerogear-hybrid https://github.com/jbosstools/jbosstools-aerogear/commit/287aa09fbcd7ee12...
> * missing: JBIDE-24001-Browsersim-and-Cordovasim-are-broken-since-jetty-v-9.4.0-was-added-to-TP https://github.com/jbosstools/jbosstools-aerogear/commit/2cafddea6db60f4b...
> * missing: JBIDE-23944-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-aerogear/commit/03b5f9bd3bbc7b71...
> [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
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24392) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Aerogear]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24392:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Aerogear]
Key: JBIDE-24392
URL: https://issues.jboss.org/browse/JBIDE-24392
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid, cordovasim
Reporter: Jeff MAURY
Priority: Blocker
For JBIDE 4.4.4.Final [Aerogear]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
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 master and missing from jbosstools-4.4.x
Commit hash "4661c6" is the last common ancestor of master and jbosstools-4.4.x
4661c6 is 6 commits ago in branch jbosstools-4.4.x
4661c6 is 8 commits ago in branch master
Commits missing from jbosstools-4.4.x that are in master:
* missing: Revert-JBIDE-24341-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-aerogear/commit/eef2e4ae44a04d11...
* missing: JBIDE-24341-comment-bump-up-to-parent-pom-version-4.4.4.Final-SNAPSHOT-close https://github.com/jbosstools/jbosstools-aerogear/commit/b854b2e8d7fec03a...
* missing: because-1.4.4-is-in-4.4.x-branch-must-be-1.4.100-in-master https://github.com/jbosstools/jbosstools-aerogear/commit/9243fb2668400215...
* missing: JBIDE-24126-use-latest-thym-2.1.0.201703221647-in-master-branch https://github.com/jbosstools/jbosstools-aerogear/commit/f77fd94c5fe8cf16...
* missing: JBIDE-23944-Prepare-for-4.5.0.AM1-11.0.0.AM1-aerogear-hybrid https://github.com/jbosstools/jbosstools-aerogear/commit/287aa09fbcd7ee12...
* missing: JBIDE-24001-Browsersim-and-Cordovasim-are-broken-since-jetty-v-9.4.0-was-added-to-TP https://github.com/jbosstools/jbosstools-aerogear/commit/2cafddea6db60f4b...
* missing: JBIDE-23944-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-aerogear/commit/03b5f9bd3bbc7b71...
[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
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24391) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24391:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x
Key: JBIDE-24391
URL: https://issues.jboss.org/browse/JBIDE-24391
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
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-4385
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4385) For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4385?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4385:
--------------------------------
Assignee: Jeff MAURY
> For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
> -------------------------------------------------------------------------
>
> Key: JBDS-4385
> URL: https://issues.jboss.org/browse/JBDS-4385
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: task
> Fix For: 10.4.0.GA
>
>
> For JBDS 10.4.0.GA: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 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
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4385) For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
by Jeff MAURY (JIRA)
Jeff MAURY created JBDS-4385:
--------------------------------
Summary: For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
Key: JBDS-4385
URL: https://issues.jboss.org/browse/JBDS-4385
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: installer
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 10.4.0.GA
For JBDS 10.4.0.GA: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x 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 jbosstools-4.4.x
3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x 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 jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
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
(v7.2.3#72005)
8 years, 11 months