[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 commented on JBIDE-26409:
------------------------------------
I think this is a Maven/network issue. Can you delete your $HOME/.m2/repository and test again ?
> 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: Critical
>
> 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, 6 months
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26311:
-------------------------------
Sprint: devex #155 September 2018, devex #156 October 2018 (was: devex #155 September 2018)
> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Major
> Labels: regression
> Fix For: 4.9.0.Final
>
> Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25000:
-------------------------------
Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.Final
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26160:
-------------------------------
Sprint: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018 (was: devex #154 September 2018, devex #155 September 2018)
> Server Adapter: erroneously stays in [Debugging] when you kill the pod
> ----------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Priority: Major
> Labels: server_adapter
> Fix For: 4.9.0.Final
>
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBIDE-26232) Implement CDK support
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26232?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26232:
-------------------------------
Sprint: devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018 (was: devex #153 August 2018, devex #154 September 2018, devex #155 September 2018)
> Implement CDK support
> ---------------------
>
> Key: JBIDE-26232
> URL: https://issues.jboss.org/browse/JBIDE-26232
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-server-protocol
> Affects Versions: 4.9.0.AM1
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.x
>
>
> In addition to upstream CDK, we should support Red Hat CDK supports in RST as well
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months