June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22713) IOException in CentralHelper.extractIfNeeded

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22713?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22713: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > IOException in CentralHelper.extractIfNeeded > -------------------------------------------- > > Key: JBIDE-22713 > URL: https://issues.jboss.org/browse/JBIDE-22713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Jeff MAURY > Fix For: 4.5.0.Final > > > The following problem was reported via the automated error reporting: > Message: Unable to open C:\eclipse\plugins\org.jboss.tools.central_2.0.1.Final-v20160401-1059-B103\resources\jbosstools-central-webpage.zip > {noformat} > java.io.IOException: D:\OneDrive\TreinaWeb\Java Básico\JSE\.metadata\.plugins\org.jboss.tools.central\central\bc8a80b\index.html can not be found > at org.jboss.tools.central.internal.CentralHelper.extractIfNeeded(CentralHelper.java:203) > at org.jboss.tools.central.internal.CentralHelper.getCentralPageUrl(CentralHelper.java:122) > at org.jboss.tools.central.internal.CentralHelper.getCentralUrl(CentralHelper.java:60) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$5.run(GettingStartedHtmlPage.java:252) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.1.0.qualifier | > Operating Systems: > | Linux | 3.2.0 | 4.5.7.fc23 | > | MacOSX | 10.10.5 | 10.11.5 | > | Windows | 5.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571659e0e4b055563f...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23595) Integration tests global refactoring: org.jboss.tools.vpe.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23595?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23595: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.vpe.bot.test > ------------------------------------------------------------------ > > Key: JBIDE-23595 > URL: https://issues.jboss.org/browse/JBIDE-23595 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests, vpe > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.vpe.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23402: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > [WATCHER] Explorer: can "Deploy Latest" even if the build failed > ---------------------------------------------------------------- > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM2 > > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. > In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23402: ---------------------------------- Assignee: Jeff MAURY > [WATCHER] Explorer: can "Deploy Latest" even if the build failed > ---------------------------------------------------------------- > > Key: JBIDE-23402 > URL: https://issues.jboss.org/browse/JBIDE-23402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.5.0.AM2 > > Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png > > > When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. > In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21587) Move OpenShift databinding utils to common

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21587?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21587: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Move OpenShift databinding utils to common > ------------------------------------------ > > Key: JBIDE-21587 > URL: https://issues.jboss.org/browse/JBIDE-21587 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common, openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.5.0.Final > > > We have databinding utils in OpenShift that we want to move to commons/base -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23601) Integration tests global refactoring: org.jboss.tools.browsersim.ui.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23601?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23601: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.browsersim.ui.bot.test > ---------------------------------------------------------------------------- > > Key: JBIDE-23601 > URL: https://issues.jboss.org/browse/JBIDE-23601 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: browser, integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.browsersim.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21674: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Enable hierarchical view by default in Project Explorer > ------------------------------------------------------- > > Key: JBIDE-21674 > URL: https://issues.jboss.org/browse/JBIDE-21674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common, upstream > Reporter: Xavier Coulon > Fix For: 4.5.0.AM2 > > > Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects). > After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-21674: ---------------------------------- Assignee: Jeff MAURY > Enable hierarchical view by default in Project Explorer > ------------------------------------------------------- > > Key: JBIDE-21674 > URL: https://issues.jboss.org/browse/JBIDE-21674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common, upstream > Reporter: Xavier Coulon > Assignee: Jeff MAURY > Fix For: 4.5.0.AM2 > > > Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects). > After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23586) Integration tests global refactoring: org.jboss.tools.jst.ui.bot.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23586?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23586: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.jst.ui.bot.test > --------------------------------------------------------------------- > > Key: JBIDE-23586 > URL: https://issues.jboss.org/browse/JBIDE-23586 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jst > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.jst.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23811?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23811: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > 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.5.0.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, 10 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 June 2017