[ http://jira.codehaus.org/browse/MPXDOC-153?page=comments#action_42697 ]
Rafal Krzewski commented on MPXDOC-153:
---------------------------------------
I run into the same problem after upgrading to 1.1-beta-1, which includes
xdoc-1.9.1 plugin.
My brief investigation shows that jelly:fmt works correctly when ResourceBundle
is passed explicitly, like:
<fmt:message key="site.doc_for" bundle="${msg}"/>
but fails when the bundle is selected by name from within site.jsl, like:
<jsl:template match="message" trim="true">
<j:set var="_key">
<x:expr select="@key" />
</j:set>
<j:set var="_bundle">
<x:expr select="@bundle" />
</j:set>
<j:if test="${!empty(_key)}">
<!-- Default bundle is the user one in ${maven.xdoc.bundle} -->
<j:if test="${empty(_bundle)}">
<fmt:message key="${_key}" bundle="${myMsg}" />
</j:if>
<j:if test="${!empty(_bundle)}">
<fmt:bundle basename="${_bundle}">
<fmt:message key="${_key}" />
</fmt:bundle>
</j:if>
</j:if>
<jsl:applyTemplates />
</jsl:template>
invoked from <message key="template.mail_lists.not_available"
bundle="plugin-resources\templates\templates" />
My guess is that Jelly classloader thingy is not massaged the right way, and
<fmt:bundle> feeds <fmt:message> with blank LocalizationContext.
I don't have resources to mess with Jelly ATP, so I checked out xdoc-1.8,
whacked it here and there to compile against maven-1.1-beta-1 &
maven-model-3.0.0. Worked for me.
> Some web pages shows ???<variable>??? with maven 1.1 beta-1
> -----------------------------------------------------------
>
> Key: MPXDOC-153
> URL: http://jira.codehaus.org/browse/MPXDOC-153
> Project: maven-xdoc-plugin
> Type: Bug
> Versions: 1.9.1
> Environment: Solaris 2.9, jre 1.5.0_02, maven 1.1 beta-1
> Reporter: Eric Lapierre
> Assignee: Arnaud HERITIER
> Attachments: XDOCbug.zip
>
>
> The target/docs/mail-lists.html contains things like:
> <h2>???template.mail_lists.section.title???</h2>
> <p>
> ???template.mail_lists.section.no_mail_list???
> </p>
> I have attached a small project that reproduces the problem even though I
> believe any project would produce the same result. To reproduce the problem,
> just run "maven site"
> This problem is seen with maven 1.1-beta-1. It was not tested with maven 1.0.2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
