[JBoss JIRA] (JBDS-3843) For JBDS 10.0.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3843?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3843:
------------------------------------
Assignee: Denis Golovin
> 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
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: task
> 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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22202?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22202:
--------------------------------------
Assignee: Alexey Kazakov
> 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
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> 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-22218) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22218?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22218:
--------------------------------------
Assignee: Fred Bricon
> 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/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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22219?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22219:
--------------------------------------
Assignee: Xavier Coulon
> 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
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> 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-22217) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Freemarker]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22217?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22217:
----------------------------------------
Suspicious commits:
https://github.com/jbosstools/jbosstools-freemarker//commit/d33f8812a72b9...
https://github.com/jbosstools/jbosstools-freemarker//commit/b4c28ff7b02ec...
> 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
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> 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-22217) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Freemarker]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22217?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22217:
--------------------------------------
Assignee: Alexey Kazakov
> 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
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> 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-22214) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [BrowserSim]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22214?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22214:
--------------------------------------
Assignee: Ilya Buziuk
> 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
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> 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