Hi Marcel I just flew over your Wiki page. This looks good. I had a slightly different, more generic, approach. I implemented e.g. the command: add feature name=foo .... list of attributes For this approach, less dedicated commands are necessary. But nevertheless, it's a trade of. A change would be very easy. What's your opinion about this?
But I'm also fine with your proposal. As a starting point I used the VaadinClient and derived my own client from that. But the VaadinClient doesn't use a workspace. The REST client does. I implemented directly the login command (delegated to the login of the client API) and used also the checkout. This worked (nearly) fine in my tests. I have to investigate a little bit on the REsT workspace, to understand this topic a little bit better. Then I will switch over to it. Danke und Grüße Wilfried -----Ursprüngliche Nachricht----- Von: Marcel Offermans [mailto:[email protected]] Gesendet: Mittwoch, 26. Juni 2013 01:33 An: [email protected] Betreff: Re: ACE client On Jun 25, 2013, at 23:33 PM, Marcel Offermans <[email protected]> wrote: > On Jun 25, 2013, at 17:30 , [email protected] wrote: > >> This was a good recommendation. I was able to implement a set of gogo >> commands to work on the ACE repo. > > You're welcome! Following up on this, I just created https://issues.apache.org/jira/browse/ACE-366 and added a first implementation of a set of shell commands. I also created a wiki page with some short documentation about it: https://cwiki.apache.org/confluence/display/ACE/Gogo+Shell+client+API I'm curious if this is similar to the shell commands you created and what you think about it. I'm quite confident that the shell is a powerful way to script ACE. Greetings, Marcel
