On Sunday 18 April 2004 23:39, Jason van Zyl wrote: > You pretty gave no explanation as to why catalogs would be a good thing > other than saying:
We are trying (@Avalon) the hardest to centralize the versioning of our 70+ versioned artifacts, their cross-dependencies and all the external dependencies that are involved. The http://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities gave us some ideas, but unfortunately, it doesn't really work, since ALL external references are relative current directory. That means that in every directory we would need a complete "index.ent" file listing everything, which seems like a big waste of maintenance problems. Catalogs is a mechanism to solve the non-portable SYSTEM identifiers, and map them to the actual locations of those files. I can recommend the Cocoon explaination http://cocoon.apache.org/2.1/userdocs/concepts/catalog.html and the link in that document; http://www.dpawson.co.uk/docbook/catalogs.html Catalogs or Entity Resolution revolves around using either the PUBLIC or SYSTEM identifiers, look it up in the Catalog and return the file that the catalog is pointing at (relative to the catalog file!!!). This solves our problems. If Maven is not interested in this at all, what do you have up your sleeve, so that I can have centralized lists of versions used in all the subprojects? Cheers Niclas P.S Time already wasted. ~10 lines of change in MavenUtils. -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
