Niclas Hedhman wrote: > 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.
Ah, no, not really. I should have pointed out that a little better. As described in section 5.1 in step 1 I have one central project.ent containing all entities used in my POMs and that is the only file referencesd in my locator.ent files. That does also *not* mean, that the project.ent contains the entities itself, but includes other the different entity files. So my /myproject/build/entities directory contains the project.ent and all the files that define the real entities like characters.ent, versions.ent, ... project.ent contains the lines: <!ENTITY % character-entities SYSTEM "file:characters.ent"> %character-entities; <!ENTITY % version-entities SYSTEM "file:versions.ent"> %version-entities; ... See, that all references files here are located in the same directory. All of my locator.ent files contain just one line(1) like: <!ENTITY % project-entities SYSTEM "file:../../build/entities/project.ent"> %project-entities; (1) I have a second line, since I use the same technic for entities defining goals. That are all collected in a goal.ent similar to project.ent Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
