geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Closed: (GERONIMO-487) split deployment module into at least 2 parts
Date Fri, 03 Dec 2004 15:15:23 GMT
     [ ]
Aaron Mulder closed GERONIMO-487:

      Assign To: Aaron Mulder
     Resolution: Fixed
    Fix Version: 1.0-M4

Split into 4 parts (deployment, service builder, CLI deployer, test DDBean classes).

For the DConfigBeans, an IRC conversation concluded that we might do best to create geronimo/dconfigbeans/(module)
or something along those lines so we put the DConfigBeans together yet keep them split out
by module.

> split deployment module into at least 2 parts
> ---------------------------------------------
>          Key: GERONIMO-487
>          URL:
>      Project: Apache Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M3
>     Reporter: David Jencks
>     Assignee: Aaron Mulder
>      Fix For: 1.0-M4

> I believe the last intermingling of deployment-only and runtime code is in the deployment
module, which contains at least the gbean deployer, various classes needed to boot geronimo,
and lots of jsr-88 implementation.  At the very least the gbean deployer (ServiceConfigBuilder)
should be in a different module than the boot classes.  This will let us remove xmlbeans from
the startup classpath (lib) of all geronimo versions, including the standalone deployer. 
For all subsystems, I'd like some opinions on whether the DConfigBeans should be in the builder
modules or in another parallel family of modules.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message