geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Hogstrom (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-406) Move assembly out of modules
Date Thu, 17 Nov 2005 12:53:41 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-406?page=all ]

Matt Hogstrom updated GERONIMO-406:
-----------------------------------

    Fix Version: 1.x
                     (was: 1.0)

Is this still an issue?  Moving to 1.x

> Move assembly out of modules
> ----------------------------
>
>          Key: GERONIMO-406
>          URL: http://issues.apache.org/jira/browse/GERONIMO-406
>      Project: Geronimo
>         Type: Improvement
>   Components: buildsystem
>     Versions: 1.0-M4
>     Reporter: David Jencks
>     Assignee: Jeremy Boynes
>      Fix For: 1.x

>
> The main reason for the uber-build is really the circular dependency between the modules
in geronimo "modules" and openejb.  Openejb requires many of the geronimo modules, and geronimo
assembly requires openejb.
> This could be fixed by moving geronimo assembly out of modules.  I suggest making a bunch
of assemblies, starting with assembly/default which will include current modules/assembly.
> The result is that projects can be built in this order:
> howl
> geronimo/spec
> tranql
> tranql-connector
> geronimo/modules
> activemq
> openejb
> geronimo/assembly
> This can be done by a normal continuous integration tool rather than the uber-build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message