June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26117) New OpenShift Connection Wizard: Parse Login command

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-26117: ------------------------------------- Summary: New OpenShift Connection Wizard: Parse Login command 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 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26059) OpenShift New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26059?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26059. ------------------------------ Resolution: Rejected > OpenShift New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26059 > URL: https://issues.jboss.org/browse/JBIDE-26059 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26045 #comment Create N&N for OpenShift 4.6.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26046) Central New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26046?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26046. ------------------------------ Resolution: Rejected > Central New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26046 > URL: https://issues.jboss.org/browse/JBIDE-26046 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Central by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26045 #comment Create N&N for Central 4.6.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26015) write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26015?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26015: ------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.x) > write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI > ------------------------------------------------------------------------ > > Key: JBIDE-26015 > URL: https://issues.jboss.org/browse/JBIDE-26015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.Final > > > Need new doc(s) in https://github.com/jbosstools/jbosstools-devdoc/ > * get and build maven tool from https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... > * configure keystore per https://github.com/nickboldt/maven-plugins/blob/master/hudson-job-sync-pl... > * jenkins crumbs - https://stackoverflow.com/questions/16738441/how-to-request-for-crumb-iss... > * set up bash & pom-sync.xml scripts (with examples) > * pull jobs (one by one or batch modes) > * edit jobs / save changes to github repo > * push jobs back to server (one by one or batch push mode) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26015) write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26015?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26015: ------------------------------------ Step one: update upstream docs. https://github.com/nickboldt/maven-plugins Step two: write moar docs. > write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI > ------------------------------------------------------------------------ > > Key: JBIDE-26015 > URL: https://issues.jboss.org/browse/JBIDE-26015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.Final > > > Need new doc(s) in https://github.com/jbosstools/jbosstools-devdoc/ > * get and build maven tool from https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... > * configure keystore per https://github.com/nickboldt/maven-plugins/blob/master/hudson-job-sync-pl... > * jenkins crumbs - https://stackoverflow.com/questions/16738441/how-to-request-for-crumb-iss... > * set up bash & pom-sync.xml scripts (with examples) > * pull jobs (one by one or batch modes) > * edit jobs / save changes to github repo > * push jobs back to server (one by one or batch push mode) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26097) remove TARGET_PLATFORM_CENTRAL_MAX and TARGET_PLATFORM_VERSION_MAX hardcoding in Jenkins jobs; read from parent pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26097?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-26097. -------------------------------- Resolution: Done > remove TARGET_PLATFORM_CENTRAL_MAX and TARGET_PLATFORM_VERSION_MAX hardcoding in Jenkins jobs; read from parent pom > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26097 > URL: https://issues.jboss.org/browse/JBIDE-26097 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM3 > > > remove TARGET_PLATFORM_CENTRAL_MAX and TARGET_PLATFORM_VERSION_MAX hardcoding in Jenkins jobs > Instead, read from parent pom like this: > {code} > function getVar() { > file=$1 > var=$2 > getVar_return=$(grep "<${var}>" $file | sed -e "s#.*<${var}>$.\+$</${var}>.*#\1#") > } > wget https://raw.githubusercontent.com/jbosstools/jbosstools-build/master/pare... -O parent-pom.xml > getVar pom.xml TARGET_PLATFORM_VERSION_MAX; TARGET_PLATFORM_VERSION_MAX=$getVar_return > getVar pom.xml TARGET_PLATFORM_CENTRAL_MAX; TARGET_PLATFORM_CENTRAL_MAX=$getVar_return > rm -f parent-pom.xml > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26081) Create script to purge old vsix and zip files from a staging folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26081?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-26081. -------------------------------- Assignee: Nick Boldt Resolution: Done > Create script to purge old vsix and zip files from a staging folder > ------------------------------------------------------------------- > > Key: JBIDE-26081 > URL: https://issues.jboss.org/browse/JBIDE-26081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, stack-server-protocol > Affects Versions: 4.6.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM3 > > > Need a groovy scriptlet to: > a) check a dir for files > b) find the latest release for each set of files > c) keep that one and delete the rest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26101) CreateServer request fails when ssp is running in Apache Felix

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26101?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-26101: -------------------------------- Fix Version/s: 4.6.0.Final > CreateServer request fails when ssp is running in Apache Felix > -------------------------------------------------------------- > > Key: JBIDE-26101 > URL: https://issues.jboss.org/browse/JBIDE-26101 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Environment: server is running in Apache Felix as > {code}java -jar bin/felix.jar{code} > server/createServer request fails with exceptions > {code}SEVERE: Internal error: java.lang.reflect.InvocationTargetException > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:63) > at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.request(GenericEndpoint.java:116) > at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleRequest(RemoteEndpoint.java:252) > at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:181) > at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:183) > at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:92) > at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:61) > ... 11 more > Caused by: java.lang.NoClassDefFoundError: org/jboss/tools/ssp/server/spi/model/polling/IPollResultListener > at org.jboss.tools.ssp.server.wildfly.servertype.impl.JBossServerFactory.createServerDelegate(JBossServerFactory.java:41) > at org.jboss.tools.ssp.server.model.ServerModel.createServer(ServerModel.java:97) > at org.jboss.tools.ssp.server.ServerManagementServerImpl.createServer(ServerManagementServerImpl.java:215) > ... 16 more > Caused by: java.lang.ClassNotFoundException: org.jboss.tools.ssp.server.spi.model.polling.IPollResultListener not found by org.jboss.tools.ssp.server [12] > at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1639) > at org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80) > at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 19 more > {code} > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-639) Investigate netcoredbg over Debug Adapter Protocol in Eclipse aCute

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-639?page=com.atlassian.jira.plugin.sy... ] Mickael Istria updated ERT-639: ------------------------------- Summary: Investigate netcoredbg over Debug Adapter Protocol in Eclipse aCute (was: Investigate netcoredbg in Eclipse aCute) > Investigate netcoredbg over Debug Adapter Protocol in Eclipse aCute > ------------------------------------------------------------------- > > Key: ERT-639 > URL: https://issues.jboss.org/browse/ERT-639 > Project: Eclipse Release Train > Issue Type: Enhancement > Reporter: Mickael Istria > > See https://github.com/Samsung/netcoredbg/issues/1#issuecomment-397981156 > netcoredbg can now be used over debug adapter protocol. It would be interesting to integrate it in Eclipse aCute to build at least one plugin at Eclipse.org on top of this DAP. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26115) OpenShift New and Noteworthy for 4.6.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26115?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26115: ------------------------------- Labels: task (was: ) > OpenShift New and Noteworthy for 4.6.0.Final > ----------------------------------------------------- > > Key: JBIDE-26115 > URL: https://issues.jboss.org/browse/JBIDE-26115 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.6.0.Final > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26102 #comment Create N&N for OpenShift 4.6.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.6.0.Final since the AM3 release of OpenShift, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.6.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.6.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 June 2018