Hi Brett, Well, according my experience, we also have these problems: there is classpath for bundles and another one for multiproject (maven reactor). Please check this mail: http://www.mail-archive.com/[email protected]/msg21646.html Actually, I have no clue about it, what about you?
Another problem is the translation of the report generated. In fact, I think that the language (default one and supported language) should become a standalone part of the POM definition (sourceforge.net provides translation support as project definition). Thus, all plugins should provide integrated solutions for i18n. Cheers, Vincent -----Message d'origine----- De : Brett Porter [mailto:[EMAIL PROTECTED] Envoy� : 14 f�vrier 2005 07:06 � : Maven Users List; Arnaud HERITIER Objet : Re: I18n site Hi, Is any work being undertaken on this? I'm not actively doing anything to xdoc at the moment, and it should be safe to apply the changes to HEAD. Currently the only known problems is that anything inside <![CDATA[ ... ]]> is being lost in translation (ie most <source/> fragments). - Brett On Thu, 3 Feb 2005 11:47:15 +0100, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > I used it, I just add to set the required version of the maven yo > > 1.1-SNAPSHOT instead od 1.1. > > > > It works fine for a single project but I had some problems with the > > multiproject:site. I think that the children projects are overiding > > the parent project's bundle. > > > > An improvement could be the plugin not to 'escape' the properties, > > so we could add bigger blocks in the properties files. Actually if > > you need to insert a link, you must use three properties. > > > > Could I retrieve the sources of the patch ? > > Vincent gave us the full project but not a diff. > Actually Brett is working on the xdoc plugin so you must be careful > you must merge changes done in the plugin done since Vincent's > checkout. > > A good think was : > 1) checkout the plugin at the date Vincent provided its release. > 2) override the plugin with Vincent's one > 3) Generate a diff (+ new files) for Vincent's changes (attach this > patch to the issue) > 4) Update the plugin from SVN > 5) apply the patch generated in 3 > 6) Make your changes > 7) Generate a new patch > > > > > Should I add this comments in jira or follow the thread in maven-dev ? > > We can talk about functionalities on the users list to share it with > everybody but for technical things we can use Jira. > > Arnaud > > > -- > > Thomas Recloux > > > > -------------------------------------------------------------------- > > - 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] > > --------------------------------------------------------------------- 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]
