Jim Walker wrote:
> We also understand the problem where several open source projects depend
> on older versions of Junit and don't plan to update their code to use
> the newer version. We felt it was best to start by porting the current
> version and revise it as new releases are made available. Then, look at
> adding additional older versions that are frequently used/requested.
There needs to be something about how you intend to handle these
newer versions. The canonical choices are:
1) overwrite the old version with the new, thus only having one
installed at any given time, or
2) have some directory structure/pkg architecture to support the
unambiguous installation and use of multiple versions on a
single system simultaneously
If 1, why are you doing something that isn't well aligned with
the known use-case for the component, and if 2, how will you
actually do it?
-John
