geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Geronimo Wiki] Update of "Building" by JoeBohn
Date Thu, 20 Oct 2005 18:32:34 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by JoeBohn:

  == Building the specs ==
  From the Geronimo root directory: `maven -Dmodule.types=specs`
+ = Building the Web Console =
+ The web console is composed of several elements and "pre-deployed" in the binary image.
 Hence it is a little more complicated to build:
+ First, the web console is composed of 4 parts:
+  * applications/console-core  - This component contains common parts shared across the console
+  * applications/console-framework - This component includes the Pluto portal configuration
embedded within the console application that hosts the console content.
+  * applications/console-standard - This component contains all of the console "content"
delivered as portlets.
+  * applications/console-ear - This component is resopnsible to build the console application
that includes all of the above.
+ When changing any modules in these components you should follow the build order listed above.
 For example, if you change a module in console-core then you should rebuild console-core,
followed by console-framework, followed by console-standard, followed by console-ear.  If
you only change something in console-standard then you should be ok only building console-standard
and console-ear.  Maven can be run from each of these "root" locations.
+ Finally, since the console is a pre-deployed application you should rebuild modules/assembly
if you want to update the binary image directly.  Otherwise, you can treat the console as
any other application and redeploy or undeploy/deploy it manually.
+ Note:  I've noticed some problems at times where modified classes or wars are not picked
up in higher level builds (building wars, jars, or ears).  To be on the safe side I often
find myself preceeding every "maven" with a "maven clean".
  = Compile Only =

View raw message