db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: Single JDK14 compile model?
Date Sun, 06 Mar 2005 21:17:19 GMT
I am not sure if each platform module would be small... Unless we are
talking about a really small number of files, this could cause
maintenance issues. Even in closed development enviornments, products
take extreme care to avoid code duplication.. It might be a bigger
challenge in open source setup... Having three (ME, JDK1.3, JDK1.4) or
even four (with JDK1.5) versions of the code doesn't seem right.

It is a good goal to have developpers develop on one platform. Not sure
what it the right way to get there ...


Jeremy Boynes wrote:

> If we had three small modules for the JDBC API impls then they could
> be compiled once under the appropriate JDK and then just referenced by
> others as needed (e.g. during packaging). The amount of code in each
> would be small and stagnant so there would be no need to build from
> source all the time.
> Under this model, I could do all my development and testing using 1.4
> and the JDCB3.0 modules and you would do all your development and
> testing using J2ME and the JSR169 modules. We take care in shared code
> not to use features that are not available in the other platform. We
> both make progress, and rapidly because we can concentrate on the
> feature we're working on rather than the cross-platform build.
> Every so often, say nightly, an automated process builds all versions
> on all platforms so as a whole we catch any issues with inappropriate
> dependencies or non-portable code. That process may be Gump, it may be
> something else.
> For this to work, we would need to break things down so that a
> developer could work with just one platform at a time. I think that
> means moving away from the one-jar-fits-all model to a
> package-by-platform model.
> -- 
> Jeremy

View raw message