Hello Ryan, Thanks for the kind words!
The "manual process" you refer to is probably the Web UI. There have been many discussions about that. It seems everybody wants a different user interface to talk to ACE (interactively or programmatically). You know we also have a REST API nowadays that you can talk to. In fact, Bram and I have been toying around with some ideas for a "console/shell" based interface as well, as that is probably an easy way to automate deployments. To answer your question, I think it would be fairly easy to make a simply extension that imports Karaf features, or any other way of defining dependencies. I know that for a project I'm doing at my company, that uses ACE, we have written tools that take a "bndrun" file as the input to automate deployment. In short, I think we already provide quite a few hooks that would allow you to leverage that, and we would love to accept some patches in that area from people that use Karaf (or other systems). Greetings, Marcel On Jun 17, 2013, at 22:59 PM, Ryan Moquin <[email protected]> wrote: > Awesome job guys. I downloaded it and looked over the docs. It looked > getting things into Ace is still a manual process and duplicates work done > with karaf features and things like that... is there a workflow that can be > used with ace that flows better with other ways of making sure dependencies > are handled and grouped? Excited to tryout the new release and see of it > will help me figure out a good robust deployment strategy. > > Thanks, > Ryan > On Jun 17, 2013 3:41 AM, "Marcel Offermans" <[email protected]> > wrote: > >> The Apache ACE team is proud to announce the release of ACE version 1.0.0. >> >> This is the first top-level release after completely changing the way we >> build the project and fixing many things since the last incubator release. >> From now on, we intend to release a lot more often! >> >> This release is available from our download page at: >> http://ace.apache.org/downloads.html
