Well, after setting *by hand* the bundle from
plugin-resources\templates\templates
to
plugin-resources/templates/templates
the goal xdoc:jelly-transform generated the good html document.
so do i need to fill an issue in JIRA ?
Stéphane
stéphane bouchet a écrit :
Hi,
I am having the same problem with differents environments.
On my Win2k box, with JDK 1.4.2, i got a good report document
But in my Solaris box, with JDK 1.5, i got a bad report document.
when i look in the generated reports, for example maven-reports.xml, in
both case i got :
<properties>
<title key="template.maven_reports.title"
bundle="plugin-resources\templates\templates" />
</properties>
So in Unix environements, there is a problem with the bundle ?????
Cheers,
Stéphane
Incze Lajos a écrit :
Vincent is right, bundle="plugin-resources\templates\templates" is plain
wrong (it may work on windows, but nowhere else). I checked the xdoc
plugin templates with bundle="plugin-resources.templates.templates"
and it cures your problem.
Also, it may cause problems, when files contain "&&" operators, this way
they are not valid xml (they are not inside a CDATA section). Altough,
as I see, all of them are in jelly directives, so they may disappear
before parsing the xml, I don' know jelly.
incze
On Mon, Jun 20, 2005 at 10:54:35AM -0400, Mike Ratliff wrote:
I am working on Mac OS X (10.4.1)
I got the reports to work just fine if I downgraded to Maven version
1.0.2 from Beta 1 of 1.1.
I am now working under the assumption that it is a problem with the
beta and Mac OS X, but that is just a guess.
On your suggestion of changing the backslash to a dot...I am not sure
how to see the results of that change. Those files are generated and
therefor I don't really have an opportunity to see the results of that
change being processed. Am I missing something in your suggestion?
On 6/20/05, Vincent Siveton <[EMAIL PROTECTED]> wrote:
Hi Mike,
What is your environnement?
And just to be sure, lets try to replace the backslash character by a
dot in the bundle definition, ie:
bundle="plugin-resources\templates\templates"
by
bundle="plugin-resources.templates.templates"
Gives me your feedback,
Cheers,
Vincent
2005/6/18, Mike Ratliff <[EMAIL PROTECTED]>:
The problem that I am having is manifesting itself on all the reports
under the Project Info group (mailing lists, project team, project
inf, etc)
The other reports (checkstyle, fileactivity, etc) work just fine.
The problem is that all the section headers and such have odd
references embedded instead of the text they should have. A sample of
the project-info xml and html follows...
*********************************************************************
<document>
<properties>
<title key="template.project_info.title"
bundle="plugin-resources\templates\templates"/>
</properties>
<body>
<section key="template.project_info.section.title"
bundle="plugin-resources\templates\templates">
<p>
<message
key="template.project_info.section.project_information1"
bundle="plugin-resources\templates\templates"/>
<a href="http://maven.apache.org/";>Maven</a>
<message
key="template.project_info.section.project_information2"
bundle="plugin-resources\templates\templates"/>
</p>
***********************************************************************
this results in html output that looks something like:
************************************************************************
???template.maven_reports.section.title???
???template.maven_reports.section.maven_reports1??? Maven
???template.maven_reports.section.maven_reports2???
???template.maven_reports.section.subsection.title???
**************************************************************************************************************
I realize I must be missing something simple, but I don't have a clue
as to what it is.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mike Ratliff
---------------------------------------------------------------------
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]
