Nick,
Dependencies page states that current version is 1.2, so it probably
stuck there since then, and not being generated now anyway.
As for reports plugin, apparently it it receives the site generation
settings from parent (apache). Overriding this in tika-parent may
help:
<build>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.3</version>
<configuration>
<outputDirectory>/local/dev/PROJECTS/Tika/tika.trunk/tika-parent/target/site</outputDirectory>
<reportPlugins>
<reportPlugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.7</version>
<configuration>
<dependencyDetailsEnabled>false</dependencyDetailsEnabled>
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
</configuration>
<reportSets>
<reportSet>
<id>default</id>
<configuration>
<dependencyDetailsEnabled>false</dependencyDetailsEnabled>
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
</configuration>
<reports>
<report>project-team</report>
<report>mailing-list</report>
<report>index</report>
<report>summary</report>
<report>modules</report>
<report>license</report>
<report>project-team</report>
<report>scm</report>
<report>issue-tracking</report>
<report>mailing-list</report>
<!--
<report>dependency-management</report>
<report>dependencies</report>
<report>dependency-convergence</report>
-->
<report>cim</report>
<report>plugin-management</report>
<report>plugins</report>
<report>distribution-management</report>
</reports>
</reportSet>
</reportSets>
</reportPlugin>
</reportPlugins>
</configuration>
</plugin>
</build>
On Thu, Feb 27, 2014 at 5:44 PM, Nick Burch <[email protected]> wrote:
> On Thu, 27 Feb 2014, Vadim Roizman wrote:
>>
>> No, it probably just pops up in google results, bun then it propagates:
>>
>> https://stackoverflow.com/questions/21929040/special-characters-stored-when-extracting-content-from-microsoft-word-documents#comment33371269_22007797
>
>
> It seems they're being generated by a part of the maven reports plugin,
> which is getting them wrong and I can't work out how to stop it even trying.
> My workaround is to delete the dependencies files and blacklist them in
> svn:ignore so they won't get re-committed.
>
> Suggestions on how to either make them work properly, or how to properly
> exclude that part of the report gratefully received!
>
> Nick
--
Regards,
Vadim Roizman
