August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26230) Implement Tycho build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26230?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26230: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Implement Tycho build > --------------------- > > Key: JBIDE-26230 > URL: https://issues.jboss.org/browse/JBIDE-26230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.9.x > > > Switch the Maven build to Tycho for: > * centralized management of dependencies > * unit tests in OSGI env -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26278: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.x > > > TBD -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26278: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.x > > > TBD -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26277) Update Test Plan for Devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26277?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26277: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Update Test Plan for Devstudio > ------------------------------ > > Key: JBIDE-26277 > URL: https://issues.jboss.org/browse/JBIDE-26277 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.x > > > Test plan is outdated and needs to be up to date. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26277) Update Test Plan for Devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26277?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26277: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Update Test Plan for Devstudio > ------------------------------ > > Key: JBIDE-26277 > URL: https://issues.jboss.org/browse/JBIDE-26277 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.x > > > Test plan is outdated and needs to be up to date. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26252) Implement better version of Project refresh in new app wizard

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26252?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26252: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Implement better version of Project refresh in new app wizard > ------------------------------------------------------------- > > Key: JBIDE-26252 > URL: https://issues.jboss.org/browse/JBIDE-26252 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.x > > > see https://issues.jboss.org/browse/JBIDE-26179 > There could be a better way to refresh projects in connection than Refresh button. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26313) checkUnresolvedIssues.py no longer works with latest python or latest JIRA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26313?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26313: ---------------------------------- Assignee: Nick Boldt > checkUnresolvedIssues.py no longer works with latest python or latest JIRA release > ---------------------------------------------------------------------------------- > > Key: JBIDE-26313 > URL: https://issues.jboss.org/browse/JBIDE-26313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > A couple months ago, I could run this script and it would automatically move JIRAs from last sprint to next sprint. > {code} > export userpass=JIRAUSER:JIRAPWD > # can filter out labels using --skipLabels "releasework, task, qa" etc. > # can do a dry run (list issues, do not change them) with -D > # skip verifying JIRA fixversions with -S > # automatically apply changes with -A > # for the latest sprint names see agile board https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=641&view=planning > # sometimes the sprint_NEXT is already created, but with a name that's different from what you might expect (eg., different month, wrong year) > # if previous sprint is done, use sprint=sprint_NEXT here > sprint="devex #153 August 2018" > sprint_NEXT="devex #154 September 2018" > versionWithRespin_jbt=4.9.0.AM2 > versionWithRespin_jbt_NEXT=4.9.0.AM3 > versionWithRespin_ds=12.9.0.AM2 > versionWithRespin_ds_NEXT=12.9.0.AM3 > python -W ignore /tmp/jbt.github/jbosstools-build-ci/util/checkUnresolvedIssues.py -S --jira https://issues.jboss.org \ > --jbt ${versionWithRespin_jbt} --jbt_NEXT ${versionWithRespin_jbt_NEXT} \ > --ds ${versionWithRespin_ds} --ds_NEXT ${versionWithRespin_ds_NEXT} \ > --sprint "${sprint}" --sprint_NEXT "${sprint_NEXT}" --skipLabels "task, releasework" -A > {code} > Now it's broken because ...? not sure. Problem happens on line 191. > {code} > Traceback (most recent call last): > File "/tmp/jbt.github/jbosstools-build-ci/util/checkUnresolvedIssues.py", line 191, in <module> > updateIssues(components.getIssuesFromQuery(query, jiraserver, jirauser, jirapwd), True, \ > File "/home/nboldt/tru/jbosstools-build-ci/util/components.py", line 196, in getIssuesFromQuery > return doQuery(query, 'item', jiraserver, jirauser, jirapwd, 1000) > File "/home/nboldt/tru/jbosstools-build-ci/util/components.py", line 215, in doQuery > xml = minidom.parseString(q.text) > File "/usr/lib64/python2.7/xml/dom/minidom.py", line 1928, in parseString > return expatbuilder.parseString(string) > File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 940, in parseString > return builder.parseString(string) > File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 223, in parseString > parser.Parse(string, True) > UnicodeEncodeError: 'ascii' codec can't encode character u'\ufffd' in position 172594: ordinal not in range(128) > {code} > Seems to be a problem with `xml = minidom.parseString(q.text)` on line 215 of components.py -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26252) Implement better version of Project refresh in new app wizard

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26252?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26252: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Implement better version of Project refresh in new app wizard > ------------------------------------------------------------- > > Key: JBIDE-26252 > URL: https://issues.jboss.org/browse/JBIDE-26252 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.x > > > see https://issues.jboss.org/browse/JBIDE-26179 > There could be a better way to refresh projects in connection than Refresh button. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26313) checkUnresolvedIssues.py no longer works with latest python or latest JIRA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26313?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26313: ------------------------------- Fix Version/s: 4.9.0.AM2 > checkUnresolvedIssues.py no longer works with latest python or latest JIRA release > ---------------------------------------------------------------------------------- > > Key: JBIDE-26313 > URL: https://issues.jboss.org/browse/JBIDE-26313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > A couple months ago, I could run this script and it would automatically move JIRAs from last sprint to next sprint. > {code} > export userpass=JIRAUSER:JIRAPWD > # can filter out labels using --skipLabels "releasework, task, qa" etc. > # can do a dry run (list issues, do not change them) with -D > # skip verifying JIRA fixversions with -S > # automatically apply changes with -A > # for the latest sprint names see agile board https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=641&view=planning > # sometimes the sprint_NEXT is already created, but with a name that's different from what you might expect (eg., different month, wrong year) > # if previous sprint is done, use sprint=sprint_NEXT here > sprint="devex #153 August 2018" > sprint_NEXT="devex #154 September 2018" > versionWithRespin_jbt=4.9.0.AM2 > versionWithRespin_jbt_NEXT=4.9.0.AM3 > versionWithRespin_ds=12.9.0.AM2 > versionWithRespin_ds_NEXT=12.9.0.AM3 > python -W ignore /tmp/jbt.github/jbosstools-build-ci/util/checkUnresolvedIssues.py -S --jira https://issues.jboss.org \ > --jbt ${versionWithRespin_jbt} --jbt_NEXT ${versionWithRespin_jbt_NEXT} \ > --ds ${versionWithRespin_ds} --ds_NEXT ${versionWithRespin_ds_NEXT} \ > --sprint "${sprint}" --sprint_NEXT "${sprint_NEXT}" --skipLabels "task, releasework" -A > {code} > Now it's broken because ...? not sure. Problem happens on line 191. > {code} > Traceback (most recent call last): > File "/tmp/jbt.github/jbosstools-build-ci/util/checkUnresolvedIssues.py", line 191, in <module> > updateIssues(components.getIssuesFromQuery(query, jiraserver, jirauser, jirapwd), True, \ > File "/home/nboldt/tru/jbosstools-build-ci/util/components.py", line 196, in getIssuesFromQuery > return doQuery(query, 'item', jiraserver, jirauser, jirapwd, 1000) > File "/home/nboldt/tru/jbosstools-build-ci/util/components.py", line 215, in doQuery > xml = minidom.parseString(q.text) > File "/usr/lib64/python2.7/xml/dom/minidom.py", line 1928, in parseString > return expatbuilder.parseString(string) > File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 940, in parseString > return builder.parseString(string) > File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 223, in parseString > parser.Parse(string, True) > UnicodeEncodeError: 'ascii' codec can't encode character u'\ufffd' in position 172594: ordinal not in range(128) > {code} > Seems to be a problem with `xml = minidom.parseString(q.text)` on line 215 of components.py -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26231) Implement state persistence

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26231?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26231: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Implement state persistence > --------------------------- > > Key: JBIDE-26231 > URL: https://issues.jboss.org/browse/JBIDE-26231 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.9.x > > > Server definitions and search pathes should be persistent so that users don't loose their work -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018