May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25911) Remove arquillian from integration test repo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25911?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25911: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > Remove arquillian from integration test repo > -------------------------------------------- > > Key: JBIDE-25911 > URL: https://issues.jboss.org/browse/JBIDE-25911 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian, integration-tests > Affects Versions: 4.5.3.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25892) Label truncated when downloading CDK runtime

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25892?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25892: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM1) > Label truncated when downloading CDK runtime > -------------------------------------------- > > Key: JBIDE-25892 > URL: https://issues.jboss.org/browse/JBIDE-25892 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.3.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, cdk_server_adapter, cdk_server_adapter_wizard > Fix For: 4.6.x > > Attachments: screenshot-1.png, screenshot-2.png > > > When downloading the CDK runtime, once you selected a specific CDK version the URL and a message are displayed. But the message is truncated -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25981) Fix eap7x-compatibility profile in Server ITests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25981?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25981: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > Fix eap7x-compatibility profile in Server ITests > ------------------------------------------------ > > Key: JBIDE-25981 > URL: https://issues.jboss.org/browse/JBIDE-25981 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, server > Affects Versions: 4.5.3.Final > Environment: F28, RHEL6&7 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25980) Executing query in HQL editor or Hibernate Criteria editor produces exception

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25980?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25980: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM1) > Executing query in HQL editor or Hibernate Criteria editor produces exception > ----------------------------------------------------------------------------- > > Key: JBIDE-25980 > URL: https://issues.jboss.org/browse/JBIDE-25980 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.3.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.6.x > > > To reproduce: > - create project > - create cfg.xml and console configuration (use the sakila database) > - reverse engineer from sakila > - open hql editor and execute 'select o.filmActors from Actor o' > - resulting error: 'java.lang.IllegalArgumentException: Not an entity [class java.lang.String]' > It seems to happen in an inconsistent way: > - only the first two time? > - only when using hibernate 5.3? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25980) Executing query in HQL editor or Hibernate Criteria editor produces exception

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25980?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25980: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.x* > Executing query in HQL editor or Hibernate Criteria editor produces exception > ----------------------------------------------------------------------------- > > Key: JBIDE-25980 > URL: https://issues.jboss.org/browse/JBIDE-25980 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.3.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.6.x > > > To reproduce: > - create project > - create cfg.xml and console configuration (use the sakila database) > - reverse engineer from sakila > - open hql editor and execute 'select o.filmActors from Actor o' > - resulting error: 'java.lang.IllegalArgumentException: Not an entity [class java.lang.String]' > It seems to happen in an inconsistent way: > - only the first two time? > - only when using hibernate 5.3? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25974: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM1) > CDK 3.4 runtime detection failing > --------------------------------- > > Key: JBIDE-25974 > URL: https://issues.jboss.org/browse/JBIDE-25974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.6.x > > Attachments: image-2018-05-07-17-59-59-316.png > > > Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better > steps: > # EXE: Preferences > JBoss Runtime Detection > Download > # ASSERT: List of available runtimes shows up, containing CDK 3.4.0 > # EXEC: Choose "CDK 3.4.0" & hit "Next" > # EXEC: next page: provide credentials & hit "Next" > # EXEC: next page: accept the terms & hit "Next" > # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish" > # ASSERT: wait for the download to finish > Result: > The download wont detect the new CDK 3.4.0 that you just downloaded > !image-2018-05-07-17-59-59-316.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25446: ------------------------------- Fix Version/s: 4.6.0.AM2 (was: 4.6.0.AM1) > Windows/Mac slave gets disconnected during job execution > -------------------------------------------------------- > > Key: JBIDE-25446 > URL: https://issues.jboss.org/browse/JBIDE-25446 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Blocker > Labels: jenkins > Fix For: 4.6.0.AM2, 4.6.x > > > During jenkins job execution slaves is disconnected with exception > {code} > 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available.... > 19:09:32 FATAL: command execution failed > 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected. > 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191) > 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) > 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035) > 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399) > 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367) > 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) > 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205) > 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) > 19:09:32 at hudson.model.Run.execute(Run.java:1728) > 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) > 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98) > 19:09:32 at hudson.model.Executor.run(Executor.java:404) > 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148] > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635) > 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) > 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > 19:09:32 at java.lang.Thread.run(Thread.java:748) > 19:09:32 Caused by: java.io.IOException: Connection reset by peer > 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197) > 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564) > 19:09:32 ... 6 more > 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25446: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.0.AM2* and sprint = *devex #149 May 2018* > Windows/Mac slave gets disconnected during job execution > -------------------------------------------------------- > > Key: JBIDE-25446 > URL: https://issues.jboss.org/browse/JBIDE-25446 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Blocker > Labels: jenkins > Fix For: 4.6.0.AM2, 4.6.x > > > During jenkins job execution slaves is disconnected with exception > {code} > 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available.... > 19:09:32 FATAL: command execution failed > 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected. > 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191) > 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) > 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035) > 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399) > 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367) > 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) > 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205) > 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) > 19:09:32 at hudson.model.Run.execute(Run.java:1728) > 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) > 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98) > 19:09:32 at hudson.model.Executor.run(Executor.java:404) > 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148] > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635) > 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) > 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > 19:09:32 at java.lang.Thread.run(Thread.java:748) > 19:09:32 Caused by: java.io.IOException: Connection reset by peer > 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197) > 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564) > 19:09:32 ... 6 more > 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24933) Add ITest for editing the oc location when creating/editing a connection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24933?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24933: ------------------------------- Fix Version/s: 4.6.0.AM2 (was: 4.6.0.AM1) > Add ITest for editing the oc location when creating/editing a connection > ------------------------------------------------------------------------ > > Key: JBIDE-24933 > URL: https://issues.jboss.org/browse/JBIDE-24933 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Labels: connection_wizard, integration_tests, openshift_v3 > Fix For: 4.6.0.AM2 > > > https://issues.jboss.org/browse/JBIDE-24802 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24933) Add ITest for editing the oc location when creating/editing a connection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24933?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24933: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.6.0.AM2* and sprint = *devex #149 May 2018* > Add ITest for editing the oc location when creating/editing a connection > ------------------------------------------------------------------------ > > Key: JBIDE-24933 > URL: https://issues.jboss.org/browse/JBIDE-24933 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Labels: connection_wizard, integration_tests, openshift_v3 > Fix For: 4.6.0.AM2 > > > https://issues.jboss.org/browse/JBIDE-24802 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 May 2018