bitmaker-software / tomee-cli Goto Github PK

Before verifying the signature, it should make sure it is possible to verify the signature. If it is not possible, the installation process should ignore it silently.

http://www.apache.org/dev/release-signing#verifying-signature

To properly configure tomme-cli to use a specific TomEE installation, we could pass parameters to tomee-cli in the command line in order to make it aware of a TomEE installation. The problem is that it would require typing huge command lines. A better solution would be to create a configuration file where we could put all the configuration inside and load it at initialization time. This way, the user can keep using very simple command lines to perform their repetitive work.

The configuration file could support multiple server configurations, so the user could switch from a configuration to another by simply calling (switch-to :dev) or (switch-to :test) or (switch-to :demo), where :dev, :test and :demo are three different TomEE configurations.

Some resources has optional property and isn't need put in xml, like password in Mail Resource.

This is an example of download mirrors page: http://www.apache.org/dyn/closer.cgi/tomee/tomee-1.7.1/apache-tomee-1.7.1-plus.zip
Analyze its content and extract the best link to download TomEE.

https://github.com/clojure/tools.cli

tomee-cli.core=> (start)

IOException error=13, Permission denied  java.lang.UNIXProcess.forkAndExec (UNIXProcess.java:-2)
tomee-cli.core=> 

The startup/shutdown/version should have execution permission: chmod +x ****.sh
In Wildfly we had a problem similar with aesh [ https://github.com/aeshell/aesh/commit/dd93f4bec242fa802013ed4a4bf13d1129bb4ebc ]
Maybe we can doing something like this, try set the file as executable before to call it.

(install-tomee "1.7.1" "/path/to/desired/location")

Support to configure database by vendor, like:

(add-new-datasource-resource :mysql)
(add-new-datasource-resource :oracle)
(add-new-datasource-resource :sql)
(add-new-datasource-resource :...)

This case the TomEE-CLI automatically download the drive and put in TOMEE_HOME/lib and configure the resource.

The user doesn't need to pass jdbc-driver and jdbc-url, the TomEE-CLI should need to receive only the port (has a default value case the user doesn't pass), database-name, username and password.