November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23321 at 11/11/16 6:03 AM: -------------------------------------------------------------------- [~psrna] You plan on trying to have an automatic install of minishift? A few argument to counterbalance: * Isnt that somehow duplicating our efforts for a CDK installer? * aren't we adding one more dependecy that we then have to maintain, while in CDK, we have to anyhow and have people that help? I'm not saying that we shouldnt go minishift. I dont know minishift enough. Looking at the minishift description I feel like it isnt that much simpler: It's mostly just the vagrant part that's missing. The other depenencies are there too: KVM/Virtualbox etc. And then you have to duplicate the template install script that we have in CDK (via oc). was (Author: adietish): [~psrna] You plan on trying to have an automatic install of minishift? A few argument to counterbalance: * Isnt that somehow duplicating our efforts for a CDK installer? * aren't we adding one more dependecy that we then have to maintain, while in CDK, we have to anyhow and have people that help. > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.2.Final > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23321: ------------------------------------------ [~psrna] You plan on trying to have an automatic install of minishift? A few argument to counterbalance: * Isnt that somehow duplicating our efforts for a CDK installer? * aren't we adding one more dependecy that we then have to maintain, while in CDK, we have to anyhow and have people that help. > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.2.Final > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central

by Václav Kadlčík (JIRA)

Václav Kadlčík created JBDS-4175: ------------------------------------ Summary: RPM version: NPE after install from Red Hat Central Key: JBDS-4175 URL: https://issues.jboss.org/browse/JBDS-4175 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: rpm Environment: RHEL 7.2 with RHSCL repositories available: * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....) * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...) Reporter: Václav Kadlčík Attachments: sw_to_install.txt, workspace.log I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module"). I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster. Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-973) BPMN2: Delete SWTBot launchers

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-973?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-973. ----------------------------------- pushed to master > BPMN2: Delete SWTBot launchers > ------------------------------ > > Key: JBTIS-973 > URL: https://issues.jboss.org/browse/JBTIS-973 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Jozef Marko > Fix For: 4.4.0.Final > > > tests/org.jboss.tools.bpmn2.ui.bot.test/launcher > - AllEditorTests.launch > - AllWizardTests.launch -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4133: ---------------------------------- Webservices build is now broken and will likely stay that way until Xavier's PR is pushed: {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.26.0:compile (default-compile) on project org.jboss.tools.ws.jaxrs.core: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-webservices_master/sources/plugins/org.jboss.tools.ws.jaxrs.core/src/org/jboss/tools/ws/jaxrs/core/internal/metamodel/search/JaxrsElementsIndexationDelegate.java:[21] [ERROR] import org.apache.lucene.analysis.standard.StandardAnalyzer; [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] The import org.apache.lucene.analysis.standard cannot be resolved [ERROR] /mnt/hudson_workspace/workspace/jbosstools-webservices_master/sources/plugins/org.jboss.tools.ws.jaxrs.core/src/org/jboss/tools/ws/jaxrs/core/internal/metamodel/search/JaxrsElementsIndexationDelegate.java:[64] [ERROR] private final StandardAnalyzer analyzer; [ERROR] ^^^^^^^^^^^^^^^^ [ERROR] StandardAnalyzer cannot be resolved to a type [ERROR] /mnt/hudson_workspace/workspace/jbosstools-webservices_master/sources/plugins/org.jboss.tools.ws.jaxrs.core/src/org/jboss/tools/ws/jaxrs/core/internal/metamodel/search/JaxrsElementsIndexationDelegate.java:[82] [ERROR] analyzer = new StandardAnalyzer(Version.LUCENE_35);{code} > org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4133 > URL: https://issues.jboss.org/browse/JBDS-4133 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, target-platform, webservices > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 10.2.0.GA > > Attachments: image-2016-11-08-19-07-53-492.png, lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, osgi-console-lucene.png, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml > > > I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm. > {code} > !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578 > !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...". > !STACK 0 > java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278) > at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 5 more > {code} > [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4174) Install Vagrant and Virtual box for macOS out of Apple DIsk Image

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4174: ----------------------------------- Summary: Install Vagrant and Virtual box for macOS out of Apple DIsk Image Key: JBDS-4174 URL: https://issues.jboss.org/browse/JBDS-4174 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.AM3 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.2.0.GA Installation can be done in two commands: 1. mounting dmg file as a folder 2. running macOS installer with pkg file name for corresponding application To trigger privilege lifting both commands should be wrapped with osascript command that require administartive account. Consequences are there are going o be two requests for administrator credentials. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3756) Have two progress bars download and installation progress

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3756?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3756: -------------------------------- Sprint: devex #123 November 2016 (was: devex #123 November 2016) > Have two progress bars download and installation progress > --------------------------------------------------------- > > Key: JBDS-3756 > URL: https://issues.jboss.org/browse/JBDS-3756 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Pete Muir > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 10.2.0.GA > > > Most installers have a single progress bar that shows the overall progress, and then text which explains which component is being installed right now. > Update: > After discussion on backlog grooming session it seems reasonable to have two progress bars instead of one. Considering size of downloaded resources and time spend for downloading/installation we might have much longer installation time than now with single progress bar. Instead we can start downloading resources and install them as soon as download is finished. That would let us run installation in sequence and avoid problems with running two MSI installer at the same timed. Also that would save some time and do installation for smaller components while download for big ones is in progress. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4100) Run PR checks for Windows and Mac

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4100?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4100: -------------------------------- Sprint: devex #123 November 2016 (was: devex #123 November 2016) > Run PR checks for Windows and Mac > --------------------------------- > > Key: JBDS-4100 > URL: https://issues.jboss.org/browse/JBDS-4100 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > Attachments: pr-checks.png > > > Now PR's are verified only for Windows > !pr-checks.png! > When Mac build is ready we have to create checks for Mac as well and rename checks to show what platform was used for verification. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3822: -------------------------------- Sprint: devex #123 November 2016 (was: devex #123 November 2016) > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.2.0.GA > > Attachments: devsuite.manifest > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4058) Installer does not validate VAGRANT_HOME when used

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4058?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4058: -------------------------------- Sprint: devex #123 November 2016 (was: devex #123 November 2016) > Installer does not validate VAGRANT_HOME when used > -------------------------------------------------- > > Key: JBDS-4058 > URL: https://issues.jboss.org/browse/JBDS-4058 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > > As per JBDS-3838, we require users with space in their name to use VAGRANT_HOME environment variable. The problem is, the installer will let you proceed without validating the variable contents. > Something like "x:\this definitely has no spaces\" will allow the user to proceed with installation, which inevitably fails. We need to validate if the path stored in the variable is valid, that the selected drive actually exists, and that there are no spaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 November 2016