[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22959:
-------------------------------------
Priority: Minor (was: Major)
> Properties: rename Deployment to Replication Controller
> -------------------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22959:
------------------------------------------
As far as I can see JBT currently matches the web-ui. [~jcantrill] do you know where/how the web-ui displays replica sets? I still believe that we should match the web-ui wherever it makes sense.
> Properties: rename Deployment to Replication Controller
> -------------------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22959:
-------------------------------------
Fix Version/s: 4.4.x
> Properties: rename Deployment to Replication Controller
> -------------------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22959:
-------------------------------------
Issue Type: Enhancement (was: Bug)
> Properties: rename Deployment to Replication Controller
> -------------------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22959:
-------------------------------------
Summary: Properties: rename Deployment to Replication Controller (was: Properties: renamte Deployment to Replication Controller)
> Properties: rename Deployment to Replication Controller
> -------------------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, properties
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22959:
-------------------------------------
Labels: openshift_v3 properties (was: openshift_v3)
> Properties: rename Deployment to Replication Controller
> -------------------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, properties
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22963) NPE when creating a html5 project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22963?page=com.atlassian.jira.plugi... ]
Koen Aers reassigned JBIDE-22963:
---------------------------------
Assignee: Koen Aers
> NPE when creating a html5 project
> ---------------------------------
>
> Key: JBIDE-22963
> URL: https://issues.jboss.org/browse/JBIDE-22963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.4.1.Final
>
>
> I get this NPE when I create the HTML5 project from Central:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.lookupHibernateVersion(JPAPostInstallFasetListener.java:222)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.buildConsoleConfiguration(JPAPostInstallFasetListener.java:182)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.handleEvent(JPAPostInstallFasetListener.java:79)
> at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62)
> at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454)
> 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:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:152)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:108)
> 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:112)
> 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.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:830)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.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:112)
> 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.createArchetypeProjects(ProjectConfigurationManager.java:758)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:382)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.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.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:377)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:419)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
> I was using devstudio-10.1.0.AM3-v20160808-1833-B5724-installer-standalone.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22963) NPE when creating a html5 project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22963?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-22963:
------------------------------
Fix Version/s: 4.4.1.Final
> NPE when creating a html5 project
> ---------------------------------
>
> Key: JBIDE-22963
> URL: https://issues.jboss.org/browse/JBIDE-22963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.4.1.Final
>
>
> I get this NPE when I create the HTML5 project from Central:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.lookupHibernateVersion(JPAPostInstallFasetListener.java:222)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.buildConsoleConfiguration(JPAPostInstallFasetListener.java:182)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.handleEvent(JPAPostInstallFasetListener.java:79)
> at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62)
> at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454)
> 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:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:152)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:108)
> 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:112)
> 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.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:830)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.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:112)
> 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.createArchetypeProjects(ProjectConfigurationManager.java:758)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:382)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.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.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:377)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:419)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
> I was using devstudio-10.1.0.AM3-v20160808-1833-B5724-installer-standalone.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22963) NPE when creating a html5 project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22963?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-22963:
------------------------------
Story Points: 8
Sprint: devex #119 August 2016
> NPE when creating a html5 project
> ---------------------------------
>
> Key: JBIDE-22963
> URL: https://issues.jboss.org/browse/JBIDE-22963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.4.1.Final
>
>
> I get this NPE when I create the HTML5 project from Central:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.lookupHibernateVersion(JPAPostInstallFasetListener.java:222)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.buildConsoleConfiguration(JPAPostInstallFasetListener.java:182)
> at org.jboss.tools.hibernate.jpt.core.internal.JPAPostInstallFasetListener.handleEvent(JPAPostInstallFasetListener.java:79)
> at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62)
> at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454)
> 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:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:152)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:108)
> 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:112)
> 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.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:830)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:760)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.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:112)
> 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.createArchetypeProjects(ProjectConfigurationManager.java:758)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:382)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.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.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:377)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:419)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
> I was using devstudio-10.1.0.AM3-v20160808-1833-B5724-installer-standalone.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22882) vagrant-sshfs plugin prevents CDK server adapter from starting
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22882?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-22882:
----------------------------------
Priority: Blocker (was: Major)
> vagrant-sshfs plugin prevents CDK server adapter from starting
> --------------------------------------------------------------
>
> Key: JBIDE-22882
> URL: https://issues.jboss.org/browse/JBIDE-22882
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.0.Final
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.1.AM3
>
>
> This is a follow up issue on JBIDE-22604.
> The problem was fixed in CDK 2.1.0 by removing sshfs setup in the default Vagrant file. The original upstream issue still need to be fixed if we want to enable sshfs setup in the default Vagrant file which is used by devstudio by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months