[JBoss JIRA] (JBDS-4087) Mark as invalid Vagrant versions known to be not working
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4087?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4087:
--------------------------------
Summary: Mark as invalid Vagrant versions known to be not working (was: Mars as invalid Vagrant versions known to be not working)
> Mark as invalid Vagrant versions known to be not working
> --------------------------------------------------------
>
> Key: JBDS-4087
> URL: https://issues.jboss.org/browse/JBDS-4087
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
>
> Vagrant version superior to 1.8.4 are known to be non-working, please mark them as invalid during installation of the components isntead of saying that there is a newer version.
> For my part there was no clue on what was the issue, i was based on the latest at the moment 1.8.6.
> When using JBDS, I had a timeout when trying to launch the Container in Server view and the console starting the server was displaying no errors
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22897) ZipException below JarAccess.getContent (thrown in ZipFile.read)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22897?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-22897.
---------------------------------
Resolution: Rejected
This is a perfectly reasonable error message to log for the user to see. It indicates an attempt to read a corrupt jar file. I've reviewed the code and see nothing there to indicate our code is wrong at all.
> ZipException below JarAccess.getContent (thrown in ZipFile.read)
> ----------------------------------------------------------------
>
> Key: JBIDE-22897
> URL: https://issues.jboss.org/browse/JBIDE-22897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Exception occurs when reading C:\Users\d18r6979550\.m2\repository\org\jboss\resteasy\resteasy-client\3.0.14.Final\resteasy-client-3.0.14.Final.jar
> {noformat}
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(null:-2)
> at java.util.zip.ZipFile.access$1400(null:-1)
> at java.util.zip.ZipFile$ZipFileInputStream.read(null:-1)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(null:-1)
> at java.util.zip.InflaterInputStream.read(null:-1)
> at java.io.BufferedInputStream.fill(null:-1)
> at java.io.BufferedInputStream.read1(null:-1)
> at java.io.BufferedInputStream.read(null:-1)
> 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.getChildren(RegularObjectImpl.java:73)
> at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parse(LibraryScanner.java:92)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.doProcess(ClassPathMonitor.java:105)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.process(ClassPathMonitor.java:76)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:362)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:72)
> at org.jboss.tools.cdi.core.CDICoreNature._loadProjectDependencies(CDICoreNature.java:678)
> at org.jboss.tools.cdi.core.CDICoreNature.loadProjectDependenciesFromKBProject(CDICoreNature.java:674)
> at org.jboss.tools.cdi.core.CDICoreNature.loadProjectDependencies(CDICoreNature.java:665)
> at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:167)
> at org.jboss.tools.cdi.core.CDIUtil.enableCDI(CDIUtil.java:149)
> at org.jboss.tools.cdi.internal.core.project.facet.CDIFacetInstallDelegate.execute(CDIFacetInstallDelegate.java:66)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installCDIFacet(CDIProjectConfigurator.java:174)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installDefaultFacets(CDIProjectConfigurator.java:162)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configureInternal(CDIProjectConfigurator.java:108)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configure(CDIProjectConfigurator.java:87)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob$1.doCreateMavenProjects(ImportMavenProjectsJob.java:68)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob.runInWorkspace(ImportMavenProjectsJob.java:77)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> 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.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.12.0.v20160606-1100 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 |
> | org.eclipse.jface.text | 3.11.0.v20160505-1301 | 3.11.0.v20160505-1301 |
> | org.eclipse.m2e.core | 1.6.3.20160209-1446 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.core.ui | 1.6.3.20160209-1446 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.jdt | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.wtp | 1.2.1.20150819-2220 | 1.3.0.20160530-2310 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.navigator | 3.6.100.v20160518-1929 | 3.6.100.v20160518-1929 |
> | org.eclipse.wst.common.project.facet.core | 1.4.300.v201111030423 | 1.4.300.v201111030423 |
> | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.batch.core | 1.8.0.Final-v20160610-0126-B1 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.el.core | 3.8.0.Final-v20160610-1533-B7 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160607-2053 |
> | org.jboss.tools.common.model.ui | 3.8.0.Final-v20160610-1533-B7 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.jst.web | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 |
> | org.jboss.tools.jst.web.ui | 3.8.0.Final-v20160609-2146-B2 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.maven.cdi | 1.7.1.Final-v20160401-1059-B103 | 1.8.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.10.0.22 | 4.6.4.fc24 |
> | MacOSX | 10.11.5 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5729a811e4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22897) ZipException below JarAccess.getContent (thrown in ZipFile.read)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22897?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22897:
--------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.x)
> ZipException below JarAccess.getContent (thrown in ZipFile.read)
> ----------------------------------------------------------------
>
> Key: JBIDE-22897
> URL: https://issues.jboss.org/browse/JBIDE-22897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Exception occurs when reading C:\Users\d18r6979550\.m2\repository\org\jboss\resteasy\resteasy-client\3.0.14.Final\resteasy-client-3.0.14.Final.jar
> {noformat}
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(null:-2)
> at java.util.zip.ZipFile.access$1400(null:-1)
> at java.util.zip.ZipFile$ZipFileInputStream.read(null:-1)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(null:-1)
> at java.util.zip.InflaterInputStream.read(null:-1)
> at java.io.BufferedInputStream.fill(null:-1)
> at java.io.BufferedInputStream.read1(null:-1)
> at java.io.BufferedInputStream.read(null:-1)
> 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.getChildren(RegularObjectImpl.java:73)
> at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parse(LibraryScanner.java:92)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.doProcess(ClassPathMonitor.java:105)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.process(ClassPathMonitor.java:76)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:362)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:72)
> at org.jboss.tools.cdi.core.CDICoreNature._loadProjectDependencies(CDICoreNature.java:678)
> at org.jboss.tools.cdi.core.CDICoreNature.loadProjectDependenciesFromKBProject(CDICoreNature.java:674)
> at org.jboss.tools.cdi.core.CDICoreNature.loadProjectDependencies(CDICoreNature.java:665)
> at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:167)
> at org.jboss.tools.cdi.core.CDIUtil.enableCDI(CDIUtil.java:149)
> at org.jboss.tools.cdi.internal.core.project.facet.CDIFacetInstallDelegate.execute(CDIFacetInstallDelegate.java:66)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installCDIFacet(CDIProjectConfigurator.java:174)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installDefaultFacets(CDIProjectConfigurator.java:162)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configureInternal(CDIProjectConfigurator.java:108)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configure(CDIProjectConfigurator.java:87)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob$1.doCreateMavenProjects(ImportMavenProjectsJob.java:68)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob.runInWorkspace(ImportMavenProjectsJob.java:77)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> 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.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.12.0.v20160606-1100 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 |
> | org.eclipse.jface.text | 3.11.0.v20160505-1301 | 3.11.0.v20160505-1301 |
> | org.eclipse.m2e.core | 1.6.3.20160209-1446 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.core.ui | 1.6.3.20160209-1446 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.jdt | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.wtp | 1.2.1.20150819-2220 | 1.3.0.20160530-2310 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.navigator | 3.6.100.v20160518-1929 | 3.6.100.v20160518-1929 |
> | org.eclipse.wst.common.project.facet.core | 1.4.300.v201111030423 | 1.4.300.v201111030423 |
> | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.batch.core | 1.8.0.Final-v20160610-0126-B1 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.el.core | 3.8.0.Final-v20160610-1533-B7 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160607-2053 |
> | org.jboss.tools.common.model.ui | 3.8.0.Final-v20160610-1533-B7 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.jst.web | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 |
> | org.jboss.tools.jst.web.ui | 3.8.0.Final-v20160609-2146-B2 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.maven.cdi | 1.7.1.Final-v20160401-1059-B103 | 1.8.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.10.0.22 | 4.6.4.fc24 |
> | MacOSX | 10.11.5 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5729a811e4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3813) Using a network path in the target folder causes stuttering
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3813?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3813.
---------------------------------
Resolution: Cannot Reproduce Bug
Cannot replicate with validation for path format check in place.
> Using a network path in the target folder causes stuttering
> -----------------------------------------------------------
>
> Key: JBDS-3813
> URL: https://issues.jboss.org/browse/JBDS-3813
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM2
>
>
> The target folder validator will check (synchronously) if a directory with the given path exists with every change. Using a path such as //domain/folder will trigger a check that takes about a second or two while the UI stops responding.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov edited comment on JBIDE-22803 at 10/6/16 6:29 PM:
-------------------------------------------------------------------
[~jcantrill] [~adietish]
* possibly it is a bug, but anonymous user can't see the version
* definitely changes in restclient are needed. And while playing with Watch manager i found all these things.
* yes, i agree that this logic is in jbt. And there is a restart method in WatchManager.WatchListener. And i was asking about the comment: _// TODO enhance fix to only check project once_ in the restart() method of Watch. What are the cases where watching needs to get restarted?
* ok, it's just a pitty that my searches about version logic were useless. Alexey and Andre both told me that it would be a useful feature. Strangely we didn't know about this design decision. About "'try' to watch projects and fall back" - this is one of the ways i wrote about above, and that i thought was a hack. Please have a look.
was (Author: dbocharov):
* possibly it is a bug, but anonymous user can't see the version
* definitely changes in restclient are needed. And while playing with Watch manager i found all these things.
* yes, i agree that this logic is in jbt. And there is a restart method in WatchManager.WatchListener. And i was asking about the comment: _// TODO enhance fix to only check project once_ in the restart() method of Watch. What are the cases where watching needs to get restarted?
* ok, it's just a pitty that my searches about version logic were useless. Alexey and Andre both told me that it would be a useful feature. Strangely we didn't know about this design decision. About "'try' to watch projects and fall back" - this is one of the ways i wrote about above, and that i thought was a hack. Please have a look.
> Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22803
> URL: https://issues.jboss.org/browse/JBIDE-22803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Labels: explorer, openshift, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png
>
>
> EXEC: create an Openshift project
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> ASSERT: wait for the pod to be available
> EXEC: delete the Openshit project
> EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists)
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> EXEC: expand the nodejs-example node
> ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22816:
------------------------------------------
[~jeffmaury][~bdshadow] given the continous amount of reviews, discussions, help and then my own integration test issues I have to tackle, it's very unlikely that I'll be able to tackle this issue. Anyone willing to take this one over, please? We'll postpone this one to the next milestone otherwise
> Create application from image (or builder) may lead to update being detected
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22816
> URL: https://issues.jboss.org/browse/JBIDE-22816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.4.2.AM2
>
>
> When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4085:
----------------------------------
For example:
{code}
!ENTRY org.eclipse.linuxtools.docker.core 4 0 2016-10-06 14:13:15.493
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.docker.core [343]
Unresolved requirement: Require-Bundle: com.google.guava; bundle-version="15.0.0"
-> Bundle-SymbolicName: com.google.guava; bundle-version="15.0.0.v201403281430"
com.google.guava [1242]
Unresolved requirement: Import-Package: sun.misc; resolution:="optional"
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.linuxtools.docker.core [osgi.identity; type="osgi.bundle"; version:Version="2.1.0.201609081448"; osgi.identity="org.eclipse.linuxtools.docker.core"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; type="osgi.bundle"; version:Version="3.11.1.v20160920-1429"; osgi.identity="org.eclipse.osgi"; singleton:="true"] and jaxb-api [osgi.identity; type="osgi.bundle"; version:Version="2.2.12.b141001_1542"; osgi.identity="jaxb-api"] via two dependency chains.
Chain 1:
org.eclipse.linuxtools.docker.core [osgi.identity; type="osgi.bundle"; version:Version="2.1.0.201609081448"; osgi.identity="org.eclipse.linuxtools.docker.core"; singleton:="true"]
require: (&(osgi.wiring.bundle=org.eclipse.core.runtime)(bundle-version>=3.12.0))
|
provide: osgi.wiring.bundle: org.eclipse.core.runtime
org.eclipse.osgi [osgi.identity; type="osgi.bundle"; version:Version="3.11.1.v20160920-1429"; osgi.identity="org.eclipse.osgi"; singleton:="true"]
Chain 2:
org.eclipse.linuxtools.docker.core [osgi.identity; type="osgi.bundle"; version:Version="2.1.0.201609081448"; osgi.identity="org.eclipse.linuxtools.docker.core"; singleton:="true"]
require: (&(osgi.wiring.bundle=org.glassfish.jersey.media.jersey-media-json-jackson)(bundle-version>=2.14.0))
|
provide: osgi.wiring.bundle; bundle-version:Version="2.22.2"; osgi.wiring.bundle="org.glassfish.jersey.media.jersey-media-json-jackson"
org.glassfish.jersey.media.jersey-media-json-jackson [osgi.identity; type="osgi.bundle"; version:Version="2.22.2"; osgi.identity="org.glassfish.jersey.media.jersey-media-json-jackson"]
import: (&(osgi.wiring.package=org.glassfish.jersey.message.filtering.spi)(&(version>=2.22.0)(!(version>=3.0.0))))
|
export: osgi.wiring.package=org.glassfish.jersey.message.filtering.spi; uses:=javax.xml.bind
org.glassfish.jersey.ext.jersey-entity-filtering [osgi.identity; type="osgi.bundle"; version:Version="2.22.2"; osgi.identity="org.glassfish.jersey.ext.jersey-entity-filtering"]
import: (osgi.wiring.package=javax.xml.bind)
|
export: osgi.wiring.package: javax.xml.bind
jaxb-api [osgi.identity; type="osgi.bundle"; version:Version="2.2.12.b141001_1542"; osgi.identity="jaxb-api"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
... is caused by these two plugins being co-installed:
* /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/plugins/org.eclipse.osgi_3.11.1.v20160920-1429.jar and
* /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.glassfish.jersey.media.jersey-media-json-jackson_2.22.2.jar
> unresolved bundles, slow initial start up
> -----------------------------------------
>
> Key: JBDS-4085
> URL: https://issues.jboss.org/browse/JBDS-4085
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Reporter: Václav Kadlčík
> Attachments: restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log
>
>
> Tested:
> * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
> * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
> rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
> I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
> * "min" in the name means minimal install rh-eclipse46-devstudio
> * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
> * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
> As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
> initial start of rh-eclipse46: 40s
> same as above with rh-eclipse46-devstudio: 120s
> initial start of rh-eclipse46* except devstudio: 50s
> same as above with rh-eclipse46-devstudio: 140s
> Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months