If you look down near the end of the configs poms you see something like:
<plugin>
<groupId>org.apache.geronimo.plugins</groupId>
<artifactId>car-maven-plugin</artifactId>
<configuration>
<deploymentConfigs>
<deploymentConfig>${gbeanDeployer}</deploymentConfig>
<deploymentConfig>${j2eeDeployer}</deploymentConfig>
<deploymentConfig>${jettyDeployer}</deploymentConfig>
<deploymentConfig>${clientDeployer}</deploymentConfig>
<deploymentConfig>${openejbDeployer}</deploymentConfig>
<deploymentConfig>${axisDeployer}</deploymentConfig>
</deploymentConfigs>
<module>
<groupId>org.apache.geronimo.applications</groupId>
<artifactId>geronimo-dojo</artifactId>
<version>${version}</version>
<type>war</type>
</module>
</configuration>
</plugin>
The deploymentConfigs are the builder configs that need to be started before we
start trying to build the current module. Through some maven magic Jason made
it so these even turn into dependencies so they don't need to be duplicated in
the dependency list!
thanks
david jencks
----- Original Message ----
From: Tim McConnell <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Friday, November 17, 2006 1:45:16 PM
Subject: Kernel builder question during maven build process
Does anyone happen to know how builders are loaded by the Geronimo Kernel
during the Maven build process ??
Reason I ask is that I notice that during parts of the build the Deployer class
is aware of either 1 or
sometimes 2 builders, although it is instantiated with zero builders. It looks
like these builders are the
ServiceConfigBuilder GBean and the EARConfigBuilder GBean, but I'd just like to
understand how, why, and when
they get loaded during a build process (not from the normal Daemon startup).
Thanks much
Tim