February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23892) Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23892?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23892: --------------------------------- Assignee: Koen Aers > Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23892 > URL: https://issues.jboss.org/browse/JBIDE-23892 > Project: Tools (JBoss Tools) > Issue Type: Task > Affects Versions: 4.4.3.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23892) Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23892?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23892: ------------------------------ Fix Version/s: 4.4.3.Final > Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23892 > URL: https://issues.jboss.org/browse/JBIDE-23892 > Project: Tools (JBoss Tools) > Issue Type: Task > Affects Versions: 4.4.3.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23892) Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23892?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23892: ------------------------------ Component/s: hibernate > Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23892 > URL: https://issues.jboss.org/browse/JBIDE-23892 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.3.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23892) Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23892?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23892: ------------------------------ Affects Version/s: 4.4.3.AM2 > Add tests for org.jboss.tools.hibernate.runtime.spi.IOverrideRepository in the runtime providers > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23892 > URL: https://issues.jboss.org/browse/JBIDE-23892 > Project: Tools (JBoss Tools) > Issue Type: Task > Affects Versions: 4.4.3.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Claudio Weiler (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ] Claudio Weiler commented on JBIDE-23872: ---------------------------------------- [~rob.stryker], ok, lets move on on server or module publish actions, I updated workaround method to let it more clear. Your 1-2-3 steps match with my observations, but it do not full publish in "server publish" action. Here a desktop record of it: [youtu.be/sdmAR0S3rSQ|https://youtu.be/sdmAR0S3rSQ] Maybe this behavior is relative of some configuration in my Eclipse, but all settings that I try do not change this, what "almost" worked was: - Enabled compressed deploy. This solves empty deploy, but each deploy for simple changes is slow and reset session. - Disable deploy on server start (eclipse). This removes the empty deploy on server start, but on any simple resource change an empty deploy is made. I would like to strengthen that this is for WAR module resources in an EAR project, EJB module is published ok. > Tools clear war deployed files > ------------------------------ > > Key: JBIDE-23872 > URL: https://issues.jboss.org/browse/JBIDE-23872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: Windows 7 64 > JDK 8 > Eclipse Neon 1 > JBoss Tools 4.4 > WildFly 10.1 > Reporter: Claudio Weiler > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > After an Eclipse start war deployed files are deleted and not republished. > I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: > "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-481) Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-481: --------------------------------------- Summary: Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025] Key: ERT-481 URL: https://issues.jboss.org/browse/ERT-481 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23603) Server adapter: changes to eap are (published but) not visible unless in debug

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23603?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23603: ------------------------------------- Workaround Description: First option: after changes, right-click on server adapter -> Clean... -> OK Second option:Restart the server adapter in Debug mode was:Restart the server adapter in Debug mode > Server adapter: changes to eap are (published but) not visible unless in debug > ------------------------------------------------------------------------------ > > Key: JBIDE-23603 > URL: https://issues.jboss.org/browse/JBIDE-23603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23514. ------------------------------- Verified in 4.4.3 latest nightly (OS 3 v. 3.3.2.v20170210-0414). > Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23514 > URL: https://issues.jboss.org/browse/JBIDE-23514 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: jmx, openshift_v3, server_adapter > Fix For: 4.4.3.Final > > Attachments: jmx-error-nodejs.png > > > Most likely server adapters for non-java based apps should not have a jmx node. > Steps to reproduce: > # ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template) > # ASSERT: make sure the build is finished, the pod is running. > # ASSERT: make sure that you have a server adapter for your service > # ASSERT: make sure that it is in "[Started, Synchronized]" state) > # EXEC: unfold the server adapter and double click on the JMX child > Result: > An error shows up > !jmx-error-nodejs.png! > {code} > java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328) > at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278) > at org.jolokia.client.J4pClient.execute(J4pClient.java:191) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4276) Update OpenJDK to 8u121

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4276?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4276. ----------------------------- Verified in master and 1.3.0 latest. > Update OpenJDK to 8u121 > ----------------------- > > Key: JBDS-4276 > URL: https://issues.jboss.org/browse/JBDS-4276 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.3.0.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.GA > > > DM link: https://developers.redhat.com/download-manager/file/java-1.8.0-openjdk-1.... > sha256: de5ea4e373cc913fa89942800998d92fb926f29ae393a2d24a9140a1d821e611 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23886) Delete Resource: when deleting a resource we should say what resource type is deleted

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23886?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23886. ------------------------------- Verified in 4.4.3 latest nightly (OS 3 v. 3.3.2.v20170210-0414). > Delete Resource: when deleting a resource we should say what resource type is deleted > ------------------------------------------------------------------------------------- > > Key: JBIDE-23886 > URL: https://issues.jboss.org/browse/JBIDE-23886 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.Final > > > When deleting a single resource, we're telling the user that we're deleting a resource. It would be valuable information to tell the user what kind of resource this actually is. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017