Transit is not at the point where the full transit system can be
executed as an Ant plugin. This basically means 100% of the fully
functional repository services available in ant.
Earlier today I was experimenting with repository based deployment of
runnable plugins - which is working fine. I now want to move on to the
loading of magic as a plugin under the control of the repository system.
This requires the addition of the support for Magic's plugin descriptor
model - but that would introduce a second plugin model in the repository
impl
a) .meta files used by the repo system (e.g. logging impls,
merlin system, activation, etc.)
b) the '.plugin' descriptor used in magic
It seems to me that perhaps we should normalize the two before we get
into a release cycle with Magic. Some suggestions on this subject were
posted by Niclas back ages ago:
http://marc.theaimsgroup.com/?l=avalon-dev&m=106871435803658&w=2
http://marc.theaimsgroup.com/?l=avalon-dev&m=106871960908984&w=2
Maybe now is a good time to prototype something?
Stephen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
