Date: 2004-01-29T08:32:34 Editor: 66.93.38.137 <> Wiki: Apache Geronimo Wiki Page: BuildingAndRunning URL: http://wiki.apache.org/geronimo/BuildingAndRunning
no comment Change Log: ------------------------------------------------------------------------------ @@ -28,6 +28,8 @@ = General Advice = +On Jan 21, 2004, we tagged the fairly stable current version and commenced rewriting the deployment structure. Until this process is complete, you may wish to experiment with the tagged version by checking out the last_geronimombean branch. You may wish to check on the IRC channel and mailing list to see how far the rewrite has proceeded. + If having problems building Geronimo, make sure it isn't simply because your Maven repository has become 'corrupted' or out of sync: Delete (or temporarily rename) the .maven directory in your home directory and try building Geronimo again. @@ -65,6 +67,20 @@ = Running The Server = +== For HEAD revision: == +(Jan 29, 2004) Deploying and running applications is now a multi step process. There is a maven plugin to help with the needed tasks. The current examples are in the assembly directory, and there are maven goals to run each step. Currently only gbean packages can be reliably deployed, although we expect this to change rapidly. + +1. Prepare your package. For gbean packages this should be a jar or zip file with class jars at the root and a META-INF/geronimo-service.xml file. The class jars need to be listed in <path> elements in geronimo-service.xml. Geronimo modules can include dependency jars in the package by including <package>true</package> in the dependency's property section. Packages are built automatically for geronimo modules with a src/etc/META-INF/geronimo-service.xml file. + +2. Deploy your package singly or in combination with other packages. This converts whatever you are deploying into the gbeans that will exist on the running Geronimo server and serializes the persistent GBean state and the classes needed into a .car (configuration archive). There is a maven plugin task def to help with this. An example is the assembly deploy:server goal which deploys a geronimo server. (It should have pretty much everything we have working in it). + +3. Install your configuration archive into a servers local configuration store. This informs the server that the configuration exists and indexes it. There is a maven plugin task to help with this. An example is the assembly install:server goal which installs the configuration constructed in (1). + +4. Start a server with a particular configuration. This can be done from maven in-vm using the load or loadAndWait tasks, examples being load:server and loadAndWait:server, or in a separate vm, examples being run:server and debug:server. + +There is also a "do it all" deployinstallrun goal. + +== For the legacy last_geronimombean tagged copy: == Once you've downloaded the source code, installed Maven and built the server, type `maven run:main` to run the server. As of December, 2003, there is no way to stop the server other than killing it, control-C or other such means.
