VMware Cloud Community
nimeshjain
Contributor
Contributor
Jump to solution

Unable to bundle the workflows in the modeldriven archetype in VRO 7.5

Hello All:

   I am using VRO 7.5 and trying to develop a plugin using Model Driven Archetype. The plugin seems to be working but i am unable to package the workflows that i have created for the plugin. On looking into the vso.xml i see that the generated file always have the name of the package as o11nplugin-examples-*  as below.

<installation mode="always">

        <action resource="packages/o11nplugin-example-package-${project.version}" type="install-package"/>

    </installation>

whereas the skeleton code that is generated by the mvn archetype is 

<packageFileName>o11nplugin-test-package-${project.version}</packageFileName>

if i hardcode the value of the package filename to o11nplugin-example-package this seems to be working whereas otherwise my package does not seem to be uploaded in the VRO.

Can you suggest if there is anything in the configuration that i may have missed out or is this a bug in the model driven. For VRO 7.0 that i have used earlier i did not face this issue.

Thanks & Regards,

Nimesh

Tags (1)
1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi Nimesh,

This looks like a bug in the archetype. To mitigate it, follow these steps:

  • generate the plug-in skeleton code from the archetype (as usual)
  • in the generated files, find a file named CustomModule.java. It should be part of the o11nplugin-test-custom sub-module of the generated plug-in code
  • open the file in a text editor
  • towards the end of the file, there should be a line similar to the following:

plugin.setPackages(Collections.singletonList("o11nplugin-example-package-${project.version}.package"));

  • within this line, replace -example- with -test- (or whatever artifact ID you gave during skeleton generation), and save the file
  • recompile the plug-in, and verify that the content of vso.xml file is now correct

View solution in original post

2 Replies
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi Nimesh,

This looks like a bug in the archetype. To mitigate it, follow these steps:

  • generate the plug-in skeleton code from the archetype (as usual)
  • in the generated files, find a file named CustomModule.java. It should be part of the o11nplugin-test-custom sub-module of the generated plug-in code
  • open the file in a text editor
  • towards the end of the file, there should be a line similar to the following:

plugin.setPackages(Collections.singletonList("o11nplugin-example-package-${project.version}.package"));

  • within this line, replace -example- with -test- (or whatever artifact ID you gave during skeleton generation), and save the file
  • recompile the plug-in, and verify that the content of vso.xml file is now correct
nimeshjain
Contributor
Contributor
Jump to solution

Thanks This works. Do you want me to mark this as a bug somewhere so that it can be fixed in the later releases. For now i can go ahead and complete my work. So thanks for this.

0 Kudos