You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Jencks <da...@yahoo.com> on 2007/09/19 15:16:50 UTC

Should geronimo plans have the "external knobs" in them?

While chatting with vamsi on IRC I realized there is now a big  
difference between deploying using the car-maven-plugin and deploying  
using the console or cli deployers.  With the car--maven-plugin you  
get to add stuff to config.xml, artifact_aliease.properties, and  
config-substitutions.properties -- basically all the knobs your  
application exposes that enable external configuration to the server  
environment.  With the other ways none of this is available.

This makes be wonder if we should be including all this "knobs" stuff  
in our plans rather than hiding it in the maven pom for the car-maven- 
plugin to find.

hopefully this is coherent enough to understand....

thanks
david jencks


Re: Should geronimo plans have the "external knobs" in them?

Posted by Donald Woods <dw...@apache.org>.
Advanced users always want extra knobs to turn... :-)

Seems that we need to update the deployer and Portlet to expose these 
knobs/configuration options, instead of restricting the functionality of the 
car-maven-plugin or just to that tool.

Maybe the plugin support needs to be moved out of the deployer and into a 
separate command module (which can still use the deploy code when a local CAR 
is being installed), now that we have GShell?  Seems that there are a lot of 
options in the current "deploy" tool which have nothing to do with deploying 
and undeploying apps, which should be moved out into GShell as their own 
commands....


-Donald


David Jencks wrote:
> While chatting with vamsi on IRC I realized there is now a big 
> difference between deploying using the car-maven-plugin and deploying 
> using the console or cli deployers.  With the car--maven-plugin you get 
> to add stuff to config.xml, artifact_aliease.properties, and 
> config-substitutions.properties -- basically all the knobs your 
> application exposes that enable external configuration to the server 
> environment.  With the other ways none of this is available.
> 
> This makes be wonder if we should be including all this "knobs" stuff in 
> our plans rather than hiding it in the maven pom for the 
> car-maven-plugin to find.
> 
> hopefully this is coherent enough to understand....
> 
> thanks
> david jencks
> 
> 
>