You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Daniel Cunha <da...@gmail.com> on 2015/04/13 22:20:32 UTC
A client to manage your Apache TomEE instances
Hello everyone,
I'm glad to announce today the release of Tomee-cli, a command line
tool to manage your Apache TomEE instances.
https://github.com/bitmaker-software/tomee-cli
We decided to think out of the box and come up with a solution that's
easy to use and develop, offering the maximum number of
functionalities with a minimum amount of code. To achieve that, we
wrote the tool in Clojure (a JVM hosted language) and we use its REPL
to offer the command line facilities. It's so straightforward to use
that we probably are more user friendly than JBoss-cli.
We currently support the following functionalities:
install tomee
start server
stop server
restart server
print versions of the execution environment
deploy war and ear applications
undeploy war and ear applications
add email resource
add datasource
add JMS resource
All these functionalities were written in less than 300 lines of code
within just over a month (started in Mar 9th) . Can you imagine what
we can achieve within a year?!
We already use tomee-cli internally and we're happy with the result.
We would love to see you using it as well. So, please, follow the
instructions in the readme file, try it and let us know what you
think.
The project is open, so you can help like do you want.
--
Best regard,
Daniel Cunha (soro)
Re: A client to manage your Apache TomEE instances
Posted by Hildeberto Mendonça <me...@hildeberto.com>.
These are all valuable feedback. Thanks a lot Romain!
On Tue, Apr 14, 2015 at 11:31 AM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> 2015-04-14 10:51 GMT+02:00 Hildeberto Mendonça <me...@hildeberto.com>:
>
> > On Tue, Apr 14, 2015 at 9:43 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > wrote:
> >
> > > hmm,
> > >
> > > so it seems the readme is not yet complete ;)
> > >
> >
> > Documentation is a continuous effort. Now we have a release, we will
> > finally give more attention to it. Did you miss something there? Any
> > difficulty that we can simplify?
> >
> >
> well surely the roadmap part and the template side is a bit "light" today
> (typically I need far more properties for prod - not for other
> environments.
>
>
> >
> > > btw tomee has a ssh connector with some commands (
> > >
> >
> https://rmannibucau.wordpress.com/2012/05/09/tomee-and-its-ssh-connector/
> > > ).
> > >
> >
> > That's good material. Thanks for sharing. Btw, your first sentence there
> > "TomEE is a simple but great container." represents exactly the
> philosophy
> > behind Clojure. Good that we are not bringing something complex to the
> > table. It means, as a community, we may not "speak" the same language but
> > we think exactly the same way. ;-)
> >
> >
> Sure, my point was more about "merging" communities. Just checking github
> projects you often see "i rewrote it cause it was not in my language".
>
>
> >
> > > That said joining our efforts would still be good and even if in 3
> lines
> > of
> > > clojure you avoid maybe 10 lines of java you stay "alone" in term of
> > > community and you can't assume you have clojure on prod machines IMO
> and
> > > that "prod" guys can write clojure - but you can assume you have java
> and
> > > that prod guys are shell expert, no?
> > >
> >
> > We are literally joining your effort, but in a different repository and
> in
> > another language. This is not a contribution to TomEE's code base, but
> it's
> > definitely a contribution to TomEE's ecosystem. We are aware of the risk
> of
> > having less contributors, but what actually motivates us is to deliver a
> > new functionality in the shortest amount of time we can possibly get,
> > preserving the same level of performance and robustness of the JVM.
> >
> >
> Let's try and see what is happening, maybe I'm not optimist enough - but
> well I'm french ;)
>
>
> > Btw, Clojure is just one more jar in the app ;-) When people install
> > TomEE-CLI, all dependencies are downloaded automatically. They don't even
> > realise that Clojure is there. When they pass the commands to the command
> > line they don't even realize they are actually programming in clojure.
> For
> > instance, install TomEE:
> >
> >
> That's more about default environment otherwise you are right.
>
>
> > // Install the latest version of TomEE web profile in the working
> > directory.
> > (install-tomee)
> >
> > // Install the latest version of TomEE Plus in the working directory.
> > (install-tomee :dist "plus")
> >
> > // Install the version 1.7 of TomEE Plus in the path /opt.
> > (install-tomee :version "1.7" :dist "plus" :location "/opt")
> >
> > These are valid Clojure expressions, as simple as command lines. We are
> > simply calling our functions there.
> >
> >
> Ask a shell guys, it is weird and when he'll get a syntax error it will not
> be obvious - once again just real feedback, tried groovy in prod as
> "interface" and was already too much.
>
>
> > I know, the actual Clojure source code looks strange. That's what I
> thought
> > when I first looked at it. But I can tell you that I'm not that smart,
> but
> > I was able to grasp the language in less than a month. I started learning
> > Clojure in January only during my free time, sharing this time with two
> > little kids under 3.5 years old, and now I'm releasing software with it.
> > When I became parent I realized time is my most important resource. I
> > simply can't waste it anymore.
> >
> > So, we will be happy when we finally have contributors, but we will be
> even
> > happier when we have many happy users \o/
> >
>
> So you have to do .deb and .rpm ;). That's surely your best way to promote
> it without loosing guys on the road.
>
--
Hildeberto Mendonça, Ph.D
Blog: http://www.hildeberto.com
Community: http://www.cejug.net
Twitter: https://twitter.com/htmfilho
Re: A client to manage your Apache TomEE instances
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2015-04-14 10:51 GMT+02:00 Hildeberto Mendonça <me...@hildeberto.com>:
> On Tue, Apr 14, 2015 at 9:43 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> wrote:
>
> > hmm,
> >
> > so it seems the readme is not yet complete ;)
> >
>
> Documentation is a continuous effort. Now we have a release, we will
> finally give more attention to it. Did you miss something there? Any
> difficulty that we can simplify?
>
>
well surely the roadmap part and the template side is a bit "light" today
(typically I need far more properties for prod - not for other environments.
>
> > btw tomee has a ssh connector with some commands (
> >
> https://rmannibucau.wordpress.com/2012/05/09/tomee-and-its-ssh-connector/
> > ).
> >
>
> That's good material. Thanks for sharing. Btw, your first sentence there
> "TomEE is a simple but great container." represents exactly the philosophy
> behind Clojure. Good that we are not bringing something complex to the
> table. It means, as a community, we may not "speak" the same language but
> we think exactly the same way. ;-)
>
>
Sure, my point was more about "merging" communities. Just checking github
projects you often see "i rewrote it cause it was not in my language".
>
> > That said joining our efforts would still be good and even if in 3 lines
> of
> > clojure you avoid maybe 10 lines of java you stay "alone" in term of
> > community and you can't assume you have clojure on prod machines IMO and
> > that "prod" guys can write clojure - but you can assume you have java and
> > that prod guys are shell expert, no?
> >
>
> We are literally joining your effort, but in a different repository and in
> another language. This is not a contribution to TomEE's code base, but it's
> definitely a contribution to TomEE's ecosystem. We are aware of the risk of
> having less contributors, but what actually motivates us is to deliver a
> new functionality in the shortest amount of time we can possibly get,
> preserving the same level of performance and robustness of the JVM.
>
>
Let's try and see what is happening, maybe I'm not optimist enough - but
well I'm french ;)
> Btw, Clojure is just one more jar in the app ;-) When people install
> TomEE-CLI, all dependencies are downloaded automatically. They don't even
> realise that Clojure is there. When they pass the commands to the command
> line they don't even realize they are actually programming in clojure. For
> instance, install TomEE:
>
>
That's more about default environment otherwise you are right.
> // Install the latest version of TomEE web profile in the working
> directory.
> (install-tomee)
>
> // Install the latest version of TomEE Plus in the working directory.
> (install-tomee :dist "plus")
>
> // Install the version 1.7 of TomEE Plus in the path /opt.
> (install-tomee :version "1.7" :dist "plus" :location "/opt")
>
> These are valid Clojure expressions, as simple as command lines. We are
> simply calling our functions there.
>
>
Ask a shell guys, it is weird and when he'll get a syntax error it will not
be obvious - once again just real feedback, tried groovy in prod as
"interface" and was already too much.
> I know, the actual Clojure source code looks strange. That's what I thought
> when I first looked at it. But I can tell you that I'm not that smart, but
> I was able to grasp the language in less than a month. I started learning
> Clojure in January only during my free time, sharing this time with two
> little kids under 3.5 years old, and now I'm releasing software with it.
> When I became parent I realized time is my most important resource. I
> simply can't waste it anymore.
>
> So, we will be happy when we finally have contributors, but we will be even
> happier when we have many happy users \o/
>
So you have to do .deb and .rpm ;). That's surely your best way to promote
it without loosing guys on the road.
Re: A client to manage your Apache TomEE instances
Posted by Hildeberto Mendonça <me...@hildeberto.com>.
On Tue, Apr 14, 2015 at 9:43 AM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> hmm,
>
> so it seems the readme is not yet complete ;)
>
Documentation is a continuous effort. Now we have a release, we will
finally give more attention to it. Did you miss something there? Any
difficulty that we can simplify?
> btw tomee has a ssh connector with some commands (
> https://rmannibucau.wordpress.com/2012/05/09/tomee-and-its-ssh-connector/
> ).
>
That's good material. Thanks for sharing. Btw, your first sentence there
"TomEE is a simple but great container." represents exactly the philosophy
behind Clojure. Good that we are not bringing something complex to the
table. It means, as a community, we may not "speak" the same language but
we think exactly the same way. ;-)
> That said joining our efforts would still be good and even if in 3 lines of
> clojure you avoid maybe 10 lines of java you stay "alone" in term of
> community and you can't assume you have clojure on prod machines IMO and
> that "prod" guys can write clojure - but you can assume you have java and
> that prod guys are shell expert, no?
>
We are literally joining your effort, but in a different repository and in
another language. This is not a contribution to TomEE's code base, but it's
definitely a contribution to TomEE's ecosystem. We are aware of the risk of
having less contributors, but what actually motivates us is to deliver a
new functionality in the shortest amount of time we can possibly get,
preserving the same level of performance and robustness of the JVM.
Btw, Clojure is just one more jar in the app ;-) When people install
TomEE-CLI, all dependencies are downloaded automatically. They don't even
realise that Clojure is there. When they pass the commands to the command
line they don't even realize they are actually programming in clojure. For
instance, install TomEE:
// Install the latest version of TomEE web profile in the working directory.
(install-tomee)
// Install the latest version of TomEE Plus in the working directory.
(install-tomee :dist "plus")
// Install the version 1.7 of TomEE Plus in the path /opt.
(install-tomee :version "1.7" :dist "plus" :location "/opt")
These are valid Clojure expressions, as simple as command lines. We are
simply calling our functions there.
I know, the actual Clojure source code looks strange. That's what I thought
when I first looked at it. But I can tell you that I'm not that smart, but
I was able to grasp the language in less than a month. I started learning
Clojure in January only during my free time, sharing this time with two
little kids under 3.5 years old, and now I'm releasing software with it.
When I became parent I realized time is my most important resource. I
simply can't waste it anymore.
So, we will be happy when we finally have contributors, but we will be even
happier when we have many happy users \o/
Re: A client to manage your Apache TomEE instances
Posted by Romain Manni-Bucau <rm...@gmail.com>.
hmm,
so it seems the readme is not yet complete ;)
btw tomee has a ssh connector with some commands (
https://rmannibucau.wordpress.com/2012/05/09/tomee-and-its-ssh-connector/).
That said joining our efforts would still be good and even if in 3 lines of
clojure you avoid maybe 10 lines of java you stay "alone" in term of
community and you can't assume you have clojure on prod machines IMO and
that "prod" guys can write clojure - but you can assume you have java and
that prod guys are shell expert, no?
BTW looking forward to see what's your remote solution!
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-04-14 7:05 GMT+02:00 htmfilho <me...@hildeberto.com>:
> Hi Romain,
>
> Concerning Clojure, we try to think about the goal, not the medium. If a
> language allow us to provide more for TomEE with less effort and time then
> that's the one we are going to use.
>
> Good that there are some commands available. We can easily embed all of
> them
> into TomEE-CLI by simply reusing them.
>
> Clojure's REPLs can connect to each other. So, if we have a cluster
> environment, we can start TomEE-CLI in each one of the servers and control
> all of them from the instance you started at your machine. We don't need to
> code this complex mechanism in Java to achieve the same result. More news
> about this feature in the next milestone that comes out every 30 days.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/A-client-to-manage-your-Apache-TomEE-instances-tp4674390p4674398.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
Re: A client to manage your Apache TomEE instances
Posted by htmfilho <me...@hildeberto.com>.
Hi Romain,
Concerning Clojure, we try to think about the goal, not the medium. If a
language allow us to provide more for TomEE with less effort and time then
that's the one we are going to use.
Good that there are some commands available. We can easily embed all of them
into TomEE-CLI by simply reusing them.
Clojure's REPLs can connect to each other. So, if we have a cluster
environment, we can start TomEE-CLI in each one of the servers and control
all of them from the instance you started at your machine. We don't need to
code this complex mechanism in Java to achieve the same result. More news
about this feature in the next milestone that comes out every 30 days.
Thanks
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/A-client-to-manage-your-Apache-TomEE-instances-tp4674390p4674398.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: A client to manage your Apache TomEE instances
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Looks interesting but clojure doesn't help contribution for java projects
in general (well from my experience at least).
FYI TomEE already has some command tooling using tomee.sh. It is based on
simple java main (public static void main(final String... args)) + a small
SPI (META-INF/org.apache.openejb.cli/mycommand):
-------------------------------
$ ./bin/tomee.sh --help
usage: openejb <command> [options] [args]
Available commands:
cipher Encrypt a database password and print it to stdout.
deploy Deploy an ejb jar or ear into OpenEJB.
effectivetomee Shows properties TomEE will use for resources
properties Convert and print the OpenEJB configuration as
properties
setters List property available for a class
start Start the OpenEJB Remote Server for accessing beans in
client/server mode.
stop Stop the OpenEJB Remote Server.
undeploy Undeploy an ejb jar or ear
Try 'openejb <command> --help' for help on a specific command.
For example 'openejb deploy --help'.
Apache OpenEJB -- EJB Container System and Server.
For additional information, see http://tomee.apache.org
Bug Reports to <us...@tomee.apache.org>
-------------------------------
It is pretty trivial to enrich and while in tomee/lib it is auto discovered.
We don't have yet add-X commands but should be easy to add while just
modifying tomee.xml - would need a little more work to do it in a running
server but still possible.
Advantage of org.apache.openejb.cli commands is it is aligned with tomee
(version). Drawback is the same (release lifecycle).
What do you think about migrating commands you miss to a tomee module (or
just enriching the ones in openejb-core)?
Personally I would even go further than your CLI using the shell a bit more
either to pass inline all properties/attributes of a resource or to ask it
in interactive mode:
$ ./tomee.sh add-resource --JdbcUrl jdbc:mysql://localhost:3606/test
--JdbcDriver auto --SomeSpecificProperty specificValue --attribute:type
DataSource --attribute:id=jdbc/mysqlDb
Then add-datasource would just be a shortcut with defaults for all missing
attributes/properties.
wdyt? does it make sense? Motivated to try to merge your project with
tomee/openejb?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-04-13 22:34 GMT+02:00 Daniel Cunha <da...@gmail.com>:
> Another thing that we want to do, interoperability between Clojure and
> Java,
> it's by creating a JBoss Forge addon, so you can run the tool within
> JBoss Forge.
>
> On Mon, Apr 13, 2015 at 5:20 PM, Daniel Cunha <da...@gmail.com>
> wrote:
> > Hello everyone,
> >
> > I'm glad to announce today the release of Tomee-cli, a command line
> > tool to manage your Apache TomEE instances.
> >
> > https://github.com/bitmaker-software/tomee-cli
> >
> > We decided to think out of the box and come up with a solution that's
> > easy to use and develop, offering the maximum number of
> > functionalities with a minimum amount of code. To achieve that, we
> > wrote the tool in Clojure (a JVM hosted language) and we use its REPL
> > to offer the command line facilities. It's so straightforward to use
> > that we probably are more user friendly than JBoss-cli.
> >
> > We currently support the following functionalities:
> >
> > install tomee
> > start server
> > stop server
> > restart server
> > print versions of the execution environment
> > deploy war and ear applications
> > undeploy war and ear applications
> > add email resource
> > add datasource
> > add JMS resource
> >
> > All these functionalities were written in less than 300 lines of code
> > within just over a month (started in Mar 9th) . Can you imagine what
> > we can achieve within a year?!
> >
> > We already use tomee-cli internally and we're happy with the result.
> > We would love to see you using it as well. So, please, follow the
> > instructions in the readme file, try it and let us know what you
> > think.
> >
> > The project is open, so you can help like do you want.
> >
> > --
> > Best regard,
> > Daniel Cunha (soro)
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>
Re: A client to manage your Apache TomEE instances
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Looks interesting but clojure doesn't help contribution for java projects
in general (well from my experience at least).
FYI TomEE already has some command tooling using tomee.sh. It is based on
simple java main (public static void main(final String... args)) + a small
SPI (META-INF/org.apache.openejb.cli/mycommand):
-------------------------------
$ ./bin/tomee.sh --help
usage: openejb <command> [options] [args]
Available commands:
cipher Encrypt a database password and print it to stdout.
deploy Deploy an ejb jar or ear into OpenEJB.
effectivetomee Shows properties TomEE will use for resources
properties Convert and print the OpenEJB configuration as
properties
setters List property available for a class
start Start the OpenEJB Remote Server for accessing beans in
client/server mode.
stop Stop the OpenEJB Remote Server.
undeploy Undeploy an ejb jar or ear
Try 'openejb <command> --help' for help on a specific command.
For example 'openejb deploy --help'.
Apache OpenEJB -- EJB Container System and Server.
For additional information, see http://tomee.apache.org
Bug Reports to <us...@tomee.apache.org>
-------------------------------
It is pretty trivial to enrich and while in tomee/lib it is auto discovered.
We don't have yet add-X commands but should be easy to add while just
modifying tomee.xml - would need a little more work to do it in a running
server but still possible.
Advantage of org.apache.openejb.cli commands is it is aligned with tomee
(version). Drawback is the same (release lifecycle).
What do you think about migrating commands you miss to a tomee module (or
just enriching the ones in openejb-core)?
Personally I would even go further than your CLI using the shell a bit more
either to pass inline all properties/attributes of a resource or to ask it
in interactive mode:
$ ./tomee.sh add-resource --JdbcUrl jdbc:mysql://localhost:3606/test
--JdbcDriver auto --SomeSpecificProperty specificValue --attribute:type
DataSource --attribute:id=jdbc/mysqlDb
Then add-datasource would just be a shortcut with defaults for all missing
attributes/properties.
wdyt? does it make sense? Motivated to try to merge your project with
tomee/openejb?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-04-13 22:34 GMT+02:00 Daniel Cunha <da...@gmail.com>:
> Another thing that we want to do, interoperability between Clojure and
> Java,
> it's by creating a JBoss Forge addon, so you can run the tool within
> JBoss Forge.
>
> On Mon, Apr 13, 2015 at 5:20 PM, Daniel Cunha <da...@gmail.com>
> wrote:
> > Hello everyone,
> >
> > I'm glad to announce today the release of Tomee-cli, a command line
> > tool to manage your Apache TomEE instances.
> >
> > https://github.com/bitmaker-software/tomee-cli
> >
> > We decided to think out of the box and come up with a solution that's
> > easy to use and develop, offering the maximum number of
> > functionalities with a minimum amount of code. To achieve that, we
> > wrote the tool in Clojure (a JVM hosted language) and we use its REPL
> > to offer the command line facilities. It's so straightforward to use
> > that we probably are more user friendly than JBoss-cli.
> >
> > We currently support the following functionalities:
> >
> > install tomee
> > start server
> > stop server
> > restart server
> > print versions of the execution environment
> > deploy war and ear applications
> > undeploy war and ear applications
> > add email resource
> > add datasource
> > add JMS resource
> >
> > All these functionalities were written in less than 300 lines of code
> > within just over a month (started in Mar 9th) . Can you imagine what
> > we can achieve within a year?!
> >
> > We already use tomee-cli internally and we're happy with the result.
> > We would love to see you using it as well. So, please, follow the
> > instructions in the readme file, try it and let us know what you
> > think.
> >
> > The project is open, so you can help like do you want.
> >
> > --
> > Best regard,
> > Daniel Cunha (soro)
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>
Re: A client to manage your Apache TomEE instances
Posted by Daniel Cunha <da...@gmail.com>.
Another thing that we want to do, interoperability between Clojure and Java,
it's by creating a JBoss Forge addon, so you can run the tool within
JBoss Forge.
On Mon, Apr 13, 2015 at 5:20 PM, Daniel Cunha <da...@gmail.com> wrote:
> Hello everyone,
>
> I'm glad to announce today the release of Tomee-cli, a command line
> tool to manage your Apache TomEE instances.
>
> https://github.com/bitmaker-software/tomee-cli
>
> We decided to think out of the box and come up with a solution that's
> easy to use and develop, offering the maximum number of
> functionalities with a minimum amount of code. To achieve that, we
> wrote the tool in Clojure (a JVM hosted language) and we use its REPL
> to offer the command line facilities. It's so straightforward to use
> that we probably are more user friendly than JBoss-cli.
>
> We currently support the following functionalities:
>
> install tomee
> start server
> stop server
> restart server
> print versions of the execution environment
> deploy war and ear applications
> undeploy war and ear applications
> add email resource
> add datasource
> add JMS resource
>
> All these functionalities were written in less than 300 lines of code
> within just over a month (started in Mar 9th) . Can you imagine what
> we can achieve within a year?!
>
> We already use tomee-cli internally and we're happy with the result.
> We would love to see you using it as well. So, please, follow the
> instructions in the readme file, try it and let us know what you
> think.
>
> The project is open, so you can help like do you want.
>
> --
> Best regard,
> Daniel Cunha (soro)
--
Best regard,
Daniel Cunha (soro)
Re: A client to manage your Apache TomEE instances
Posted by Daniel Cunha <da...@gmail.com>.
Another thing that we want to do, interoperability between Clojure and Java,
it's by creating a JBoss Forge addon, so you can run the tool within
JBoss Forge.
On Mon, Apr 13, 2015 at 5:20 PM, Daniel Cunha <da...@gmail.com> wrote:
> Hello everyone,
>
> I'm glad to announce today the release of Tomee-cli, a command line
> tool to manage your Apache TomEE instances.
>
> https://github.com/bitmaker-software/tomee-cli
>
> We decided to think out of the box and come up with a solution that's
> easy to use and develop, offering the maximum number of
> functionalities with a minimum amount of code. To achieve that, we
> wrote the tool in Clojure (a JVM hosted language) and we use its REPL
> to offer the command line facilities. It's so straightforward to use
> that we probably are more user friendly than JBoss-cli.
>
> We currently support the following functionalities:
>
> install tomee
> start server
> stop server
> restart server
> print versions of the execution environment
> deploy war and ear applications
> undeploy war and ear applications
> add email resource
> add datasource
> add JMS resource
>
> All these functionalities were written in less than 300 lines of code
> within just over a month (started in Mar 9th) . Can you imagine what
> we can achieve within a year?!
>
> We already use tomee-cli internally and we're happy with the result.
> We would love to see you using it as well. So, please, follow the
> instructions in the readme file, try it and let us know what you
> think.
>
> The project is open, so you can help like do you want.
>
> --
> Best regard,
> Daniel Cunha (soro)
--
Best regard,
Daniel Cunha (soro)
Re: A client to manage your Apache TomEE instances
Posted by "Leonardo K. Shikida" <sh...@gmail.com>.
Kudos, Daniel :-)
[]
Leo
On Mon, Apr 13, 2015 at 5:20 PM, Daniel Cunha <da...@gmail.com> wrote:
> Hello everyone,
>
> I'm glad to announce today the release of Tomee-cli, a command line
> tool to manage your Apache TomEE instances.
>
> https://github.com/bitmaker-software/tomee-cli
>
> We decided to think out of the box and come up with a solution that's
> easy to use and develop, offering the maximum number of
> functionalities with a minimum amount of code. To achieve that, we
> wrote the tool in Clojure (a JVM hosted language) and we use its REPL
> to offer the command line facilities. It's so straightforward to use
> that we probably are more user friendly than JBoss-cli.
>
> We currently support the following functionalities:
>
> install tomee
> start server
> stop server
> restart server
> print versions of the execution environment
> deploy war and ear applications
> undeploy war and ear applications
> add email resource
> add datasource
> add JMS resource
>
> All these functionalities were written in less than 300 lines of code
> within just over a month (started in Mar 9th) . Can you imagine what
> we can achieve within a year?!
>
> We already use tomee-cli internally and we're happy with the result.
> We would love to see you using it as well. So, please, follow the
> instructions in the readme file, try it and let us know what you
> think.
>
> The project is open, so you can help like do you want.
>
> --
> Best regard,
> Daniel Cunha (soro)
>