Hi all, with provisioning in place in I know some people, like me, are struggeling with setting up a nice development environment. We have some tools in place, but I feel we can do better. Here are just some thought ideas and things I have encountered sofar. I'd really like to hear your feedback and ideas.
1) AMS boostrap One of the first things you want to do is setting up an AMS with the Amdatu Platform ready to deploy. To do so you need all processors, bundles and configurations uploaded, associated into features, and distributions. You can do it by hand using webui or create a client to do so. The former gets tiring pretty fast, so I've seen people creating shell scripts, amdatu-maven-plugin import/export models, ace-client based importers Drawback is that everybody is creating and maintaining their own populatiosn/solutions, having to update/upgrade/debug them every time something changes etc. Could we come up with a generic workable solution of most common cases? I want to say "Use the Amdatu Web feature [1,2)", but obviously "Exclude the JSP support". IMHO that should be supported in a way you can automate it as well as do in an eclipse kind of UI dialog. It could be a way to declarative define features/profiles you find in pax/p2/eclipse. I think it would not be far off from the current export/import of artifacts, features and their associations using resolvable uris and common handlers (eg. http/mvn). 2) Development cycle Once you have a populated AMS the next thing a developer wants to do is setting up an efficient development cycle. Our maven-plugin brings some relief but there are some issues here. Eg. the plugin has some timestamp support, but when developing the list of artifacts in the webui quickly become unmanageable. Should we drop and create here? Or find a way to trigger updates with an in place file? This is even more challenging for non-bundle artifacts as the AMS does not support auto-version update on these like it does on bundles. So you could still use the timestamping on files here, but you must then register is under a new name an update the associations with the feature to point to the new configuration artifact. Again, versioning support and/or in place updates would probably make life a lot easier.. Eg. What if we created some kind of (optional) "maven-repository-connector" for artifacts that would sit in the AMS and manage the client artifacts based on observing the repository? It could use the standard versions snapshot logic to (periodically) check for updates. This could also support versioning on non-bundle artifacts (like) config and bridge it to the ACE model that does not support it. Thoughts.. :) I'd love to get some input and ideas. grz Bram _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
