September 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26283: ------------------------------- Priority: Major (was: Blocker) > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26283: ------------------------------- Fix Version/s: 4.9.0.Final (was: 4.9.x) > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26338) Changing ports in Server Editor does not work

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26338?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26338. --------------------------------- Resolution: Rejected Functioning as expected. Note the text above ports section: The ports entered here are which ports the tools\nwill poll the server on. Changing these fields\nwill not change the ports the server itself listens on. > Changing ports in Server Editor does not work > --------------------------------------------- > > Key: JBIDE-26338 > URL: https://issues.jboss.org/browse/JBIDE-26338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.AM3 > Environment: F28, EAP 7.1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.9.0.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26338) Changing ports in Server Editor does not work

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26338?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26338: ---------------------------------- Priority: Major (was: Critical) > Changing ports in Server Editor does not work > --------------------------------------------- > > Key: JBIDE-26338 > URL: https://issues.jboss.org/browse/JBIDE-26338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.AM3 > Environment: F28, EAP 7.1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.9.0.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26336) Upgrade jacoco version to 0.8.2+ to be compatible with Java 11

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26336?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-26336: ----------------------------------------- The best is to upgrade everything to use the latest jacoco version. It will provide more accurate code coverage. in a first time, using it only for jdk11 profile is fine. Upgrading for all versions (and so use the newest plugins on Jenkins) can be done in a second iteration. > Upgrade jacoco version to 0.8.2+ to be compatible with Java 11 > -------------------------------------------------------------- > > Key: JBIDE-26336 > URL: https://issues.jboss.org/browse/JBIDE-26336 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.9.0.AM3 > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.9.0.Final > > > https://github.com/jacoco/jacoco/releases/tag/v0.8.2 > {quote}Experimental support for Java 11 and Java 12 class files, including JEP 12 "preview features" (GitHub #719, #738, #743).{quote} > for now for SAp Tooling, I got > {noformat} > 09:37:54 Exception in thread "main" java.lang.reflect.InvocationTargetException > 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 09:37:54 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > 09:37:54 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 09:37:54 at java.base/java.lang.reflect.Method.invoke(Method.java:566) > 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) > 09:37:54 at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) > 09:37:54 Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented. > 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140) > 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101) > 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55) > 09:37:54 at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47) > 09:37:54 ... 6 more > 09:37:54 Caused by: java.lang.NoSuchFieldException: $jacocoAccess > 09:37:54 at java.base/java.lang.Class.getField(Class.java:2000) > 09:37:54 at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138) > 09:37:54 ... 9 more > 09:37:54 FATAL ERROR in native method: processing of -javaagent failed > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26358) Implement JMX integration tests

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-26358: ------------------------------------- Summary: Implement JMX integration tests Key: JBIDE-26358 URL: https://issues.jboss.org/browse/JBIDE-26358 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: integration-tests, jmx Affects Versions: 4.9.0.AM3 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.9.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26357) JMX MBean Tree is auto collapsing when walking down the tree items of EAP 7.1 server adapter

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-26357: ------------------------------------- Summary: JMX MBean Tree is auto collapsing when walking down the tree items of EAP 7.1 server adapter Key: JBIDE-26357 URL: https://issues.jboss.org/browse/JBIDE-26357 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.9.0.AM3 Reporter: Ondrej Dockal Attachments: JMXServerConnectionAutoCollapseIssue.gif JMX MBean tree in JMX Navigator do autocollapse when walking the through tree items. When I go for an item twice, it will not collapse only on first time. I am not sure about reproducing the issue as I got it when using EAP server adapter. Wildfly is not doing it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26357) JMX MBean Tree is auto collapsing when walking down the tree items of EAP 7.1 server adapter

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26357?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26357: ---------------------------------- Description: JMX MBean tree in JMX Navigator do autocollapse when walking the tree items. When I go for an item twice, it will not collapse only on first time. I am not sure about reproducing the issue as I got it when using EAP server adapter. Wildfly is not doing it. (was: JMX MBean tree in JMX Navigator do autocollapse when walking the through tree items. When I go for an item twice, it will not collapse only on first time. I am not sure about reproducing the issue as I got it when using EAP server adapter. Wildfly is not doing it.) > JMX MBean Tree is auto collapsing when walking down the tree items of EAP 7.1 server adapter > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26357 > URL: https://issues.jboss.org/browse/JBIDE-26357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.9.0.AM3 > Reporter: Ondrej Dockal > Attachments: JMXServerConnectionAutoCollapseIssue.gif > > > JMX MBean tree in JMX Navigator do autocollapse when walking the tree items. When I go for an item twice, it will not collapse only on first time. I am not sure about reproducing the issue as I got it when using EAP server adapter. Wildfly is not doing it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26356) Add org.jboss.tools.common.launcher.feature to JBoss Tools marketplace entry

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26356?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26356: ------------------------------------ Good reminder! This step is already documented in the release guide. https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... > Add org.jboss.tools.common.launcher.feature to JBoss Tools marketplace entry > ---------------------------------------------------------------------------- > > Key: JBIDE-26356 > URL: https://issues.jboss.org/browse/JBIDE-26356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.9.0.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.9.0.Final > > > Reminder to add this new feature to the JBoss Tools Eclipse marketplace entry -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26085) Rewrite CDK itests to use cdk downloaded via download runtime wizard

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26085?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26085. --------------------------------- > Rewrite CDK itests to use cdk downloaded via download runtime wizard > -------------------------------------------------------------------- > > Key: JBIDE-26085 > URL: https://issues.jboss.org/browse/JBIDE-26085 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, integration-tests > Affects Versions: 4.6.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.9.0.AM3 > > > Implement DownloadCDKRuntime requirement that will get CDK and configure it via setup-cdk. Requirement should be use once to download latest cdk bits and reuse it for all suitable test classes. > Next step it to avoid using cdk-scripts as much as possible as so simplify setting up cdk in jenkins jobs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 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 September 2018