[JBoss JIRA] (JBIDE-22210) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Playground]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22210?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22210:
--------------------------------------
Assignee: Mickael Istria
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Playground]
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22210
> URL: https://issues.jboss.org/browse/JBIDE-22210
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: playground
> Reporter: Rob Stryker
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Playground]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-playground at https://github.com/jbosstools/jbosstools-playground/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "476620" is the last common ancestor of jbosstools-4.3.x and master
> 476620 is 4 commits ago in branch master
> 476620 is 8 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-playground//commit/c97d38ca3d141...
> - https://github.com/jbosstools/jbosstools-playground//commit/c6e3153a43e7c...
> - https://github.com/jbosstools/jbosstools-playground//commit/15c2c008ae837...
> - https://github.com/jbosstools/jbosstools-playground//commit/c82b4104d8df7...
> - https://github.com/jbosstools/jbosstools-playground//commit/16de3723185fd...
> - https://github.com/jbosstools/jbosstools-playground//commit/9758d0bfd73a8...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Playground task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22204) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [VPE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22204?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22204:
--------------------------------------
Assignee: Ilya Buziuk
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [VPE]
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22204
> URL: https://issues.jboss.org/browse/JBIDE-22204
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Rob Stryker
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [VPE]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-vpe at https://github.com/jbosstools/jbosstools-vpe/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "5fdde4" is the last common ancestor of jbosstools-4.3.x and master
> 5fdde4 is 10 commits ago in branch master
> 5fdde4 is 9 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-vpe//commit/a2b21f1b38c67f967e9a...
> - https://github.com/jbosstools/jbosstools-vpe//commit/32507f22347e7a78b46c...
> - https://github.com/jbosstools/jbosstools-vpe//commit/614fe8ef79e3e14383e9...
> - https://github.com/jbosstools/jbosstools-vpe//commit/342bb8f7a473e668918d...
> - https://github.com/jbosstools/jbosstools-vpe//commit/a9273884abd848332359...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for VPE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22206) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22206?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22206:
--------------------------------------
Assignee: Rob Stryker
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-22206
> URL: https://issues.jboss.org/browse/JBIDE-22206
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Server]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-server at https://github.com/jbosstools/jbosstools-server/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "ecbe98" is the last common ancestor of jbosstools-4.3.x and master
> ecbe98 is 50 commits ago in branch master
> ecbe98 is 52 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-server//commit/f8d95f7d1465dd60b...
> - https://github.com/jbosstools/jbosstools-server//commit/122eb9e528632345c...
> - https://github.com/jbosstools/jbosstools-server//commit/b1d95cd1ee50b92c1...
> - https://github.com/jbosstools/jbosstools-server//commit/a9a35aee507b59453...
> - https://github.com/jbosstools/jbosstools-server//commit/078a82d8f76cb02e3...
> - https://github.com/jbosstools/jbosstools-server//commit/c1c87bd10ba0e9a2c...
> - https://github.com/jbosstools/jbosstools-server//commit/784c82b35b3843f8e...
> - https://github.com/jbosstools/jbosstools-server//commit/648b5425c80e6301d...
> - https://github.com/jbosstools/jbosstools-server//commit/fdf66d3515c5f0782...
> - https://github.com/jbosstools/jbosstools-server//commit/7d6b1b7e31194bf49...
> - https://github.com/jbosstools/jbosstools-server//commit/bbf53cbb92c7cfc10...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22207) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Hibernate]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22207?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22207:
--------------------------------------
Assignee: Koen Aers
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Hibernate]
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22207
> URL: https://issues.jboss.org/browse/JBIDE-22207
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Rob Stryker
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Hibernate]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-hibernate at https://github.com/jbosstools/jbosstools-hibernate/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "fe17a3" is the last common ancestor of jbosstools-4.3.x and master
> fe17a3 is 226 commits ago in branch master
> fe17a3 is 14 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-hibernate//commit/40d70e779b0f4e...
> - https://github.com/jbosstools/jbosstools-hibernate//commit/470f7350047717...
> - https://github.com/jbosstools/jbosstools-hibernate//commit/1aebe78228b378...
> - https://github.com/jbosstools/jbosstools-hibernate//commit/e4ef139e682ab0...
> - https://github.com/jbosstools/jbosstools-hibernate//commit/4433454f98bcd9...
> - https://github.com/jbosstools/jbosstools-hibernate//commit/af17a74daccaf0...
> - https://github.com/jbosstools/jbosstools-hibernate//commit/0cfa89c8a3686f...
> - https://github.com/jbosstools/jbosstools-hibernate//commit/d30996173ae1a7...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Hibernate task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22203) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Aerogear]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22203?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22203:
--------------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Aerogear]
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-22203
> URL: https://issues.jboss.org/browse/JBIDE-22203
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Rob Stryker
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Aerogear]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-aerogear at https://github.com/jbosstools/jbosstools-aerogear/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "fbcaf6" is the last common ancestor of jbosstools-4.3.x and master
> fbcaf6 is 10 commits ago in branch master
> fbcaf6 is 20 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-aerogear//commit/938198c0668e1f5...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/c5207dc9e034c51...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/b2f26d53504a256...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/fd189752b6f5209...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/002faaa2701ce0a...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/d1776c97ba01bbf...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/ec4a1312844e068...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/a7686517ded4ef9...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/58fbd4aa7342c66...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/7c3d92f4e47f85b...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/af2dba422b0617a...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/b03070aaf0ea89f...
> - https://github.com/jbosstools/jbosstools-aerogear//commit/a37e1d0f565e234...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Aerogear task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3738:
---------------------------------
Just had a conversation with Alexey about this issue. The action items are:
1. We need a redirect to the current content, which is available on access.redhat.com[1]. ORG-3052 tracks the redirect issue. We need someone from Marketing or PM team to create the redirect from the installer.
2. We need to polish the content for CDK (see [1]) and Alexey and Marian have provided some feedback already for this. I'll be working on this in the next few days till we have a finalized version.
[1] - https://access.redhat.com/articles/2255401
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Priority: Blocker
> Labels: Havoc
> Fix For: 9.1.0.GA
>
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
> URL: http://developers.redhat.com/devstudio-preview
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22206) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22206?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22206:
-------------------------------------
Four suspicious commits:
https://github.com/jbosstools/jbosstools-server//commit/f8d95f7d1465dd60b...
https://github.com/jbosstools/jbosstools-server//commit/b1d95cd1ee50b92c1...
https://github.com/jbosstools/jbosstools-server//commit/fdf66d3515c5f0782...
https://github.com/jbosstools/jbosstools-server//commit/bbf53cbb92c7cfc10...
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Server]
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-22206
> URL: https://issues.jboss.org/browse/JBIDE-22206
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Server]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-server at https://github.com/jbosstools/jbosstools-server/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "ecbe98" is the last common ancestor of jbosstools-4.3.x and master
> ecbe98 is 50 commits ago in branch master
> ecbe98 is 52 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-server//commit/f8d95f7d1465dd60b...
> - https://github.com/jbosstools/jbosstools-server//commit/122eb9e528632345c...
> - https://github.com/jbosstools/jbosstools-server//commit/b1d95cd1ee50b92c1...
> - https://github.com/jbosstools/jbosstools-server//commit/a9a35aee507b59453...
> - https://github.com/jbosstools/jbosstools-server//commit/078a82d8f76cb02e3...
> - https://github.com/jbosstools/jbosstools-server//commit/c1c87bd10ba0e9a2c...
> - https://github.com/jbosstools/jbosstools-server//commit/784c82b35b3843f8e...
> - https://github.com/jbosstools/jbosstools-server//commit/648b5425c80e6301d...
> - https://github.com/jbosstools/jbosstools-server//commit/fdf66d3515c5f0782...
> - https://github.com/jbosstools/jbosstools-server//commit/7d6b1b7e31194bf49...
> - https://github.com/jbosstools/jbosstools-server//commit/bbf53cbb92c7cfc10...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22216) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22216?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-22216.
---------------------------------
Resolution: Done
> 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
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> 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-22216) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22216?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-22216:
-------------------------------------
Assignee: Snjezana Peco
> 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
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> 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