You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/11/20 17:12:00 UTC

[jira] [Updated] (DOXIASITETOOLS-270) Remove internal (pseudo) skin and use external Maven Fluido Skin

     [ https://issues.apache.org/jira/browse/DOXIASITETOOLS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated DOXIASITETOOLS-270:
------------------------------------------
    Summary: Remove internal (pseudo) skin and use external Maven Fluido Skin  (was: Remove bundled default skin and use external Maven Fluido Skin)

> Remove internal (pseudo) skin and use external Maven Fluido Skin
> ----------------------------------------------------------------
>
>                 Key: DOXIASITETOOLS-270
>                 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-270
>             Project: Maven Doxia Sitetools
>          Issue Type: Task
>          Components: Site renderer
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 2.0.0-M4
>
>
> The "Maven Default Skin" skin ( https://maven.apache.org/skins/maven-default-skin/ , source = https://github.com/apache/maven-default-skin/ ) is poorly maintained (see the so old-looking sample output https://maven.apache.org/skins/maven-default-skin/sample/ ) and shares a lot code with the Fluido Skin which no one cross checks.
> To ease maintenance, we will retire the Maven Default Skin with MSKINS-196 and will solely rely on bundled skin artifacts.
> By default site renderer will require a skin to be provided which is selfcontained, Maven Default Skin isn't.
> If no site.xml site descriptor is provided, by default the fluido skin will be used.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)