[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.4.3.Final
(was: 4.4.3.AM2)
> 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.4.3.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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) Cannot launch Fuse project
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-23766:
------------------------------------
Summary: Cannot launch Fuse project (was: ZipException in CDICoreBuilder when indexing some Camel artifacts)
> Cannot launch Fuse project
> --------------------------
>
> 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.Final
>
> Attachments: FT_FISprojectBldFail_011917.rtf, FT_blankBlueprintProj.log, FuseToolingInstalledSW.png, blankBlueprintPomError.png, devstudio10.0ISinstalledFTplugins.png, newFuseFISProjectCreateLog.hang, newFuseProjectCreateLog2.hang, 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
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23422:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23811) ZipException in CDICoreBuilder when indexing some Maven artifacts
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBIDE-23811:
---------------------------------------
Summary: 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
{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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23783:
-------------------------------------
Attachment: resized-project-settings-composite.png
> Server adapter editor: Project settings composite is badly layouted
> -------------------------------------------------------------------
>
> Key: JBIDE-23783
> URL: https://issues.jboss.org/browse/JBIDE-23783
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.3.AM2
>
> Attachments: corrected-project-settings-composite.png, project-settings-composite.png, resized-project-settings-composite.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a server adapter defined
> # EXEC: open up the editor for your server adapter
> Result:
> The project settings composite is badly layouted, especially the right border boundaries are not even:
> !project-settings-composite.png!
> # EXEC: maximise the editor
> Result:
> The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes.
> !resized-project-settings-composite.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23783:
-------------------------------------
Attachment: resized-project-settings-composite.png
> Server adapter editor: Project settings composite is badly layouted
> -------------------------------------------------------------------
>
> Key: JBIDE-23783
> URL: https://issues.jboss.org/browse/JBIDE-23783
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.3.AM2
>
> Attachments: corrected-project-settings-composite.png, project-settings-composite.png, resized-project-settings-composite.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a server adapter defined
> # EXEC: open up the editor for your server adapter
> Result:
> The project settings composite is badly layouted, especially the right border boundaries are not even:
> !project-settings-composite.png!
> # EXEC: maximise the editor
> Result:
> The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes.
> !resized-project-settings-composite.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23783:
-------------------------------------
Attachment: (was: resized-project-settings-composite.png)
> Server adapter editor: Project settings composite is badly layouted
> -------------------------------------------------------------------
>
> Key: JBIDE-23783
> URL: https://issues.jboss.org/browse/JBIDE-23783
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.3.AM2
>
> Attachments: corrected-project-settings-composite.png, project-settings-composite.png, resized-project-settings-composite.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a server adapter defined
> # EXEC: open up the editor for your server adapter
> Result:
> The project settings composite is badly layouted, especially the right border boundaries are not even:
> !project-settings-composite.png!
> # EXEC: maximise the editor
> Result:
> The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes.
> !resized-project-settings-composite.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months