Defining initialization parameters

[danielsoro]

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.

[htmfilho]

I think this issue can be closed after implementing the solution with the environment variable TOMEE_HOME.

[danielsoro]

-1

We need fix it completely.
We can set the TOMEE_HOME env ATM, but we cannot change the environment. So, we need implement the switch-to function and define the configuration file.

I think that this configuration file needs to have some informations like:
version // tomee version.
distrubution //tomee distribuition (jaxrs / plus / plume / webprofile)
path //tomee path

We can switch the environment with file name, like: dev.properites (switch-to :dev)
blablabla.properties (switch-to :blablabla)

Maybe we can set the default path for configuration, like: ~/.tomee-cli
But, the user can change it. OFC.
WDYT!?

[danielsoro]

Maybe we can define a record for this case and change it when switch-to is called.
It seem the most easy way.
It needs to be visible for all namespaces.

(defrecord tomee-cli-configuration [tomee-version tomee-distribution tomee-path])

WDYT!?

[htmfilho]

I think this issue should be out of the milestone. There are too many questions to be answered. Maybe, we can allocate it for the next release, when we can finally get some feedback from users.

I think we should write the basics and add only what the users ask for later on. It's a way to be sure that every single functionally is effectively used.

Just my 2 cents :-)

[danielsoro]

👍

[danielsoro]

@htmfilho
I think that is a good alternative: https://github.com/weavejester/environ