[
https://issues.apache.org/jira/browse/RAT-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809679#comment-17809679
]
Philipp Ottlinger commented on RAT-359:
---------------------------------------
Trying to copy the files with maven-resources-plugin does not yield the correct
results as the apidocs-directory is cleared once the maven-javadoc-plugin
starts to write javadoc output:
{code:xml}
<!-- RAT-353, RAT-359: font files were generated from
https://github.com/marchof/the-missing-javadoc-fonts
and are not copied over properly neither with maven-antrun nor with
resources-plugin as Javadoc run empties the apidocs directory -->
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>copy-javadoc-font-resources-to-site</id>
<phase>install</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/site/apidocs/</outputDirectory>
<resources>
<resource>
<directory>src/site/javadocFont</directory>
<filtering>false</filtering>
</resource>
</resources>
</configuration>
</execution>
<execution>
<id>copy-javadoc-font-resources-to-staging</id>
<phase>install</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/staging/apidocs/</outputDirectory>
<resources>
<resource>
<directory>src/site/javadocFont</directory>
<filtering>false</filtering>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
{code}
Therefore we copy the files from RAT's directory tree into the site repo
manually via .buildtools!
> Replace externally loaded fonts Mate SC and Overlock with locally hosted ones
> to comply with privacy regulations
> ----------------------------------------------------------------------------------------------------------------
>
> Key: RAT-359
> URL: https://issues.apache.org/jira/browse/RAT-359
> Project: Apache Rat
> Issue Type: Task
> Components: site
> Affects Versions: 0.16
> Reporter: Philipp Ottlinger
> Assignee: Philipp Ottlinger
> Priority: Major
> Fix For: 0.16.1
>
>
> Due to
> [https://privacy.apache.org/faq/committers.html#can-i-use-google-fonts]
> we should replace the
> {code:html}
> <head>
> <![CDATA[<link href="https://fonts.googleapis.com/css?family=Mate+SC";
> type="text/css" rel="stylesheet" />]]>
> </head>
> {code}
> snippets in all webpages with a locally hosted version.
> This applies to all of Creadur's projects:
> [https://whimsy.apache.org/site/project/creadur]
> h2. Font Mate SC / Overlock
> licensed under [https://openfontlicense.org/]
> is part of the google-main-fonts:
> {code:bash}
> fonts-main/ofl/matesc$ ls
> DESCRIPTION.en_us.html MateSC-Regular.ttf METADATA.pb OFL.txt
> upstream.yaml
> {code}
> - no attribution required
> - 2.1 Can I make webpages using these fonts?
> Yes! Go ahead! You could ask visitors to download and install the fonts, but
> loading the fonts dynamically as webfonts through CSS @font-face declarations
> is a much better method. The referenced fonts can be hosted on the same
> server as other site assets and content, or loaded from a separate webfont
> service. This is recommended and explicitly allowed by the licensing model
> because it is distribution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
