[JBoss JIRA] (JBIDE-20084) Import of jboss-sandbox-quickstarts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20084?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-20084:
-----------------------------------
Fix Version/s: 4.3.0.Beta2
> Import of jboss-sandbox-quickstarts
> -----------------------------------
>
> Key: JBIDE-20084
> URL: https://issues.jboss.org/browse/JBIDE-20084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Fix For: 4.3.0.Beta2
>
>
> I tried to import jboss-sandbox-quickstarts (from https://github.com/jboss-developer/jboss-sandbox-quickstarts.git) and I found following issues with it
> - it takes quite a long time (app 3 and a half minutes to import 9 projects
> - during import it seems to be "stuck" for a while and the following exception is logged
> {code}
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> 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:176)
> 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:950)
> 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: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$4.run(ProjectConfigurationManager.java:521)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:26)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.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.enableMavenNature(ProjectConfigurationManager.java:518)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator.configure(MavenProjectConfigurator.java:44)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:236)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:93)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> 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:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 35 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 41 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 44 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 47 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20084) Import of jboss-sandbox-quickstarts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20084?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-20084:
--------------------------------------
Assignee: Mickael Istria
> Import of jboss-sandbox-quickstarts
> -----------------------------------
>
> Key: JBIDE-20084
> URL: https://issues.jboss.org/browse/JBIDE-20084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta2
>
>
> I tried to import jboss-sandbox-quickstarts (from https://github.com/jboss-developer/jboss-sandbox-quickstarts.git) and I found following issues with it
> - it takes quite a long time (app 3 and a half minutes to import 9 projects
> - during import it seems to be "stuck" for a while and the following exception is logged
> {code}
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> 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:176)
> 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:950)
> 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: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$4.run(ProjectConfigurationManager.java:521)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:26)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.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.enableMavenNature(ProjectConfigurationManager.java:518)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator.configure(MavenProjectConfigurator.java:44)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:236)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:93)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> 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:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 35 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 41 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 44 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 47 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12144) EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12144?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-12144:
----------------------------------
Comment: was deleted
(was: Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.)
> EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-12144
> URL: https://issues.jboss.org/browse/JBIDE-12144
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: cleanup
> Fix For: LATER
>
>
> EgitUtils#push throws an exception if the push failed because of ex. "non fastforward push".
> {code}
> private static PushOperationResult push(Repository repository, RemoteConfig remoteConfig, boolean force, IProgressMonitor monitor) throws CoreException {
> ...
> PushOperationResult pushResult = op.getOperationResult();
> if (hasFailedEntries(pushResult)) {
> throw new CoreException(
> EGitCoreActivator.createErrorStatus(
> NLS.bind("Could not push repository {0}: {1}",
> repository.toString(), getErrors(pushResult))
> , null));
> }
> return pushResult;
> {code}
> EGit is not throwing an exception in this case. You simply get the failure in the PushResult object you'll have to look at.
> EGitUtils#push is thus changing the API semantics of EGit and it shouldn't.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12118) Port forwarding: more specific auth error description
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-12118:
---------------------------------------
Fixed title. This is not related to Tail files dialog any more. But it is still relevant to port forwarding, because currently there is even no stack trace for exception, altough there is a description to check error log for more info.
> Port forwarding: more specific auth error description
> -----------------------------------------------------
>
> Key: JBIDE-12118
> URL: https://issues.jboss.org/browse/JBIDE-12118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Priority: Minor
> Labels: port_forwarding_wizard
> Fix For: LATER
>
> Attachments: port.png, tail.png
>
>
> Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences.
> Current state:
> * Port forwarding, environment variables
> !port.png|thumbnail!
> * Tail files
> !tail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12118) Port forwarding: more specific auth error description
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-12118:
----------------------------------
Summary: Port forwarding: more specific auth error description (was: Port forwarding, Tail files wizard: more specific auth error description)
> Port forwarding: more specific auth error description
> -----------------------------------------------------
>
> Key: JBIDE-12118
> URL: https://issues.jboss.org/browse/JBIDE-12118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Priority: Minor
> Labels: port_forwarding_wizard
> Fix For: LATER
>
> Attachments: port.png, tail.png
>
>
> Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences.
> Current state:
> * Port forwarding, environment variables
> !port.png|thumbnail!
> * Tail files
> !tail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12118) Port forwarding: more specific auth error description
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-12118:
----------------------------------
Comment: was deleted
(was: Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.)
> Port forwarding: more specific auth error description
> -----------------------------------------------------
>
> Key: JBIDE-12118
> URL: https://issues.jboss.org/browse/JBIDE-12118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Priority: Minor
> Labels: port_forwarding_wizard
> Fix For: LATER
>
> Attachments: port.png, tail.png
>
>
> Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences.
> Current state:
> * Port forwarding, environment variables
> !port.png|thumbnail!
> * Tail files
> !tail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12116) Port forwarding wizard: Cannot cancel Verifying SSH session job's dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12116?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-12116.
---------------------------------
Fix Version/s: 4.3.0.Beta1
(was: LATER)
Resolution: Out of Date
Resolved as out of dated because there is no such dialog at the moment. It was removed and there is only background job to verify SSH session which is stoppable.
> Port forwarding wizard: Cannot cancel Verifying SSH session job's dialog
> ------------------------------------------------------------------------
>
> Key: JBIDE-12116
> URL: https://issues.jboss.org/browse/JBIDE-12116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Lucia Jelinkova
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
> Attachments: dialog.jpg
>
>
> When the Port forwarding is invoked from Openshift Explorer for the first time a job is triggered (Verifying SSH session to retrieve Application's ports...) and a dialog is displayed. User can run the job on backgroud, show details and cancel the job. However, when Cancel is pressed the Port forwarding dialog is shown anyway.
> !dialog.jpg!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-12116) Port forwarding wizard: Cannot cancel Verifying SSH session job's dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12116?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-12116:
----------------------------------
Comment: was deleted
(was: Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.)
> Port forwarding wizard: Cannot cancel Verifying SSH session job's dialog
> ------------------------------------------------------------------------
>
> Key: JBIDE-12116
> URL: https://issues.jboss.org/browse/JBIDE-12116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Lucia Jelinkova
> Priority: Minor
> Fix For: LATER
>
> Attachments: dialog.jpg
>
>
> When the Port forwarding is invoked from Openshift Explorer for the first time a job is triggered (Verifying SSH session to retrieve Application's ports...) and a dialog is displayed. User can run the job on backgroud, show details and cancel the job. However, when Cancel is pressed the Port forwarding dialog is shown anyway.
> !dialog.jpg!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20116) Wrong IP address used when opening in web browser via livereload
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20116?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-20116:
---------------------------------------
This issue related to JBIDE-20107 which did not fix the problem when the app server listens on another IP address
> Wrong IP address used when opening in web browser via livereload
> ----------------------------------------------------------------
>
> Key: JBIDE-20116
> URL: https://issues.jboss.org/browse/JBIDE-20116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Beta2
>
>
> If the application server runs on another machine or virtual machine (eg, a Docker container), opening the deployed application using LiveReload will use the remote address with the proxy port instead of the local address with the proxy port, resulting in the browser being unable to connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months