Yes, I think the hrefkey is definitely a better idea for this specific case.
I guess the question we have to start approaching with features now is how much more effort should be put into duplicating this across the m1/m2 plugins before we just cut the m1 plugin over to doxia (m2). - Brett Nacho G. Mac Dowell wrote: > Hi Brett, thanks for the interest! > > Currently we are mavenizing ws-jaxme and I'd like to be able to have > the external links of the user-docs on a single properties file (or > whatever) as we do right now with forrest. It seemed like a good idea > to me if we could use velocity on the user-docs and consider them as > templates if needed. Also, on multiprojects this could be quite > useful. For the links-use-case there is a simpler alternative which > would be to have a hrefkey (or whatever) on the anchor tag which would > also make sense in a i18n world. If you have any other ideas they > would be very welcome! Anyway I'm willing to contribute with patches, > docs and tests if needed. > > Best regards, > > nacho > > Brett Porter wrote: > >> Ignacio, thanks for putting the effort into this, but for significant >> changes it does need to be discussed with the dev team first (thanks for >> approaching us now to do so). >> >> I'm not in favour of this change as it is against the direction we are >> taking things. To introduce Jelly processing into the source files ties >> it to an XML format, but we support plain text, docbook, xdoc and more >> in Maven2 and may backport that to Maven1. >> >> I'd like to discuss your use case on the list to see what alternatives >> there are. >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
