April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25873) Runtime detection: Displayed type CDK 3.2 is confusing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25873?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-25873. --------------------------------- Verified that it says 3.2+ now. Closing. > Runtime detection: Displayed type CDK 3.2 is confusing > ------------------------------------------------------ > > Key: JBIDE-25873 > URL: https://issues.jboss.org/browse/JBIDE-25873 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift, runtime-detection > Affects Versions: 4.5.3.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: runtime_detection > Fix For: 4.5.3.Final > > Attachments: image-2018-03-28-16-26-09-154.png > > > # ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it > # EXEC: restart your Eclipse > Result: > You get the following dialog when Eclipse is up again: > !image-2018-03-28-16-26-09-154.png! > It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3? > A simple change for the type ex. "CDK 3.2+" would make things so much more obvious. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25858) Minishift binary is not set up after CDK runtime download

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25858?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-25858. --------------------------------- It works as expected now (devstudio 11.3.0.GA), for the most part. Closing. > Minishift binary is not set up after CDK runtime download > --------------------------------------------------------- > > Key: JBIDE-25858 > URL: https://issues.jboss.org/browse/JBIDE-25858 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.3.Final > > > This is a followup of JBIDE-25835 . > Recently a new feature was added - cdk can be downloaded directly from the IDE now. > As with other runtimes, there are two main paths you can take: > a) New Server -> Download > b) Preferences -> Runtime Detection -> Download > tl;dr: b) doesn't work properly with cdk because minishift binary is still not set after the download. > There is quite a big difference between a) and b). With a), you are adding a server manually and once your download is finished, the correct path is predefined for you. Runtime detection is not involved. > With b), the server is downloaded, extracted and then the path is added to runtime detection which is in turn run. This will result in the new server being detected and added. > Now cdk should theoretically support both of these paths. a) works - you're in the middle of adding a cdk server manually, you invoke the download and once that's done, the minishift binary field is filled properly for you. > But b) doesn't work properly for cdk, because runtime detection for cdk is built around your minishift home and not the minishift binary path. (I don't really know why that's the case, but I guess you had a good reason for it.) So when you do b), cdk binary is downloaded, but what's added to runtime detection is ~/.minishift (or $MINISHIFT_HOME if set). The result is that the cdk server adapter is added once the download is finished, but the minishift binary remains empty. So the usefulness of this feature is questionable. > Maybe you will say that there is no way to fix this. I hope you will at least agree that this is not ideal and b) doesn't really work properly right now. > I don't know what the proper solution for this is but let me start with a question: Wouldn't it make sense to change runtime detection of cdk so that it uses the minishift binary as the main path? What's stopping us from doing that? > Sorry for the lengthy description, I felt I needed to explain the whole context here. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25921) MacOS machines with label mac_xhyve are not capable of running cdk.itests

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-25921: ------------------------------------- Summary: MacOS machines with label mac_xhyve are not capable of running cdk.itests Key: JBIDE-25921 URL: https://issues.jboss.org/browse/JBIDE-25921 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, qa Affects Versions: 4.5.3.Final Environment: Mac OS High Sierra Reporter: Ondrej Dockal Assignee: Ondrej Dockal Priority: Critical Fix For: 4.6.0.AM1 Recently, cdk.itests are not able to be run on Mac OS machines within jenkins with label mac_xhyve. * find out cause of instability * add another mac os machines into label (dev_platform_mac) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25862) Starting of devstudio introduce ArrayIndexOutOfBoundsException in Error Log from org.jboss.tools.jmx.jvmmonitor.tools

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25862?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-25862. --------------------------------- Fixed in the related issue - JBIDE-25864. Closing. > Starting of devstudio introduce ArrayIndexOutOfBoundsException in Error Log from org.jboss.tools.jmx.jvmmonitor.tools > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25862 > URL: https://issues.jboss.org/browse/JBIDE-25862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.5.3.AM3 > Reporter: Ondrej Dockal > Assignee: Dmitrii Bocharov > Fix For: 4.5.3.Final > > > {code:java} > eclipse.buildId=11.3.0.AM3-v20180322-1027-B2194 > java.version=1.8.0_161 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.jmx.jvmmonitor.tools > Error > Mon Mar 26 23:57:42 CEST 2018 > Update timer canceled. > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.jboss.tools.common.jdt.debug.JavaUtilities.getMajorMinor(JavaUtilities.java:55) > at org.jboss.tools.common.jdt.debug.JavaUtilities.isJigsawRunning(JavaUtilities.java:33) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:110) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:101) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:69) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:60) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:181) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25920) Provide API to filter out "references to extensions that can be installed" when opening "New Server Runtime Environment"

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-25920: --------------------------------------- Summary: Provide API to filter out "references to extensions that can be installed" when opening "New Server Runtime Environment" Key: JBIDE-25920 URL: https://issues.jboss.org/browse/JBIDE-25920 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: server Reporter: Aurélien Pupier Fix For: 4.6.0.AM1 see https://github.com/jbosstools/jbosstools-fuse/pull/1348#issuecomment-3816... for reference -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25864) JMX Navigator does not show Local Processes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25864?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-25864. --------------------------------- Verified in devstudio 11.3.0.GA > JMX Navigator does not show Local Processes > ------------------------------------------- > > Key: JBIDE-25864 > URL: https://issues.jboss.org/browse/JBIDE-25864 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.5.3.AM3 > Environment: DevStudio 11.3.0.AM3 > Reporter: Tomáš Sedmík > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.3.Final > > Attachments: local-procceses.png > > > _Local Processes_ in JMX Navigator are empty no matter what. There is no error in _Error Log_. > For Example: > If I create a New Fuse Integration Project and run it as Local Camel Context, I should be able to access the running process via JMX Navigator. Unfortunately, the process is not listed under _Local Processes_. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17838. --------------------------------- > Make discovery-site a Maven module > ---------------------------------- > > Key: JBIDE-17838 > URL: https://issues.jboss.org/browse/JBIDE-17838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central-update > Affects Versions: 4.2.0.Beta3 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.3.Final > > > Currently, the discovery-site is generated under on of the discovery plugin. Since it's a real artifact that we copy, deploy and that depends on several modules, it would probably be easier to maintain the discovery project if we create a dedicated module for the discovery site. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25904) Update fabric8 analytics plugin in Red Hat central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25904?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25904: ------------------------------------ >From screenshot: !Screenshot from 2018-04-16 14-13-21.png|thumbnail! Just saw this today because I wasn't in this channel so didn't get notified. Does this mean to update it IMMEDIATELY or wait until GA next Monday? [~rpdavis] > Update fabric8 analytics plugin in Red Hat central > -------------------------------------------------- > > Key: JBIDE-25904 > URL: https://issues.jboss.org/browse/JBIDE-25904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.3.AM3 > Reporter: Rastislav Wagner > Assignee: Jeff MAURY > Fix For: 4.6.0.AM1 > > Attachments: Screenshot from 2018-04-16 14-13-21.png > > > Nick, can you please update fabric8-analytics plugin to the latest available version ? Update site http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19933: --------------------------------------- Also, since it was us QE that had a problem with this previously, I would like to point out that I haven't encountered this problem in the last year or two - probably mainly because things work differently now. > Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it > ---------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19933. --------------------------------- > Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it > ---------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018