[JBoss JIRA] (JBIDE-26409) Creating of Launcher project in central throws errors
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26409?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26409:
---------------------------------------
[~jeffmaury] Seemed to work. I will lower the priority and wil keep open for a while if anyone else will encounter the same error.
> 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-26409) Creating of Launcher project in central throws errors
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26409?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-26409 at 10/3/18 6:22 AM:
----------------------------------------------------------------
[~jeffmaury] Hm... Alright then, I deleted .m2 repository and will report back in couple of hours (as after deleting .m2 repository this will take probably that much time to download all artifacts).
was (Author: odockal):
[~jeffmaury] Hm... Alright then, I deleted .m2 repository and will report back in couple of hours (as deleting .m2 repository this will take probably that much time).
> 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-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project
by Dmitrii Bocharov (Jira)
[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-26330:
-------------------------------------
Story Points: 5
> Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26330
> URL: https://issues.jboss.org/browse/JBIDE-26330
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> steps:
> # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
> # EXEC: import the "hello" maven project into your Eclipse
> # EXEC: create a server adapter and start it
> # ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles...
> # ASSERT: *"openshift"* maven profile is selected
> # EXEC: Restart Eclipse
> # ASSERT: server adapter for project "hello" is *[Stopped, Republish]*
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles...
> Result:
> Project "hello" still has *"openshift"* profile selected
> Expected result:
> Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match
by Dmitrii Bocharov (Jira)
[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24646:
-------------------------------------
Story Points: 5
> Import application: doesnt check if local branch match
> ------------------------------------------------------
>
> Key: JBIDE-24646
> URL: https://issues.jboss.org/browse/JBIDE-24646
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM1
> Reporter: Jan Novak
> Assignee: Dmitrii Bocharov
> Priority: Major
> Labels: import_app, openshift_v3
> Fix For: 4.10.0.AM1
>
>
> Importing project from Openshift
> * use existing repo
> * local repo uses different branch than Openshift
> * remote branch isnt locally fetched
> * import finishes succesfully
> * in local repo is *stil checkouted wrong branch*, without any warnings
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project
by Dmitrii Bocharov (Jira)
[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-26330:
----------------------------------------
Fix Version/s: 4.10.0.AM1
(was: 4.x)
Sprint: devex #156 October 2018
Assignee: Dmitrii Bocharov
> Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26330
> URL: https://issues.jboss.org/browse/JBIDE-26330
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> steps:
> # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
> # EXEC: import the "hello" maven project into your Eclipse
> # EXEC: create a server adapter and start it
> # ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles...
> # ASSERT: *"openshift"* maven profile is selected
> # EXEC: Restart Eclipse
> # ASSERT: server adapter for project "hello" is *[Stopped, Republish]*
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles...
> Result:
> Project "hello" still has *"openshift"* profile selected
> Expected result:
> Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match
by Dmitrii Bocharov (Jira)
[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-24646:
----------------------------------------
Fix Version/s: 4.10.0.AM1
(was: 4.x)
Sprint: devex #156 October 2018
Assignee: Dmitrii Bocharov
> Import application: doesnt check if local branch match
> ------------------------------------------------------
>
> Key: JBIDE-24646
> URL: https://issues.jboss.org/browse/JBIDE-24646
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM1
> Reporter: Jan Novak
> Assignee: Dmitrii Bocharov
> Priority: Major
> Labels: import_app, openshift_v3
> Fix For: 4.10.0.AM1
>
>
> Importing project from Openshift
> * use existing repo
> * local repo uses different branch than Openshift
> * remote branch isnt locally fetched
> * import finishes succesfully
> * in local repo is *stil checkouted wrong branch*, without any warnings
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months