Niclas Hedhman wrote:
On Wednesday 05 May 2004 00:37, Stefan Bodewig wrote:
On Tue, 4 May 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
Assuming that Phoenix goes into archive, what do we do for James (and others)? There are a few:
Turn phoenix into an installed package.
Things below Phoenix are still developing, and can (have?) break Phoenix. As such, we can't even package Phoenix & expect success for James and such.
Why not? Phoenix will never change.
Part of the problem (may) be;
Phoenix depends on X. James also depends on X.
X changes so it breaks Phoenix, but Phoenix comes with its own older version of X, so "it doesn't change".
What happens for James, since it will need to compile against either the X in Phoenix or X provided by Gump.
Phoenix loads applications in their own classloader - i.e. the version used by Phoenix should not impact the version of something used in James. I.e. James can build against X provided by Gump.
Stephen.
Niclas
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
