April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24274) CDK3 server adapter editor: error decoration for "Minishift Location" should be on the left upper corner of text field

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24274?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24274: ---------------------------------------- Assignee: Rob Stryker > CDK3 server adapter editor: error decoration for "Minishift Location" should be on the left upper corner of text field > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24274 > URL: https://issues.jboss.org/browse/JBIDE-24274 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: error-decoration-application-wizard.png, error-decoration-for-minishift-location.png > > > # ASSERT: have a non-executable file ready > # ASSERT: have a cdk3/minishift server adapter > # EXEC: open server editor for your cdk3/minishift adapter > # EXEC: for "Minishift Location" hit "Browse" and choose your non-executable file > # ASSERT: error decoration appears on the top right corner of the text-field > Result: > The error decoration appears as it should, but it's located on the top right corner of the text field and is cut-off by the "Browse" button: > !error-decoration-for-minishift-location.png! > All other UIs in OpenShift have the decorations on the top left corner of the widget (text-field, combo, checkbox, etc.) > !error-decoration-application-wizard.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24273) CDK3 server adapter editor: can save editor even if "Minishif Location" is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24273?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24273: ---------------------------------------- Assignee: Rob Stryker > CDK3 server adapter editor: can save editor even if "Minishif Location" is invalid > ---------------------------------------------------------------------------------- > > Key: JBIDE-24273 > URL: https://issues.jboss.org/browse/JBIDE-24273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > > # ASSERT: have a non-executable file ready > # ASSERT: have a cdk3/minishift server adapter > # EXEC: open server editor for your cdk3/minishift adapter > # EXEC: for "Minishift Location" hit "Browse" and choose your non-executable file > # ASSERT: error decoration appears > # EXEC: hit "Save" > Result: > The server adapter is saved even though the minishift location is erroneous -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24275) CDK3 server adapter wizard: "Minishift Location" has no error-decoration

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24275?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24275: ---------------------------------------- Assignee: Rob Stryker > CDK3 server adapter wizard: "Minishift Location" has no error-decoration > ------------------------------------------------------------------------ > > Key: JBIDE-24275 > URL: https://issues.jboss.org/browse/JBIDE-24275 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: missing-decoration-cdk3-serveradapter-wizard.png > > > # ASSERT: have a non-executable file ready > # EXEC: launch server adapter wizard for "Red Hat Container Development Kit 3" > # EXEC: in "Minishift Location" choose your non-executable file > Result: > The wizard shows the correct error in the title area, but there's no decoration to the text-field "Minishift Location" > !missing-decoration-cdk3-serveradapter-wizard.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24273) CDK3 server adapter editor: can save editor even if "Minishift Location" is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24273?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24273: ------------------------------------- Summary: CDK3 server adapter editor: can save editor even if "Minishift Location" is invalid (was: CDK3 server adapter editor: can save editor even if "Minishif Location" is invalid) > CDK3 server adapter editor: can save editor even if "Minishift Location" is invalid > ----------------------------------------------------------------------------------- > > Key: JBIDE-24273 > URL: https://issues.jboss.org/browse/JBIDE-24273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > > # ASSERT: have a non-executable file ready > # ASSERT: have a cdk3/minishift server adapter > # EXEC: open server editor for your cdk3/minishift adapter > # EXEC: for "Minishift Location" hit "Browse" and choose your non-executable file > # ASSERT: error decoration appears > # EXEC: hit "Save" > Result: > The server adapter is saved even though the minishift location is erroneous -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23811) ZipException in CDICoreBuilder when indexing some Maven artifacts

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23811?page=com.atlassian.jira.plugi... ] Tomáš Sedmík commented on JBIDE-23811: -------------------------------------- [~aurelien.pupier] I hit the same issue on various operating systems (Fedora, Windows, macOS). I tried to create a new Fuse Integration Project - empty, blueprint DSL with Camel version: 2.17.3 with an empty _.m2_ folder. I tested it with JBoss Fuse Tooling 9.2.0.CI-v20170331-0810-B111 {code} eclipse.buildId=10.3.0.GA-v20170218-1636-B94 java.version=1.8.0_111 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.devstudio.core.product -pluginCustomization /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CI/resources/pluginCustomization.ini Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product -pluginCustomization /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CI/resources/pluginCustomization.ini -data /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CI/target/tmp -clean This is a continuation of log file /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CI/target/tmp/.metadata/.bak_3.log Created Time: 2017-04-13 14:10:56.134 org.jboss.tools.common.core Error Thu Apr 13 14:10:56 CEST 2017 invalid LOC header (bad signature) 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) {code} > ZipException in CDICoreBuilder when indexing some Maven artifacts > ----------------------------------------------------------------- > > Key: JBIDE-23811 > URL: https://issues.jboss.org/browse/JBIDE-23811 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Fix For: 4.4.4.Final > > Attachments: org.apache.aries.blueprint.core-1.7.1.jar > > > it would be nice to provide more information in log such as the classes in inspection by CDI Core Builder. > Also if there are some issues with those jars, please report bugs to them. > {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} > {noformat} > !ENTRY org.jboss.tools.common.model 4 0 2017-01-25 16:11:53.722 > !MESSAGE Exception occurs when reading C:\Users\Aurelien Pupier\.m2\repository\org\apache\aries\blueprint\org.apache.aries.blueprint.core\1.7.1\org.apache.aries.blueprint.core-1.7.1.jar > !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(Unknown Source) > at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source) > at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source) > at java.util.zip.InflaterInputStream.read(Unknown Source) > at java.io.BufferedInputStream.fill(Unknown Source) > at java.io.BufferedInputStream.read1(Unknown Source) > at java.io.BufferedInputStream.read(Unknown Source) > at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:235) > at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:266) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:95) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:78) > at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:159) > at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:152) > at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:347) > at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:352) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.readRuntimes(ClassPathMonitor.java:286) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:103) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.jboss.tools.cdi.core.CDICoreBuilder.<init>(CDICoreBuilder.java:101) > at org.jboss.tools.cdi.core.CDICoreNature.load(CDICoreNature.java:420) > at org.jboss.tools.cdi.core.CDICoreNature.resolveStorage(CDICoreNature.java:393) > at org.jboss.tools.cdi.core.CDICoreNature.resolve(CDICoreNature.java:406) > at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:165) > at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:104) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152) > at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374) > at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-962) Fuse - Create a test for Properties view cleaning

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-962?page=com.atlassian.jira.plugin.... ] Dominik Jelinek reassigned JBTIS-962: ------------------------------------- Assignee: Dominik Jelinek (was: Andrej Podhradsky) > Fuse - Create a test for Properties view cleaning > ------------------------------------------------- > > Key: JBTIS-962 > URL: https://issues.jboss.org/browse/JBTIS-962 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Andrej Podhradsky > Assignee: Dominik Jelinek > > Create a test for FUSETOOLS-2184 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1089) Remove TerminalView and use directly Fuse shell manager

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1089?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1089: ------------------------------------------ Set as critical since I want to move some tests to the project fuseide > Remove TerminalView and use directly Fuse shell manager > ------------------------------------------------------- > > Key: JBTIS-1089 > URL: https://issues.jboss.org/browse/JBTIS-1089 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.3.CR1 > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.3.CR1 > > > Please remove the TerminalView and use directly Fuse shell manager. The implementation is a bit confusing since all operations are outside of the Terminal view. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1089) Remove TerminalView and use directly Fuse shell manager

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1089?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1089: ------------------------------------- Priority: Critical (was: Major) > Remove TerminalView and use directly Fuse shell manager > ------------------------------------------------------- > > Key: JBTIS-1089 > URL: https://issues.jboss.org/browse/JBTIS-1089 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.3.CR1 > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.3.CR1 > > > Please remove the TerminalView and use directly Fuse shell manager. The implementation is a bit confusing since all operations are outside of the Terminal view. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-782) Fuse: Add tests for Server Runtime Overview Page

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-782?page=com.atlassian.jira.plugin.... ] Dominik Jelinek reassigned JBTIS-782: ------------------------------------- Assignee: Dominik Jelinek (was: Tomáš Sedmík) > Fuse: Add tests for Server Runtime Overview Page > ------------------------------------------------ > > Key: JBTIS-782 > URL: https://issues.jboss.org/browse/JBTIS-782 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > > see Servers View --> (select a server) --> select Open option in the context menu > also review DeploymentTest - testImmeadiatelyPublishing: > * publishing options are in Server Runtime Overview Page -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1089) Remove TerminalView and use directly Fuse shell manager

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1089: ---------------------------------------- Summary: Remove TerminalView and use directly Fuse shell manager Key: JBTIS-1089 URL: https://issues.jboss.org/browse/JBTIS-1089 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.4.3.CR1 Reporter: Andrej Podhradsky Assignee: Tomáš Sedmík Fix For: 4.4.3.CR1 Please remove the TerminalView and use directly Fuse shell manager. The implementation is a bit confusing since all operations are outside of the Terminal view. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 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 2017