The initial commit is out there with rev. 449892.
I can deploy the updated tomcat car and then subsequently the
tomcat-deployer car produced with these changes. I can then
subsequently deploy a simple web application on tomcat. I have also
done the same with jetty, jetty-deploy, and again a simple web
application.
However, to this I have to cheat a little at the moment. I manually
copy the 1.2-SNAPSHOT jars necessary for tomcat, tomcat-deployer, jetty,
jetty-deployer, and most recently geronimo-clustering (due to the
dependency from jetty to geronimo-clustering) into the assemblies
repository. This is necessary for the time being because these jars
don't exist in any public repository.
I also have to cheat and copy the jetty schemas into the schema location
(the framework assembly build already includes the tomcat schemas for
now). Aaron pointed me to some info on how to get these schemas
included in the plugin and copied at deploy time which I will look at
next. Finally, for Jetty I also have to modify var\config\config.xml
WebBuilder default namespace to reference jetty instead of tomcat so
there's still some more work necessary there.
There are also some more items that should probably be removed from this
framework assembly ... but this is a start.
Initial commit to trunk on 09/25/06:
Adding assemblies\geronimo-framework
Adding assemblies\geronimo-framework\LICENSE.txt
Adding assemblies\geronimo-framework\NOTICE.txt
Adding assemblies\geronimo-framework\pom.xml
Adding assemblies\geronimo-framework\src
Adding assemblies\geronimo-framework\src\main
Adding assemblies\geronimo-framework\src\main\assembly
Adding assemblies\geronimo-framework\src\main\assembly\bin.xml
Adding assemblies\geronimo-framework\src\main\var
Adding assemblies\geronimo-framework\src\main\var\config
Adding assemblies\geronimo-framework\src\main\var\config\config.xml
Adding
assemblies\geronimo-framework\src\main\var\config\offline-deployer-list
Sending assemblies\pom.xml
Sending configs\jetty\pom.xml
Adding configs\jetty\src\main
Adding configs\jetty\src\main\resources
Adding configs\jetty\src\main\resources\META-INF
Adding configs\jetty\src\main\resources\META-INF\geronimo-plugin.xml
Sending configs\jetty\src\plan\plan.xml
Sending configs\jetty-deployer\pom.xml
Adding configs\jetty-deployer\src\main
Adding configs\jetty-deployer\src\main\resources
Adding configs\jetty-deployer\src\main\resources\META-INF
Adding
configs\jetty-deployer\src\main\resources\META-INF\geronimo-plugin.xml
Sending configs\pom.xml
Sending configs\tomcat\pom.xml
Adding configs\tomcat\src\main
Adding configs\tomcat\src\main\resources
Adding configs\tomcat\src\main\resources\META-INF
Adding
configs\tomcat\src\main\resources\META-INF\geronimo-plugin.xml
Sending configs\tomcat\src\plan\plan.xml
Sending configs\tomcat-deployer\pom.xml
Adding configs\tomcat-deployer\src\main
Adding configs\tomcat-deployer\src\main\resources
Adding configs\tomcat-deployer\src\main\resources\META-INF
Adding
configs\tomcat-deployer\src\main\resources\META-INF\geronimo-plugin.xml
Transmitting file data ..................
Committed revision 449892.
Joe Bohn wrote:
I've done some work on a new assembly that I've nicknamed "Micro-G" (I
know .. not very creative). The name that I'm using under
geronimo/assemblies is "geronimo-framework". This is intended to be a
new foundational assembly from which any customized Geronimo assembly
could be built by installing plugins we would provide (starting with
tomcat and jetty plugins).
Hopefully this could help us eliminate the need to provide so many
canned configurations with each release. I'm pretty sure we would
probably still want to provide at least one full j2ee server
configuration that we certified against, but we could potentially drop
the little-G assemblies and hopefully avoid additional future assemblies
based upon different combinations of components in the works.
So far, I've been doing this on my local image. I would like to get
this code (incomplete as it currently is) checked into trunk to better
manage the changes and to share the effort. Is this considered a
"controversial change"? Should I first provide a patch as it currently
stands so that folks can comment on it prior to a commit(ala RTC)?
I'm inclined to just commit the code since it is relatively self
contained at the moment, safe, and can be easily reverted. I think the
only controversial change thus far might be that I updated the default
port selections on the tomcat configuration so that if you install a
tomcat plugin on this framework assembly you will end up with the same
port configurations currently available on our existing tomcat
distributions. Of course, this means that the default ports are no
longer conducive to running two web servers in the same configuration.
Should I go ahead and commit this new assembly and config updates?
Joe
