October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26100) base does not compile on JDK9/10

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26100?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26100. --------------------------------- Closing, I was able to build base repo on JDK9 and JDK10. > base does not compile on JDK9/10 > -------------------------------- > > Key: JBIDE-26100 > URL: https://issues.jboss.org/browse/JBIDE-26100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.6.0.Final > > > base does not compile on JDK9-10: the import jdk.internal.dynalink.support.RuntimeContextLinkRequestImpl is not found -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4710: ----------------------------- Attachment: screenshot-2.png > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.x > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png, screenshot-1.png, screenshot-2.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Josef Kopriva commented on JBDS-4710: ------------------------------------- On F29 it still not showing proper contents after page reload. > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.x > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png, screenshot-1.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Josef Kopriva edited comment on JBDS-4710 at 10/12/18 2:13 AM: --------------------------------------------------------------- On F29 it is still not showing proper content after page reload. was (Author: jkopriva): On F29 it still not showing proper contents after page reload. > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.x > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png, screenshot-1.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26441) The server was shutdown forcefully. All processes were terminated.

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26441?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26441: ------------------------------- Fix Version/s: 4.10.x > The server was shutdown forcefully. All processes were terminated. > ------------------------------------------------------------------ > > Key: JBIDE-26441 > URL: https://issues.jboss.org/browse/JBIDE-26441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > jboss data virtualization server 6.3 > Reporter: Rakesh Jain > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.10.x > > > eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26441) The server was shutdown forcefully. All processes were terminated.

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26441?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26441: ------------------------------------ [~rakeshjain1] can you give us more details so that we have a better idea of the problem and work on it. Thanks > The server was shutdown forcefully. All processes were terminated. > ------------------------------------------------------------------ > > Key: JBIDE-26441 > URL: https://issues.jboss.org/browse/JBIDE-26441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > jboss data virtualization server 6.3 > Reporter: Rakesh Jain > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.10.x > > > eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26409) Creating of Launcher project in central throws errors

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26409?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26409: ------------------------------- Fix Version/s: 4.10.x > Creating of Launcher project in central throws errors > ----------------------------------------------------- > > Key: JBIDE-26409 > URL: https://issues.jboss.org/browse/JBIDE-26409 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.9.0.Final > Environment: Fedora 28 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.10.x > > > I got some errors just after launcher project is created: > {code} > Errors occurred during the build. > Errors running builder 'Maven Project Builder' on project 'Thortnail'. > Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0 > Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0 > Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0 > Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0 > {code} > and > {code} > eclipse.buildId=12.9.0.GA-v20180928-1629-B3448 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/odockal/workspace1290GA/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.m2e.core > Error > Wed Oct 03 08:31:55 CEST 2018 > Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0 > org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-war-plugin:3.1.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0 > at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117) > at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47) > at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:181) > at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:286) > at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:244) > at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:168) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408) > at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420) > at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:961) > at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408) > at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:76) > at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:97) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:508) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:501) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:288) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:175) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177) > 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:143) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133) > at org.jboss.tools.common.launcher.ui.wizard.NewLauncherProjectWizardController.createMavenProject(NewLauncherProjectWizardController.java:135) > at org.jboss.tools.common.launcher.ui.wizard.NewLauncherProjectWizardController.createProject(NewLauncherProjectWizardController.java:94) > at org.jboss.tools.common.launcher.ui.wizard.NewLauncherProjectWizardController.run(NewLauncherProjectWizardController.java:63) > at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:3.1.0 > at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:276) > at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:192) > at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:253) > at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103) > ... 34 more > Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from https://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the update interval of redhat-ea-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from/to redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/): The operation was cancelled. > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:422) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:224) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:201) > at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:261) > ... 37 more > Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from https://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the update interval of redhat-ea-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-war-plugin:pom:3.1.0 from/to redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/): The operation was cancelled. > at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:240) > at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:208) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:563) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:481) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:399) > ... 40 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26412) Openshift Itests: create job for testing multiple oc on Jenkins

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26412?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26412: ---------------------------------- Fix Version/s: 4.10.x > Openshift Itests: create job for testing multiple oc on Jenkins > --------------------------------------------------------------- > > Key: JBIDE-26412 > URL: https://issues.jboss.org/browse/JBIDE-26412 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.9.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26441) The server was shutdown forcefully. All processes were terminated.

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26441?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-26441: ------------------------------------- Assignee: Rob Stryker > The server was shutdown forcefully. All processes were terminated. > ------------------------------------------------------------------ > > Key: JBIDE-26441 > URL: https://issues.jboss.org/browse/JBIDE-26441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > jboss data virtualization server 6.3 > Reporter: Rakesh Jain > Assignee: Rob Stryker > Priority: Blocker > > eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26441) The server was shutdown forcefully. All processes were terminated.

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26441?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26441: ---------------------------------- Component/s: server > The server was shutdown forcefully. All processes were terminated. > ------------------------------------------------------------------ > > Key: JBIDE-26441 > URL: https://issues.jboss.org/browse/JBIDE-26441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > jboss data virtualization server 6.3 > Reporter: Rakesh Jain > Priority: Blocker > > eclipse.buildId=11.3.0.GA-v20180413-0714-B2352 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 October 2018