kumartade's Posts

Remote Plugin SDK: navigateTo API related queries

by Enthusiast in vSphere Client SDK Discussions
‎06-29-2021 10:58 PM
1 Kudo
‎06-29-2021 10:58 PM
1 Kudo
Hi, As per the documentation, in remote plugin sdk's app.navigateTo API behavior is different from localplugin SDK API which used to navigate to specified view of a vSphere entity as below: window.... See more...
Hi, As per the documentation, in remote plugin sdk's app.navigateTo API behavior is different from localplugin SDK API which used to navigate to specified view of a vSphere entity as below: window.htmlClientSdk.app.navigateTo({ targetViewId: "vsphere.core.vm.monitor.performance.advancedView", objectId: "urn:vmomi:VirtualMachine:vm-19:f9d74ee2-c9c8-4f33-ad61-68245632fd75"});  But in remote plugin SDK it will either navigate to a vSphere entity without targetViewId only. I had seen the htmlSdk.app.navigateToClientView({  targetViewId: "administration.ceip" }); which will support only one targetViewId:"administration.ceip" as per documentation.  Is there a way to achieve the usecase of navigating to specific view of a native vSphere entity view?
Labels

Unable to make remote plugin rendered removing

by Enthusiast in vSphere Client SDK Discussions
‎05-31-2021 06:14 AM
‎05-31-2021 06:14 AM
Hi, we had decouple the backend and frontend code in the sdk sample. Our aim is to have the UI only running on manifest server and make api calls for data using auxiliary servers. In the process I h... See more...
Hi, we had decouple the backend and frontend code in the sdk sample. Our aim is to have the UI only running on manifest server and make api calls for data using auxiliary servers. In the process I had made changes and every thing is working fine. As part of requirement, we want to get rid of java and artifact generation as .jar. As a first step up I had taken the dist folder and serving them using static http-server (https://github.com/http-party/http-server) and changed context-path/basehref from '/sample-ui' to '/'. This is same case even if we change the application.properties context-path to '/' After that plugin stopped rendering and showing the below error: Refused to apply style from 'https://10.60.6.6/plugins/com.acme.plugin.remote~1.0.0.0~-1202886956/styles.css' because its MIME type ('text/plain') is not a supported stylesheet MIME type, and strict MIME checking is enabled. I'm able to see the application by accessing the remote url. Is this restriction from Plugin iframe? Please suggest.

Remote Plugin: Dynamic extensions feature support for Summary views

by Enthusiast in vSphere Client SDK Discussions
‎03-17-2021 04:18 AM
‎03-17-2021 04:18 AM
Hi Is the Dynamic extensions feature support for vSphere Summary views extension as well? In documentation I could see it is being supported for monitor, configure, menu actions only. Could you pl... See more...
Hi Is the Dynamic extensions feature support for vSphere Summary views extension as well? In documentation I could see it is being supported for monitor, configure, menu actions only. Could you please confirm on summary views as well?   Thanks, Kumar

Re: Plugin Seed for Remote plugin to support Dev and plugin mode

by Enthusiast in vSphere Client SDK Discussions
‎02-24-2020 06:00 AM
‎02-24-2020 06:00 AM
Hi Vladi, Yes we use DevMode and Plugin Mode extensively. Sure, I can provide our plugin rewrite journey as case study. Recently we had rewritten our flex plugin to HTML5 plugin using new ... See more...
Hi Vladi, Yes we use DevMode and Plugin Mode extensively. Sure, I can provide our plugin rewrite journey as case study. Recently we had rewritten our flex plugin to HTML5 plugin using new HTML5 JS API(local) SDK using plugin seed v1.0.0 based on Angular 5 and Clairty v0.11. As part of this effort, we had implemented a REST API layer to cater the UI calls. Due to devmode we were able to de-couple the dependency between plugin(UI) team and backend API team. Hence, both effort went in almost parallel. Plugin team used json-server and implemented the UI and able to write unit testing as well. At the end of subsequent sprint both backend and UI get integrated. Whenever we propose the migration to new framework, the very first question we have been asked by the management is cost and effort estimate which will be always high without proper framework/tooling from VMware. So, partners will stay on the same architecture as it does the job. This is where VMware can focus and provide tooling like plugin seed which gives clear picture for teams to assess and project the effort to the management with confidence. Driving factors for Remote Plugin based Plug-in seed: - Dev Mode for rapid development/debugging - Unit testing/code coverage (CI/CD) - Latest stack (angular 9/Clarity 3.x) - Easy debugging/Fixing UI specific bugs - Partner presence in Cloud based VMware products we all know how much time it took for our customers/partners to move to HTML5 Client which is a great client compared to flash one. Hope this could be avoided in case of remote vs local architecture.:smileygrin: Regards, Kumar

Plugin Seed for Remote plugin to support Dev and plugin mode

by Enthusiast in vSphere Client SDK Discussions
‎01-31-2020 08:54 PM
‎01-31-2020 08:54 PM
Hi, Can you provide Plugin Seed for Remote plugin to support Dev and plugin mode with angular 8 and clarity 2.x as stack? This will help partners to start/think on migration of plugin to late... See more...
Hi, Can you provide Plugin Seed for Remote plugin to support Dev and plugin mode with angular 8 and clarity 2.x as stack? This will help partners to start/think on migration of plugin to latest architecture. Thanks, Kumar

Remote plugin sample plugin compilation errors

by Enthusiast in vSphere Client SDK Discussions
‎01-24-2020 10:51 PM
‎01-24-2020 10:51 PM
Hi Team, I'm trying to build remote plugin sample bundled as part of vsphere-client-sdk-6.7.0.40000-14186396. Following are the outputs for mvn validate C:\Users\kumart\Downloads\vsphere-cli... See more...
Hi Team, I'm trying to build remote plugin sample bundled as part of vsphere-client-sdk-6.7.0.40000-14186396. Following are the outputs for mvn validate C:\Users\kumart\Downloads\vsphere-client-sdk-6.7.0.40000-14186396\html-client-sdk\samples\remote-plugin-sample λ mvn vaidate -e [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 263, column 18 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 174, column 18 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 247, column 18 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-install-plugin is missing. @ line 131, column 18 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] --------------< com.vmware.samples:remote-plugin-sample >--------------- [INFO] Building remote-plugin-sample 6.7.0-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time:  1.805 s [INFO] Finished at: 2020-01-25T12:16:54+05:30 [INFO] ------------------------------------------------------------------------ [ERROR] Unknown lifecycle phase "vaidate". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] org.apache.maven.lifecycle.LifecyclePhaseNotFoundException: Unknown lifecycle phase "vaidate". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy.     at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:248)     at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions (DefaultLifecycleExecutionPlanCalculator.java:217)     at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:126)     at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:144)     at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan (BuilderCommon.java:97)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:111)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke (Method.java:498)     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException Following is the mvn clean install output: C:\Users\kumart\Downloads\vsphere-client-sdk-6.7.0.40000-14186396\html-client-sdk\samples\remote-plugin-sample λ mvn clean install -e [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 263, column 18 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 174, column 18 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 247, column 18 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-install-plugin is missing. @ line 131, column 18 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] --------------< com.vmware.samples:remote-plugin-sample >--------------- [INFO] Building remote-plugin-sample 6.7.0-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [WARNING] The POM for com.vmware.vim25:vim25:jar:6.7.0 is missing, no dependency information available [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time:  6.869 s [INFO] Finished at: 2020-01-25T12:18:59+05:30 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project remote-plugin-sample: Could not resolve dependencies for project com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project remote-plugin-sample: Could not resolve dependencies for project com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:269)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke (Method.java:498)     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:209)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke (Method.java:498)     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced     at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:357)     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:202)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke (Method.java:498)     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:424)     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)     at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:340)     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:202)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke (Method.java:498)     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced     at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException (DefaultUpdateCheckManager.java:218)     at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact (DefaultUpdateCheckManager.java:193)     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads (DefaultArtifactResolver.java:559)     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads (DefaultArtifactResolver.java:483)     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:401)     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)     at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:340)     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:202)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke (Method.java:498)     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException I'm using maven 3.6.3

How to specify an action extension to open Modal without title and Close button in Plugin.xml

by Enthusiast in vSphere Client SDK Discussions
‎12-02-2019 02:44 AM
‎12-02-2019 02:44 AM
Hi Team, Im trying to define and action extension without title and close button on plugin.xml by not specifying the dialogTitle tag. But it is adding padding and close button(highlighted in ... See more...
Hi Team, Im trying to define and action extension without title and close button on plugin.xml by not specifying the dialogTitle tag. But it is adding padding and close button(highlighted in red color) as shown below: Result: Expectation: Sample extension code Snippet: <extension id="com.acme.myhtmlplugin.datastore.provisioning.actions">         <extendedPoint>vise.actions.sets</extendedPoint>         <object>             <actions>                 <com.vmware.actionsfw.ActionSpec>                     <uid>com.acme.myhtmlplugin.provisionDatastore</uid>                     <label>#{DatastoreProvision.action.label}</label>                     <delegate>                         <className>com.vmware.vsphere.client.HtmlPluginModalAction</className>                         <object>                             <root>                                 <actionUrl>/ui/myhtmlplugin/index.html?view=datastore-provisioning</actionUrl> //No DialogTitle                                 <dialogSize>1152,455</dialogSize>                             </root>                         </object>                     </delegate>                 </com.vmware.actionsfw.ActionSpec>             </actions>         </object>         <metadata>             <objectType>Datacenter,ClusterComputeResource,HostSystem</objectType>         </metadata>     </extension> I could achieve the desired behavior using API programmatically by passing title=null and closable=false in modal config. How to achieve the same thing in plugin.xml ? SDK Details: vSphere SDK: using vSphere New JS 6.5U2 SDK. Thanks, Kumar

Re:Global refresh support on vSphere entity Summary portlet

by Enthusiast in vSphere Client SDK Discussions
‎11-26-2019 12:07 AM
‎11-26-2019 12:07 AM
There is a bug in our code. We had corrected and its working as expected. Thanks for the reply.

Global refresh support on vSphere entity Summary portlet

by Enthusiast in vSphere Client SDK Discussions
‎11-25-2019 05:35 AM
‎11-25-2019 05:35 AM
Hi, We are using new JS APIs SDK(local) of vSphere 6.5U2 SDK for our plugin. We had implemented two portlets on datastore object. But global refresh is not working as it is working on global v... See more...
Hi, We are using new JS APIs SDK(local) of vSphere 6.5U2 SDK for our plugin. We had implemented two portlets on datastore object. But global refresh is not working as it is working on global views. We are going through our implementation. But no clue what's wrong. Can some one from VMware team confirm the following query: Is Global refresh supported vSphere entity(say Datastore) Summary portlet is supported? Are there any limitations? Regards, Kumar

Plugin seed for remote plugin ?

by Enthusiast in vSphere Client SDK Discussions
‎11-15-2019 12:08 AM
‎11-15-2019 12:08 AM
Hi Is it possible to provide a plug-in seed for remote plugin which supports devmode and plugin mode? Thanks, Kumar

Re: plugin seed 1.0.0 released

by Enthusiast in vSphere Client SDK Discussions
‎09-06-2019 09:06 AM
‎09-06-2019 09:06 AM
Globally i installed Node 6.13.0 and npm 5.3.0. I had done the npm cache clean up as well. I'm getting the following error : C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui λ ng serve ... See more...
Globally i installed Node 6.13.0 and npm 5.3.0. I had done the npm cache clean up as well. I'm getting the following error : C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui λ ng serve Schema validation failed with the following errors:   Data path "" should NOT have additional properties(project). Error: Schema validation failed with the following errors:   Data path "" should NOT have additional properties(project).     at BaseException (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\@angular-devkit\core\src\exception\exception.js:12:9)     at SchemaValidationException (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\@angular-devkit\core\src\json\schema\registry.js:25:9)     at MergeMapSubscriber._registry.compile.pipe.operators_1.concatMap.validatorResult [as project] (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\@angular-devkit\core\src\workspace\workspace.js:173:42)     at MergeMapSubscriber._tryNext (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\rxjs\internal\operators\mergeMap.js:65:27)     at MergeMapSubscriber._next (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\rxjs\internal\operators\mergeMap.js:55:18)     at MergeMapSubscriber.Subscriber.next (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\rxjs\internal\Subscriber.js:64:18)     at MergeMapSubscriber.notifyNext (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\rxjs\internal\operators\mergeMap.js:84:26)     at InnerSubscriber._next (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\rxjs\internal\InnerSubscriber.js:25:21)     at InnerSubscriber.Subscriber.next (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\rxjs\internal\Subscriber.js:64:18)     at MapSubscriber._next (C:\Users\kumart\Downloads\plugin-seed-1.0.0\seed-ui\node_modules\rxjs\internal\operators\map.js:52:26) Here is the ng -v output at project home λ ng -v Angular CLI: 6.0.8 Node: 6.13.0 OS: win32 x64 Angular: 6.0.9 ... animations, common, compiler, compiler-cli, core, forms ... http, platform-browser, platform-browser-dynamic ... platform-server, router Package                           Version ----------------------------------------------------------- @angular-devkit/architect         0.6.8 @angular-devkit/build-angular     0.6.8 @angular-devkit/build-optimizer   0.6.8 @angular-devkit/core              0.6.8 @angular-devkit/schematics        0.6.8 @angular/cli                      6.0.8 @angular/tsc-wrapped              4.4.6 @ngtools/webpack                  6.0.8 @schematics/angular               0.6.8 @schematics/update                0.6.8 rxjs                              6.2.2 typescript                        2.7.2 webpack                           4.8.3 λ ng -v      _                      _                 ____ _     ___    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | | /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|                |___/ Angular CLI: 6.0.8Node: 6.13.0OS: win32 x64Angular: 6.0.9... animations, common, compiler, compiler-cli, core, forms... http, platform-browser, platform-browser-dynamic... platform-server, router Package                           Version-----------------------------------------------------------@angular-devkit/architect         0.6.8@angular-devkit/build-angular     0.6.8@angular-devkit/build-optimizer   0.6.8@angular-devkit/core              0.6.8@angular-devkit/schematics        0.6.8@angular/cli                      6.0.8@angular/tsc-wrapped              4.4.6@ngtools/webpack                  6.0.8@schematics/angular               0.6.8@schematics/update                0.6.8rxjs                              6.2.2typescript                        2.7.2webpack                           4.8.3
package.json.zip

Re: plugin seed 1.0.0 released

by Enthusiast in vSphere Client SDK Discussions
‎09-03-2019 07:21 AM
‎09-03-2019 07:21 AM
Please provide a plugin seed with latest angular(8.x) and clarity(2.x) which supports dev mode and unit test for local plugin. This will help many vendors to use latest JS APIs with new stack.

Re:How to Filter Property Constraint in HTML5 Plugin Implementation

by Enthusiast in vSphere Client SDK Discussions
‎03-28-2019 07:39 AM
1 Kudo
‎03-28-2019 07:39 AM
1 Kudo
Thanks Vladi. We are able to resolve the issue and property constraint is working as expected.

Re:How to Filter Property Constraint in HTML5 Plugin Implementation

by Enthusiast in vSphere Client SDK Discussions
‎03-20-2019 10:25 PM
‎03-20-2019 10:25 PM
Thanks Vladi for the confirmation. I understand the concerns and limitations here. We though it would be some simple mistake like SummaryViews Extension Height &amp; Width of Portlet is not Refle... See more...
Thanks Vladi for the confirmation. I understand the concerns and limitations here. We though it would be some simple mistake like SummaryViews Extension Height &amp; Width of Portlet is not Reflecting in Plugin Mode We got a suggestion from one of the community user like "<Boolean>true</Boolean> instead of <String>true</String>". Hence, we assumed this would be simple error and provided extension snippet. The adapter is being called and we can see the log statement of adapter in vSphere client log. We will provide the logs and psuedo code of property adapter  where the adapter is being called. If feasible to reproduce, we will provide a sample as well Thanks, Kumar T.

Re:How to Filter Property Constraint in HTML5 Plugin Implementation

by Enthusiast in vSphere Client SDK Discussions
‎03-20-2019 07:10 AM
‎03-20-2019 07:10 AM
Hi Martin, Sorry to say this. We don't have ready sample to share. This is pretty straight forward case to code by yourselves and verify. Please provide us a solution/workaround for this. ... See more...
Hi Martin, Sorry to say this. We don't have ready sample to share. This is pretty straight forward case to code by yourselves and verify. Please provide us a solution/workaround for this. If this is a bug we need to know the effected vSphere Client versions. Regards, Kumar T.

Re:How to Filter Property Constraint in HTML5 Plugin Implementation

by Enthusiast in vSphere Client SDK Discussions
‎03-19-2019 11:35 PM
‎03-19-2019 11:35 PM
Hi Martin, Yes. The action/summaryPortlets are working without custom Property Constraint. But if I use the custom property constraint as shown below it is not working. <com.vmware.data.que... See more...
Hi Martin, Yes. The action/summaryPortlets are working without custom Property Constraint. But if I use the custom property constraint as shown below it is not working. <com.vmware.data.query.PropertyConstraint>      <propertyName>sampleDatastoreProperty</propertyName>      <comparator>EQUALS</comparator>      <comparableValue>           <Boolean>true</Boolean>       </comparableValue> </com.vmware.data.query.PropertyConstraint> (or) <com.vmware.data.query.PropertyConstraint>      <propertyName>sampleDatastoreProperty</propertyName>      <comparator>EQUALS</comparator>      <comparableValue>           <String>true</String>       </comparableValue> </com.vmware.data.query.PropertyConstraint> and it is also working with the vSphere native property as a constraint as well. <com.vmware.data.query.PropertyConstraint>    <propertyName>summary.type</propertyName>       <comparator>EQUALS</comparator>       <comparableValue>            <String>VMFS</String>        </comparableValue> </com.vmware.data.query.PropertyConstraint> We are following vSphere SDK only vSphere 6.5U2: Online Documentation - vSphere Client SDK Developer Guide - VMware {code} VSphere 6.7 SDK: Online Documentation - Developing Local Plug-ins with the vSphere Client SDK - VMware {code} I don't think VMWare had provided a detailed documentation for latest release also. Some of the available documentation needs to be updated, one documentation update missing example is SummaryViews Extension Height &amp; Width of Portlet is not Reflecting in Plugin Mode  query. Does VMWare provided any other documentation other than the above one???? If so please share us. NOTE: All these constraints(custom property/vmware property/both) are used to work in flex client with flex SDK. Regards, Kumar T.

Re:How to Filter Property Constraint in HTML5 Plugin Implementation

by Enthusiast in vSphere Client SDK Discussions
‎03-19-2019 09:41 AM
‎03-19-2019 09:41 AM
We are waiting for the solution here. Please look into this.

Re:How to Filter Property Constraint in HTML5 Plugin Implementation

by Enthusiast in vSphere Client SDK Discussions
‎03-16-2019 06:12 AM
‎03-16-2019 06:12 AM
We had verified with the suggested type. Still it is not working. Please check out once. We had tested on vSphere Client: 6.5U2

Re: Need help in Plugin Extension Version specification

by Enthusiast in vSphere Client SDK Discussions
‎03-12-2019 06:31 AM
‎03-12-2019 06:31 AM
Thanks for the inputs lokesh,

Re: Need help in Plugin Extension Version specification

by Enthusiast in vSphere Client SDK Discussions
‎03-12-2019 01:36 AM
‎03-12-2019 01:36 AM
Thanks for the detailed info on plugin registration internals. I have few queries: 1. Currently, to update our plugin existing plugin, we call unregister/remove-plugin and then re-registe... See more...
Thanks for the detailed info on plugin registration internals. I have few queries: 1. Currently, to update our plugin existing plugin, we call unregister/remove-plugin and then re-register plugin with new version. Is this recommended way? What is the recommended approach? 2. Every time we update a plugin we see multiple plugin folders in vc_packages. we have to delete the plugin folders manually as clean-up process. Can we not have neater way of doing this by using VMware provided mechanism to have smooth upgrade experience? 3. Does Version number A.B.C.D have any min or max integer range?