Serge Knystautas wrote:
Stephen McConnell wrote:Danny Angus wrote:1. a James releasse scenario - this is where you referencingrelased jars2. a James build that is based on the current CVS of Avalonbased on Gump
I agree with 1, but not with 2.
I don't think it does James any good to treat the Avalon jar dependencies any different than we would other libraries. I also don't think it does Avalon any good in the long term.
I agree with Serge, despite our close relationship with avalon I think we *must* work with released software only,
But your not - your build against and distributing against an unrelease cornerstone package.
Well yes, and I think this is again why we don't want (and would like to no longer be) doing #2, i.e., building against what's in CVS... because we end up using unreleased code and are otherwise not supported.
No. I'm not suggesting *using* unrelease code.
#2 is getting the Gump descriptor for James sorted - that does not effect you day to day work.
So now it's a question of getting Avalon to make a published release, and then get a proposal from someone to do the upgrade... and as you imply, since we're not building against a release, I don't think you'd get much disagreement (and I hope we've been supportive of your preparatory work to have that happen).
I would really like to sucessfully validate the candidates against James before proposing releases.
If there is cornerstone code we need that isn't getting released, we can absorb that code into the James package so that we can determine it releasable, and then if Avalon does release it, we can review handing over responsibility for that functionality back to them.
I've updated corenerstone so that each component that James is depedent on has its own build procedure and release version. This means that (a) your not carrying around code for components you are not using, (b) your migrating to something that is supported, and (c) furture evolution of components can be managed properly.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
