Ok, I get it. The xdoc should be written with the same encoding that is
used when it is read to generate the final report, which is
project.build.sourceEncoding (by default).
I fixed it, thanks!
-Lukas
Benjamin Bentmann wrote:
Lukas Theussl wrote:
I am confused indeed. I simply used MPLU
On Jan 16, 2011, at 5:52 PM, Brett Porter wrote:
> I was surprised to read this:
>
> http://www.sonatype.com/people/2011/01/how-to-use-aether-in-maven-plugins/
>
> Especially in context of the first two paragraphs of this:
>
> http://mail-archives.apache.org/mod_mbox/maven-dev/201008.mbox/%3cb
Lukas Theussl wrote:
I am confused indeed. I simply used MPLUGIN-180 to verify it works, but
just realized it's not good because both input and output encoding are
the same there.
Right, it gets only interesting if the two encodings have different
values, e.g. setting project.reporting.output
+1
On 12/01/2011, at 7:35 AM, Brian Demers wrote:
> Hi,
>
> We solved 6 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112&version=17017
>
> ** Improvement
>* [MINDEXER-4] - Upgrade to Lucene 3.0.3
>* [MINDEXER-7] - Make IndexingContext be able to receive remo
I was surprised to read this:
http://www.sonatype.com/people/2011/01/how-to-use-aether-in-maven-plugins/
Especially in context of the first two paragraphs of this:
http://mail-archives.apache.org/mod_mbox/maven-dev/201008.mbox/%3cb00d71d7-8a8e-4db2-bb99-725bf0f01...@apache.org%3E
As far as I kn
Benjamin Bentmann wrote:
Hi Lukaus,
Author: ltheussl
Date: Sun Jan 16 13:14:04 2011
New Revision: 1059551
URL: http://svn.apache.org/viewvc?rev=1059551&view=rev
Log:
[MPLUGIN-180] forward encoding to the PluginToolsRequest
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java
Hi Lukaus,
Author: ltheussl
Date: Sun Jan 16 13:14:04 2011
New Revision: 1059551
URL: http://svn.apache.org/viewvc?rev=1059551&view=rev
Log:
[MPLUGIN-180] forward encoding to the PluginToolsRequest
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plug
