August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4710: ----------------------------- Fix Version/s: 12.x (was: 12.9.0.AM2) > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.x > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4719) Eclipse will not change to alternate JDK with Spring Boot project.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4719?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4719: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > Eclipse will not change to alternate JDK with Spring Boot project. > ------------------------------------------------------------------ > > Key: JBDS-4719 > URL: https://issues.jboss.org/browse/JBDS-4719 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 11.3.0.GA > Reporter: Hiram Chirino > Assignee: Jeff MAURY > Fix For: 12.x > > > Feed back from [~egetchel] in a recent Fuse enablement session: > This seems specific to JBDS 11.x as it is not a problem in 10. Typical scenario - I start a new project in Eclipse and it defaults to a JRE enviornment. This gets picked up at runtime. I add the JDK to Eclipse. Normally, I can go into the project configuration and change the compile and runtime to use the new JDK. In Eclipse 11, we could not find any option to do this, and no matter what we did, running the Spring Boot project still defaulted back to the JRE. The only way to force Eclipse to use the JDK was to go into Eclipse and delete the reference to the JRE, so that only a single JDK existed. -- 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 resolved JBIDE-26313. -------------------------------- Resolution: Done Quick fix: https://github.com/jbosstools/jbosstools-build-ci/commit/46ff99c9d30610f5... Thanks, SO: https://stackoverflow.com/questions/9942594/unicodeencodeerror-ascii-code... > 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-26147) Incremental publish not working with WF13, WF12 and WF11

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26147: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Incremental publish not working with WF13, WF12 and WF11 > -------------------------------------------------------- > > Key: JBIDE-26147 > URL: https://issues.jboss.org/browse/JBIDE-26147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Fix For: 4.9.x > > Attachments: helloworld-rs.zip > > > Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context. > This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0. > Then this code is commented out, the application is incrementally published but the error persists -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26147) Incremental publish not working with WF13, WF12 and WF11

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26147: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Incremental publish not working with WF13, WF12 and WF11 > -------------------------------------------------------- > > Key: JBIDE-26147 > URL: https://issues.jboss.org/browse/JBIDE-26147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Fix For: 4.9.x > > Attachments: helloworld-rs.zip > > > Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context. > This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0. > Then this code is commented out, the application is incrementally published but the error persists -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26117: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) > ----------------------------------------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.9.x > > > The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi... > Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection: > The Eclipse > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26117: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) > ----------------------------------------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.9.x > > > The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi... > Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection: > The Eclipse > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22138: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.x > > Attachments: image-2018-06-22-19-02-57-247.png > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22138: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.x > > Attachments: image-2018-06-22-19-02-57-247.png > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4719) Eclipse will not change to alternate JDK with Spring Boot project.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4719?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4719: ----------------------------- Fix Version/s: 12.x (was: 12.9.0.AM2) > Eclipse will not change to alternate JDK with Spring Boot project. > ------------------------------------------------------------------ > > Key: JBDS-4719 > URL: https://issues.jboss.org/browse/JBDS-4719 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 11.3.0.GA > Reporter: Hiram Chirino > Assignee: Jeff MAURY > Fix For: 12.x > > > Feed back from [~egetchel] in a recent Fuse enablement session: > This seems specific to JBDS 11.x as it is not a problem in 10. Typical scenario - I start a new project in Eclipse and it defaults to a JRE enviornment. This gets picked up at runtime. I add the JDK to Eclipse. Normally, I can go into the project configuration and change the compile and runtime to use the new JDK. In Eclipse 11, we could not find any option to do this, and no matter what we did, running the Spring Boot project still defaulted back to the JRE. The only way to force Eclipse to use the JDK was to go into Eclipse and delete the reference to the JRE, so that only a single JDK existed. -- 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