[EMAIL PROTECTED] wrote:Added Tim as a developer. It'd probably be a good idea to have an xml file
with entity definitions for commons developers so that the entry is the same
in each project.xml.
Shared entities are a PITA for people who care only about certain subprojects
(referencing shared files outside the subproject's directory generally sucks,
especially if they don't make it into source distributions).
i agree in general terms but the mavenized component builds mostly depend on the top level project.xml so i don't think that this would really make things much worse than they are already. probably should think about whether our source distributions need tweaking, though, since it's unlikely they'll build out-of-the-box at the moment.
I'd suggest do talk to the Maven people whether they could provide a sort
of include mechanism with graceful fallback, somewhat like XInclude. Or
actually use XInclude (pull out Cocoon's XInclude processor).
i had considered XInclude but concluded that it would probably impose a greater overhead on developers. if we're moving towards unified documentation builds, maybe this is something that could be addressed when we have a single documentation build.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
