Parameterize runlevel for "deployCollectionXXX" task

[windhamg]

I've run into a situation where I would like to deploy a collection of modules, via the deployCollectionXXX task, but need one of the modules to be deployed at an earlier runlevel than the others (as it loads some external data into a Persistent Data Store, which the other modules subsequently reference). Currently, I get deployment errors due to one of the relying modules referencing the PDS resource before it's created.

Would it be possible to add an optional runlevel parameter to each module in the deploy { ... } block? If not, do you have any suggestions on how to handle this situation?

Thanks in advance!
--Gary

[pjr1060]

Hi Gary - interesting use-case. I think it should be pretty straight forward to support run-levels in the configuration for the collection. I'll take a look and get back to you later today.

P.

[pjr1060]

Hi Gary - it took a little more work than I thought but you can now specify a runlevel on the module declaration in the deployCollection.

Here's the documentation:

http://docs.netkernel.org/book/view/book:org:netkernel:gradle:plugin:book/doc:org:netkernel:gradle:doc:deploy#NetKernel_Runlevel_Option

Please let us know how you get on.

P.

PS Just change version to 1.1.25 to get this, it's in the repo.