> -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > > On Monday 15 December 2003 20:35, Nicolai Wadstr�m wrote: > > Any thoughts or comments? > > I have brought this up a couple of months ago on the > developer list, under a "Naming and Identification" "flaw" > (Read room for future improvements.) > > We'll see if there is enough "itch" somewhere to make an > improvement. Care to > help with a patch ? :o)
Sure, though being new to the mailing list and how the Avalon project is managed, I do not exactly know where to start... (but with some help..) To me this seems like it could be done through: - Get a more clean structure documented. - Getting enough consensus behind the clean structure to get it published as part of the documentation. To me this seems crucial to the mission of Merlin to allow COP, and make it easy to assemble applications of ready-made components, but who are the stakeholders here? - A repository provider that supports an alias list stored in the repository itself would help migration to a more clean-structure (thus existing repositories could be migrated to the new clean structure, and old components would still be able to access the .JAR's they use as long as a version of Merlin with the new Repository Provider is being used). Another approach might be just to go for an alias file outside the repository itself, so that one could configure the mapping for a particular Merlin installation. / Nicolai --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
