January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1021) Correct AllWizardsTest suite

by Dominik Hanak (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1021?page=com.atlassian.jira.plugin... ] Dominik Hanak updated JBTIS-1021: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/861 > Correct AllWizardsTest suite > ----------------------------- > > Key: JBTIS-1021 > URL: https://issues.jboss.org/browse/JBTIS-1021 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Dominik Hanak > Assignee: Andrej Podhradsky > > A bunch of tests in this test suite is failing. > They need to be look at and corrected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23020) Integration tests: Have a dedicated OS instance

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23020?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23020: ------------------------------------ There is not a dedicated instance, but cdk 2.3 can run on rhel in central-ci now. We usually start cdk on slave as part of the jenkins job config. CDK3 still doesn't work. > Integration tests: Have a dedicated OS instance > ----------------------------------------------- > > Key: JBIDE-23020 > URL: https://issues.jboss.org/browse/JBIDE-23020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We dont have a dedicated OS instance for the integration tests. > Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. > Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1021) Correct AllWizardsTest suite

by Dominik Hanak (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1021?page=com.atlassian.jira.plugin... ] Dominik Hanak updated JBTIS-1021: --------------------------------- Description: A bunch of tests in this test suite is failing. They need to be look at and corrected. was: A bunch of tests in this test suite is failing. They to be look at and corrected. > Correct AllWizardsTest suite > ----------------------------- > > Key: JBTIS-1021 > URL: https://issues.jboss.org/browse/JBTIS-1021 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Dominik Hanak > Assignee: Andrej Podhradsky > > A bunch of tests in this test suite is failing. > They need to be look at and corrected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1021) Correct AllWizardsTest suite

by Dominik Hanak (JIRA)

Dominik Hanak created JBTIS-1021: ------------------------------------ Summary: Correct AllWizardsTest suite Key: JBTIS-1021 URL: https://issues.jboss.org/browse/JBTIS-1021 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPMN2, QE Affects Versions: 4.4.0.Alpha1 Reporter: Dominik Hanak Assignee: Andrej Podhradsky A bunch of tests in this test suite is failing. They to be look at and corrected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3869) DevSuite Installer should check/warn if Hyper-V is already enabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3869: ------------------------------------- To determine Hyper-V version {code}wmic datafile where name=”c:\\windows\\system32\\vmms.exe” get version{code} > DevSuite Installer should check/warn if Hyper-V is already enabled > ------------------------------------------------------------------ > > Key: JBDS-3869 > URL: https://issues.jboss.org/browse/JBDS-3869 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 10 Pro, 64 bit. > Reporter: Robert Terzi > Assignee: Sudhir Verma > Labels: ui > Fix For: 10.3.0.AM2 > > > The platform installer should check and warn if Hyper-V is already enabled on Windows systems. > Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3933) Platform installer - If the installer is run while (inadvertently) off the network or behind proxy, the error message only indicates an invalid password

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3933?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3933: -------------------------------- Attachment: cannot-access.png > Platform installer - If the installer is run while (inadvertently) off the network or behind proxy, the error message only indicates an invalid password > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3933 > URL: https://issues.jboss.org/browse/JBDS-3933 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Environment: development-suite-10.0.0-GA-20160607-173-bundle-installer.exe > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 10.3.0.AM2 > > Attachments: cannot-access.png, error.png > > > A more informative error message ("network failure", etc.) would be helpful - see the attached screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts

by Jane Murphey (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ] Jane Murphey commented on JBIDE-23766: -------------------------------------- Hitting the ZipException: invalid LOC header (bad signature) org.jboss.tools.common.model... error. Will provide more information shortly. Was able to create a Fuse empty Blueprint project after some time, but could not run it as local camel context. Will attach error and console logs. Had lots of trouble adding and configuring nodes (route editor very flakey, switching location of choice and otherwise nodes back and forth inside the route container) to build the route. > ZipException in CDICoreBuilder when indexing some Camel artifacts > ----------------------------------------------------------------- > > Key: JBIDE-23766 > URL: https://issues.jboss.org/browse/JBIDE-23766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.4.2.Final > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > Attachments: FT_FISprojectBldFail_011917.rtf, FT_blankBlueprintProj.log, FuseToolingInstalledSW.png, blankBlueprintPomError.png, settings.xml > > > it would be nice to provide more information in log such as teh classes in inspection by CDI Core Builder > {noformat} > !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815 > !MESSAGE invalid LOC header (bad signature) > !STACK 0 > java.util.zip.ZipException: invalid LOC header (bad signature) > at java.util.zip.ZipFile.read(Native Method) > at java.util.zip.ZipFile.access$1400(ZipFile.java:60) > at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717) > at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419) > at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at java.io.DataInputStream.readFully(DataInputStream.java:195) > at java.io.DataInputStream.readFully(DataInputStream.java:169) > at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433) > at org.jboss.jandex.Indexer.index(Indexer.java:689) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56) > at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4254) Validate Hyper-V configuration is correct for minishift to work

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4254?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4254: ----------------------------------- Assignee: Denis Golovin > Validate Hyper-V configuration is correct for minishift to work > --------------------------------------------------------------- > > Key: JBDS-4254 > URL: https://issues.jboss.org/browse/JBDS-4254 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Environment: Windows 10 Pro > Reporter: Denis Golovin > Assignee: Denis Golovin > > Installer should check if Hyper-V configured correctly to work with minishift and show warnings/errors. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4255) Check it there is at least one virtual switch available

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4255: ----------------------------------- Summary: Check it there is at least one virtual switch available Key: JBDS-4255 URL: https://issues.jboss.org/browse/JBDS-4255 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Story Components: platform-installer Affects Versions: 10.3.0.AM2 Environment: Windows 10 Pro/Educational/Enterprise Reporter: Denis Golovin Assignee: Denis Golovin There should be at least one virtual switch configured. TBD: Figure out what kind of virtual witch is required for minishift to work. SOme insights are available here https://github.com/minishift/minishift/issues/107#issuecomment-249658360. {quote}The actual code where the hyper-v driver is configured is in https://github.com/jimmidyson/minishift/blob/master/pkg/minikube/cluster/.... You can see the options being passed to the driver. Details on the options are at https://docs.docker.com/machine/drivers/hyper-v/ & https://github.com/docker/machine/blob/master/drivers/hyperv/hyperv.go.{q... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4254) Validate Hyper-V configuration is correct for minishift to work

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4254: ----------------------------------- Summary: Validate Hyper-V configuration is correct for minishift to work Key: JBDS-4254 URL: https://issues.jboss.org/browse/JBDS-4254 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Epic Components: platform-installer Affects Versions: 10.3.0.AM2 Environment: Windows 10 Pro Reporter: Denis Golovin Installer should check if Hyper-V configured correctly to work with minishift and show warnings/errors. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017