April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22226) Forge Wizard Cheatsheet Line Bug when moving backwards

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22226?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22226: ----------------------------------------- Looks like it's because of the serialVersionUID declared in the beginning of the file? Not sure how the cheatsheet handles this > Forge Wizard Cheatsheet Line Bug when moving backwards > ------------------------------------------------------ > > Key: JBIDE-22226 > URL: https://issues.jboss.org/browse/JBIDE-22226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Burr Sutter > Assignee: Snjezana Peco > > See the video > http://screencast.com/t/xmTabea5I -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22226) Forge Wizard Cheatsheet Line Bug when moving backwards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22226?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22226: -------------------------------------- Assignee: Snjezana Peco I'm not sure it's actually Forge specific or probably some upstream issue. [~snjeza] could you please take a look? cc: [~gastaldi]] > Forge Wizard Cheatsheet Line Bug when moving backwards > ------------------------------------------------------ > > Key: JBIDE-22226 > URL: https://issues.jboss.org/browse/JBIDE-22226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Burr Sutter > Assignee: Snjezana Peco > > See the video > http://screencast.com/t/xmTabea5I -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22226) Forge Wizard Cheatsheet Line Bug when moving backwards

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22226?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-22226 at 4/20/16 2:21 PM: ----------------------------------------------------------------- I'm not sure it's actually Forge specific or probably some upstream issue. [~snjeza] could you please take a look? cc: [~gastaldi] was (Author: akazakov): I'm not sure it's actually Forge specific or probably some upstream issue. [~snjeza] could you please take a look? cc: [~gastaldi]] > Forge Wizard Cheatsheet Line Bug when moving backwards > ------------------------------------------------------ > > Key: JBIDE-22226 > URL: https://issues.jboss.org/browse/JBIDE-22226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Burr Sutter > Assignee: Snjezana Peco > > See the video > http://screencast.com/t/xmTabea5I -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22211) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22211?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22211. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE] > -------------------------------------------------------------------------------------- > > Key: JBIDE-22211 > URL: https://issues.jboss.org/browse/JBIDE-22211 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Rob Stryker > Assignee: Viacheslav Kabanovich > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [JavaEE]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-javaee at https://github.com/jbosstools/jbosstools-javaee/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "e96264" is the last common ancestor of jbosstools-4.3.x and master > e96264 is 23 commits ago in branch master > e96264 is 19 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-javaee//commit/2d520a947a6ecd802... > - https://github.com/jbosstools/jbosstools-javaee//commit/ab8ac4c4f0e8f477d... > - https://github.com/jbosstools/jbosstools-javaee//commit/f21505be773e27a92... > - https://github.com/jbosstools/jbosstools-javaee//commit/4065cbff5708de0f7... > - https://github.com/jbosstools/jbosstools-javaee//commit/e1e0ef7c4bfdd6eda... > - https://github.com/jbosstools/jbosstools-javaee//commit/529f2e4ae943cf425... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JavaEE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22211) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22211?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22211: ------------------------------------- Seems this commit was another victim of context mattering in the patch-id. > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE] > -------------------------------------------------------------------------------------- > > Key: JBIDE-22211 > URL: https://issues.jboss.org/browse/JBIDE-22211 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Rob Stryker > Assignee: Viacheslav Kabanovich > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [JavaEE]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-javaee at https://github.com/jbosstools/jbosstools-javaee/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "e96264" is the last common ancestor of jbosstools-4.3.x and master > e96264 is 23 commits ago in branch master > e96264 is 19 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-javaee//commit/2d520a947a6ecd802... > - https://github.com/jbosstools/jbosstools-javaee//commit/ab8ac4c4f0e8f477d... > - https://github.com/jbosstools/jbosstools-javaee//commit/f21505be773e27a92... > - https://github.com/jbosstools/jbosstools-javaee//commit/4065cbff5708de0f7... > - https://github.com/jbosstools/jbosstools-javaee//commit/e1e0ef7c4bfdd6eda... > - https://github.com/jbosstools/jbosstools-javaee//commit/529f2e4ae943cf425... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JavaEE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3845) Copyright notice refers to 2015, not 2016

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3845?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3845: ---------------------------------- Thanks for the PR. Can you also do one for the 16+ JBT projects? :D > Copyright notice refers to 2015, not 2016 > ----------------------------------------- > > Key: JBDS-3845 > URL: https://issues.jboss.org/browse/JBDS-3845 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.1.0.GA > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.0.0.Alpha1 > > Attachments: screenshot-1.png > > > It is the same issue, two years in a row, maybe we can put a test in place to check the year? Or automate the replacement at build time? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3845) Copyright notice refers to 2015, not 2016

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3845?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3845: ----------------------------- Priority: Optional (was: Major) > Copyright notice refers to 2015, not 2016 > ----------------------------------------- > > Key: JBDS-3845 > URL: https://issues.jboss.org/browse/JBDS-3845 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.1.0.GA > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.0.0.Alpha1 > > Attachments: screenshot-1.png > > > It is the same issue, two years in a row, maybe we can put a test in place to check the year? Or automate the replacement at build time? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3845?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3845: ----------------------------- Fix Version/s: 10.0.0.Alpha1 > Copyright notice refers to 2015, not 2016 > ----------------------------------------- > > Key: JBDS-3845 > URL: https://issues.jboss.org/browse/JBDS-3845 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.1.0.GA > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.0.0.Alpha1 > > Attachments: screenshot-1.png > > > It is the same issue, two years in a row, maybe we can put a test in place to check the year? Or automate the replacement at build time? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22211) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22211?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22211: ----------------------------------------------- This issue can be closed. > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE] > -------------------------------------------------------------------------------------- > > Key: JBIDE-22211 > URL: https://issues.jboss.org/browse/JBIDE-22211 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Rob Stryker > Assignee: Viacheslav Kabanovich > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [JavaEE]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-javaee at https://github.com/jbosstools/jbosstools-javaee/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "e96264" is the last common ancestor of jbosstools-4.3.x and master > e96264 is 23 commits ago in branch master > e96264 is 19 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-javaee//commit/2d520a947a6ecd802... > - https://github.com/jbosstools/jbosstools-javaee//commit/ab8ac4c4f0e8f477d... > - https://github.com/jbosstools/jbosstools-javaee//commit/f21505be773e27a92... > - https://github.com/jbosstools/jbosstools-javaee//commit/4065cbff5708de0f7... > - https://github.com/jbosstools/jbosstools-javaee//commit/e1e0ef7c4bfdd6eda... > - https://github.com/jbosstools/jbosstools-javaee//commit/529f2e4ae943cf425... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JavaEE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22211) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE]

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22211?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22211: ----------------------------------------------- In master it is commit https://github.com/jbosstools/jbosstools-javaee/commit/5bfe287df1540e4137... > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JavaEE] > -------------------------------------------------------------------------------------- > > Key: JBIDE-22211 > URL: https://issues.jboss.org/browse/JBIDE-22211 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Rob Stryker > Assignee: Viacheslav Kabanovich > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [JavaEE]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-javaee at https://github.com/jbosstools/jbosstools-javaee/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "e96264" is the last common ancestor of jbosstools-4.3.x and master > e96264 is 23 commits ago in branch master > e96264 is 19 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-javaee//commit/2d520a947a6ecd802... > - https://github.com/jbosstools/jbosstools-javaee//commit/ab8ac4c4f0e8f477d... > - https://github.com/jbosstools/jbosstools-javaee//commit/f21505be773e27a92... > - https://github.com/jbosstools/jbosstools-javaee//commit/4065cbff5708de0f7... > - https://github.com/jbosstools/jbosstools-javaee//commit/e1e0ef7c4bfdd6eda... > - https://github.com/jbosstools/jbosstools-javaee//commit/529f2e4ae943cf425... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JavaEE task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016