[rtjeffe]

I’ve got a question about the smart deployment feature of ME. I’m wondering how “far down” the dependency chain does the smart deployment deploy. I currently have a setup with the following chain of dependencies.

CactusWeb->TestCases->Business1->Business2

I have createad a WebProject and configured it to run as a cactus test harness. I have then put all my test cases in to a Java Project named “TestCases”. TestCases tests classes in “Business1”. All this seems to be deployed just fine. The issue is if Business1 depends on Business2 or any other external Jars such as Hibernate then everything blows up.

Does the smart deployment feature go down the full chain of dependencies? If so is there something I’m missing on why this isn’t working.

Thanks,
Rob

[Scott Anderson]

Rob,

Does the smart deployment feature go down the full chain of dependencies?

No, it specifically does not. We decided that automatically deploying the full closure of all preferenced projects and libraries was a little too “over the top”. As a result, we’ll deploy any Java projects and external libraries that are directly referenced dependencies of your web project. But that’s where it stops. In your case, you should be able to get what you want by adding your two business projects to the dependency list for CactusWeb.

[rtjeffe]

So basically what you are saying is that the usage chain would stay the same in my code, but I would make the web project reference directly all projects and external Jars that are ever used.

I guess its ugly from a academic view but easy from a development view.

Thanks,
Rob

[Scott Anderson]

Rob,

I guess its ugly from a academic view but easy from a development view.

I’d rather call it “understandable” than ugly, but that’s the gist of it. Otherwise we’d have to hang around and answer questions like “I just want to deploy my web app and all these other projects that I only use for testing are always deployed to my server. How can I stop that?” 😉

[Author]

Posts