On Monday 21 June 2004 01:51, Adam R. B. Jack wrote: > I'd be interesting in collaborating to keep parts of Depot, and integrate > with Avalon's code. I think that bringing fresh eyes into the code (and > onto the problem) would force us (Depot) to focus and clean-up the > docs/designs (on Wiki). I think a joint goal -- with joint use cases -- > could really work this out to something practical. Yes, I'd be very > interested in that.
Good. I'll try to set aside some time to be part of Depot move forward... Short notice on versioning; We have more or less concluded that 'version strings' now in use are malicious. They mix concerns too much and should probably not be used in the way it is (indicating buildnumber, compatibility, development stage et cetera). They should be seen as opaque strings and a separate system should be made to express the orthogonal concerns of such version. More about this later. > BTW: So Magic can use Ant tasks, is that it? I've read about it (in mails) > but I hadn't registered that. Interesting. Magic is really a set of Tasks, and a tiny "boiler-template" for invoking it all. And it is all done using the standard mechanisms available in Ant. That said, there is a Model, which defines all the projects within the 'larger project', and standard targets (similar to Maven's goals) which are available. And since the underlying mechansim is 100% Ant, any modifications to the build.xml (boiler-template mentioned above), will be carried in its expected fashion. Next on _my_ agenda for Magic is to allow Java logic (in script form) to be invoked as part of the build process, when doing in Ant or Ant+JavaScript makes it messy. Another issue I think is on our agenda, is that Avalon Repository is not used in Magic, since Magic builds Repository, and that would be nice to solve as well. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+