geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Sisson <>
Subject Re: Sample plan bits for configId branch, please review!
Date Wed, 15 Feb 2006 23:24:06 GMT
Dain Sundstrom wrote:
> On Feb 15, 2006, at 10:59 AM, David Jencks wrote:
>>     <properties>
>>       <property>
>>         <name>base-name</name>
>>         <value>geronimo.maven:J2EEServer=geronimo</value>
>>       </property>
>>     </properties>
> I like this but I think the name should be name spaces to avoid 
> conflict.  Also we are the only ones that will touch this property so 
> if it is long it doesn't matter.  How about 
> org.apache.geronimo.j2ee.BaseName?
I agree we should be using name spaces.  If we think there may be other 
naming systems in the future, would it be worth having a prefix before 
the j2ee part of the name space to make it easier to find all uses (e.g. 
using grep or an IDE search function) of geronimo's naming properties 
regardless of the naming system used?  E.G:

'name' may not be the best choice in the example.. I chose it because 
'org.apache.geronimo.naming' is already used as a package name.

> On Feb 15, 2006, at 10:59 AM, David Jencks wrote:
>>       < dependency>
>>         <groupId>geronimo</groupId>
>>         <artifactId>geronimo-deployment</artifactId>
>>         <version>1.0.1-SNAPSHOT</version>
>>         <include/>
>>       </dependency>
> For those that are not aware, include means to literally include the 
> contents of the dependency jar into the car created by the 
> configuration.  This makes it easy to create stand alone self 
> executing configurations.  I suggest we move this feature to the 
> deploy tool using an optional flag and leave it out of this xml file.
> On Feb 15, 2006, at 12:51 PM, Matt Hogstrom wrote:
>> I'd prefer to make the version and type as optional.  Version would 
>> default to some server default.  Also, type can default to *car*.
> I think type "jar" will be the most common.  My guess is a component 
> will have 0-2 parents most of the time, but lots of jars.
>>>>>       <dependency>
>>>>>         <groupId>geronimo</groupId>
>>>>>         <artifactId>geronimo-common</artifactId>
>>>>>         <version>1.0.1-SNAPSHOT</version>
>>>>>         <load>class</load>
>> I'd prefer multiple <include> tags like
>> <include>classes</include>
>> <include>services</include>
> Since "include" has an existing meaning in Geronimo service plans, I 
> suggest that we name this element "import" to avoid any possible 
> confusion.
>> or the ever popular
>> <include>*</include>
> We are only talking about 2 items which isn't a big deal.  Also David 
> mentioned somewhere that the default in the absence to any "load" 
> (name David is using) tags it to do both classes and services.
> -dain

View raw message