|
||||||||
|
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
To start with the last one: I'm in favor of supporting only one mechanism: the new one. Our release notes currently state that support for File Install and related plugins will be removed for 1.0.0, and this mechanism is much closer to the provisioning we use in production. Of course we will need some time to rewrite the existing tests, so we can't throw out the current mechanism right away, but all new tests should be written using the new mechanism. So I would be in favor of adding some new "base" bundle instead of adding it to the old one.
Related to that, I don't see a need for having test classes that can switch provisioning on and off.
<modularity-hat-on>Providing everybody a set of base bundles and not making them thing about the ones they really need is convenient, but it also has a downside. First of all, probably most tests will run against more bundles than they actually need and we run the risk of not testing different subsets of platform and subproject bundles. As far as I'm concerned, I don't want this platform to end up like Spring in the sense that if you need one module, you need the whole platform because everything depends on everything.</modularity-hat-off>
About releasing the snapshot, can you release that bundle based on the current ACE trunk?