Robert,
On 3/29/2019 8:59 AM, Robert Munteanu wrote:
Hi Ruben,
On Fri, 2019-03-29 at 08:13 -0700, Ruben Reusser wrote:
Robert,
I think as long as the 'maybe help with other stuff' part of your
email
is true I'd suggest not to use sling.cli
Suggestions welcome, I'm not terribly good at naming :-)
maybe sling.dc (sling developer companion) for things that are relevant
to the work a sling developer does?
On a separate note, for the sling based peregrine-cms we chose to
use
nodejs for the cli [1] to lower the entry barrier a bit
That's interesting. I briefly considered using something like go which
seems better suited for CLI tools ... but ended up deciding for
something familiar. How did you find node for writing CLI tools?
writing cli tools with node is in fact very simple and straight forward
as most nodejs based frameworks provide a cli tool. There is also a cli
tool for front end developers working on AEM (aemfed) at [1] it relies
on aemsync [2]
[1] https://www.npmjs.com/package/aemfed
[2] https://www.npmjs.com/package/aemsync
Robert
Ruben
[1] https://github.com/headwirecom/percli
On 3/29/2019 2:13 AM, Robert Munteanu wrote:
Hi,
Radu and I have been working on a little tool to automate some of
the
release work [1] (and maybe help with other stuff). See [2] for
background information.
As it's starting to take shape and become usable we'd like to move
it
out of the whiteboard.
I suggest we use 'org.apache.sling.cli' as the artifactId and
'sling-
org-apache-sling-cli' as the repository.
Thoughts?
Thanks,
Robert
[1]: https://github.com/apache/sling-whiteboard/tree/master/cli
[2]:
https://lists.apache.org/thread.html/b3001deea28c800f81830701c9293e66634f5512d70bed0043fb2302@%3Cdev.sling.apache.org%3E
