The following comment has been added to this issue:
Author: Martin Skopp
Created: Fri, 22 Aug 2003 3:51 AM
Body:
+1 (and I mean it)
maven -especially the plugins- need better documentation.
There are _lots_ of undocumented properties, this is just one example.
maven.javadoc.links is (was) another (fixed in MVEN-94).
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-707
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-707
Summary: Set encoding when doing javadoc
Type: Bug
Status: Unassigned
Priority: Trivial
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-javadoc
Fix Fors:
1.1
Versions:
1.0-beta-10
Assignee:
Reporter: dion gillard
Created: Thu, 21 Aug 2003 7:46 PM
Updated: Thu, 21 Aug 2003 7:46 PM
Description:
Hi,
I decided to use Maven in my project - this is great and powerful tool.
I encountered one problem during site:generate. I use utf-8 charset in
java sources (javadocs are written in polish) and I noticed that Maven
doesn't set proper <meta> tag to generated javadoc's HTMLs regardless
the setting of maven.docs.outputencoding property.
Is there a way to force Maven to use encoding in generated javadocs?
I use v. 1.0-beta-10.
--
pozdrawiam . . . . . . . . . . .
Piotr Maj .:. kernelpanic.pl .:.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
