I have created the vRO plugin using model driven archetype.
After that I tried to create some workflow and then imported it in our package folder using below command.
mvn o11n-package:import-package -DserverUrl=user:pass@localhost:8281
I am able to import the workflows in package folder, after that I built the plugin and deployed it in vRO but after deploying was unable to see the Workflow in vRO.
Please find the below pom.xml file:
<plugin>
<groupId>com.vmware.o11n.mojo.pkg</groupId>
<artifactId>maven-o11n-package-plugin</artifactId>
<version>${vco.version}</version>
<extensions>true</extensions>
<configuration>
<packageName>com.sample.example</packageName>
<!-- Set the local path to the *.vmokeystore file used to sign the content -->
<keystoreLocation>${keystoreLocation}</keystoreLocation>
<keystorePassword>${keystorePassword}</keystorePassword>
<includes>
<include>**/Library/vRO Plug-in for Sample/**/*.element_info.xml</include>
</includes>
<packageFileName>o11nplugin-sample-package-${project.version}</packageFileName>
<allowedMask>vef</allowedMask>
<exportVersionHistory>false</exportVersionHistory>
</configuration>
</plugin>
Please find the dunes-meta-inf.xml file:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<comment>127.0.0.1:8230</comment>
<entry key="pkg-description">vRO Plug-in for Sample package</entry>
<entry key="pkg-name">com.sample.example</entry>
<entry key="used-plugins">Sample#0.0.1</entry>
<entry key="pkg-owner">Sample Example</entry>
<entry key="pkg-id">4452345677834623546671713779537818809</entry>
</properties>
Are we missing something in the pom or do we need to do some other configuration?
There is another issue. The vso.xml file defines the content package as following:
<action resource="packages/o11nplugin-example-package-1.0.0-SNAPSHOT.package" type="install-package"/>
But the actual package file embedded in the dar file is named differently:
packages/o11nplugin-SampleExample-package-1.0.0-SNAPSHOT.package
That package names' mismatch is likely the reason for the 'not found' error you age getting.
After checking the logs ,We have found following error message in vRO server log.
2019-05-16 12:31:27.285+0000 [ApplicaitonEventHandler-1] ERROR {} [ModulesFactory] Unable to perform plug-in installation 'Plugin for Sample', reason : (plug-in - Plugin for Sample) Unable to install package 'packages/o11nplugin-sample-package-0.0.1' , reason : (plug-in - Plugin for Sample) Unable to import package resource 'packages/o11nplugin-sample-package-0.0.1' not found ! We have checked the contents of dar file and it has above mentioned file inside it.
This error message is printed when the package resource cannot be opened/found.
Could you share the dar file to take a look? Also, which vRO version is this?
The line 4 of your plug-in's vso.xml file is
<installation mode="${installation.mode}">
It seems there was no property installation.mode defined during the plug-in build procedure. Please define this property (with value either version or always, depending on the desired content installation behavior) somewhere (ie. as a Maven property in pom.xml files of the plug-in, or via a property on the Maven command line you use to build the plug-in) so the Maven can generate correct vso.xml file, and try again to deploy/install the plug-in.
We tried changing the installation-mode to always, but it didn't work. Still it is giving an error "2019-05-17 18:49:05.029+0530 [ApplicaitonEventHandler-1] ERROR {} [ModulesFactory] Unable to perform plug-in installation 'samplealias', reason : (plug-in - samplealias) Unable to install package 'packages/o11nplugin-example-package-1.0.0-SNAPSHOT.package' , reason : (plug-in - samplealias) Unable to import package resource 'packages/o11nplugin-example-package-1.0.0-SNAPSHOT.package' not found !"
We have changed the installation mode through maven command and pom file as well.
There is another issue. The vso.xml file defines the content package as following:
<action resource="packages/o11nplugin-example-package-1.0.0-SNAPSHOT.package" type="install-package"/>
But the actual package file embedded in the dar file is named differently:
packages/o11nplugin-SampleExample-package-1.0.0-SNAPSHOT.package
That package names' mismatch is likely the reason for the 'not found' error you age getting.
Yes llian, there was a difference in name. Also we found out that we have to give complete name in "action resource". Earlier we were not mentioned ".package" in custom module.
Thanks for help. Issue is resolved now
Thanks for the help..
Package/workflow folder is visible now in vRO.