You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Farb <dm...@chicagonet.net> on 2004/11/04 16:11:17 UTC
Re: [Apache Geronimo Wiki] Updated: WishList/M3
Axis may be required for J2EE 1.4 compliance, but I don't think that
necessarily translates into one very large build containing every
component.
If someone is working on the Axis integration, then why should they be
held up because of a problem with the integration of some other module.
If the build were subdivided into some fundamental modules (kernel,
core, system, naming, network, ...) which could be built and assembled
as a unit, and then other modules or groups of modules built on top of
that core, (Say a Jetty-Axis web group ...), it would then be possible
to build just the parts you really want.
This makes work on some particular part of Geronimo easier since that
work is dependent ONLY on the code it really needs.
Re: [Apache Geronimo Wiki] Updated: WishList/M3
Posted by Dain Sundstrom <ds...@gluecode.com>.
My gut feeling is that would be more trouble then it is worth. The
project still must build the tree every day, so we know that the source
is consistent. Also, before someone commits code they must build the
whole tree to make sure they didn't introduce a subtle bug.
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Nov 4, 2004, at 1:29 PM, Davanum Srinivas wrote:
> ok
>
>
> On Thu, 04 Nov 2004 15:11:17 -0000, David Farb
> <dm...@chicagonet.net> wrote:
>>
>> Axis may be required for J2EE 1.4 compliance, but I don't think that
>> necessarily translates into one very large build containing every
>> component.
>>
>> If someone is working on the Axis integration, then why should they be
>> held up because of a problem with the integration of some other
>> module.
>>
>> If the build were subdivided into some fundamental modules (kernel,
>> core, system, naming, network, ...) which could be built and assembled
>> as a unit, and then other modules or groups of modules built on top of
>> that core, (Say a Jetty-Axis web group ...), it would then be possible
>> to build just the parts you really want.
>>
>> This makes work on some particular part of Geronimo easier since that
>> work is dependent ONLY on the code it really needs.
>>
>>
>
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [Apache Geronimo Wiki] Updated: WishList/M3
Posted by Davanum Srinivas <da...@gmail.com>.
ok
On Thu, 04 Nov 2004 15:11:17 -0000, David Farb <dm...@chicagonet.net> wrote:
>
> Axis may be required for J2EE 1.4 compliance, but I don't think that
> necessarily translates into one very large build containing every
> component.
>
> If someone is working on the Axis integration, then why should they be
> held up because of a problem with the integration of some other module.
>
> If the build were subdivided into some fundamental modules (kernel,
> core, system, naming, network, ...) which could be built and assembled
> as a unit, and then other modules or groups of modules built on top of
> that core, (Say a Jetty-Axis web group ...), it would then be possible
> to build just the parts you really want.
>
> This makes work on some particular part of Geronimo easier since that
> work is dependent ONLY on the code it really needs.
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/