|Hot deploy and bundle resolution [message #896814]
||Thu, 19 July 2012 22:04
| Nick Bargnesi
Registered: July 2012
Hi. I have a hopefully straightforward question about bundle resolution, specifically focused on hot deployments.|
I get the concept of repositories, repository types, and bundle lifecycle. Steve Powell and Glyn Normington did a good job of clarifying things in this post, in particular with respect to developing and deploying.
I have a bundle X that depends on packages exported from Y. Bundle Y is a normal dependency that I have in a watched repository. I can hot deploy X as much as I want and things are good. What I really want to do is hot deploy X and Y, i.e., to pickup/. As I understand it, there's no way to accomplish this.
My curiousity comes from when I deploy Virgo host and snap bundles. I can deploy a snap bundle before its host bundle is deployed, and I end up in the same state as if I were to do it in the reverse order. Here's what I get when a host bundle is deployed after its child snap bundle, note the snap bound to path message on line 6:
[2012-07-19 16:59:11.020] fs-watcher <DE0000I> Installing bundle 'host-bundle' version '1.0.0'.
[2012-07-19 16:59:11.031] fs-watcher <DE0001I> Installed bundle 'host-bundle' version '1.0.0'.
[2012-07-19 16:59:11.037] fs-watcher <DE0004I> Starting bundle 'host-bundle' version '1.0.0'.
[2012-07-19 16:59:11.129] start-signalling-2 <WE0000I> Starting web bundle 'host-bundle' version '1.0.0' with context path '/host'.
[2012-07-19 16:59:11.168] start-signalling-2 <SN0000I> Host created for path '/host'
[2012-07-19 16:59:11.200] start-signalling-2 <SN0010I> Snap bound to path '/host/snap'
[2012-07-19 16:59:11.203] start-signalling-2 <WE0001I> Started web bundle 'host-bundle' version '1.0.0' with context path '/host'.
[2012-07-19 16:59:11.204] start-signalling-2 <DE0005I> Started bundle 'host-bundle' version '1.0.0'.
In effect, I can hot deploy parent host bundles, child snap bundles, and application artifacts to pickup/. But if I deploy normal dependencies, I have to use an external or watched repository. Is there any way to get the same effect between hot deploying parent/child bundles with normal dependencies and application artifacts?
Powered by FUDForum
. Page generated in 0.16684 seconds