|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
Addressing your review points:
I added an example that shows how to provision multiple bundles, a resource processor and a configuration. It adds a second test case to our one class. We could define helpers that define standard deployment package builder configurations to get you started, but as you can see, listing what you need already is pretty straightforward. Maybe we could add something like:
CoreDeploymentPackage.createAll() : DeploymentPackageBuilder -> that contains all the "standard" bundles and configurations (with the same optional exclude list) ?
Quite frankly, I could use a bit of help to replace that SNAPSHOT with a specific version. Never did that. Can you briefly explain how and why?
I agree we can move ManagementAgent to "base". I was pondering about whether we should add these new things (ManagementAgent, CoreDeploymentPackage, etc.) to the existing base bundle, or if we should create a new one. That is why I initially didn't do either yet.