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/07/25 18:49:00 UTC

[jira] [Closed] (MSITE-907) Last Published not being calculated by site plugin

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

Michael Osipov closed MSITE-907.
--------------------------------
    Fix Version/s:     (was: waiting-for-feedback)
                       (was: wontfix-candidate)
       Resolution: Information Provided

Technically likely, but that would incur the same overhead the versions-maven-plugin does. Not tolerable in a build. We generally recommend to the most recent version of a component as soon as possible.

> Last Published not being calculated by site plugin
> --------------------------------------------------
>
>                 Key: MSITE-907
>                 URL: https://issues.apache.org/jira/browse/MSITE-907
>             Project: Maven Site Plugin
>          Issue Type: Bug
>          Components: site:run
>    Affects Versions: 4.0.0-M3
>            Reporter: Dave Wichers
>            Priority: Major
>
> If you run: mvn site against the main branch of this project: [https://github.com/nahsra/antisamy]
> Instead of generating:  Last Published: 2022-07-25| Version: 1.7.0.1-dev. (on all the generated pages)
> It generates:  $i18n.getString( "site-renderer", $locale, "template.lastpublished" ): $dateValue| $i18n.getString( "site-renderer", $locale, "template.version" ): 1.7.0.1-dev
> I even tried using: version 4.0.0-M3.  The 3.12.0 release works fine for my project.
> Is something configured wrong in my use of the v4 version of this plugin? I didn't change any of my configuration when upgrading from 3.12.0 to 4.0.0.X. Or is this a bug?
> I'm likely to commit a change to the pom soon to set it back to 3.12.0. If that is the case, you'll have to change the import to 4.0.0-M3 to replicate this bug.
> I'm using Java 8, which I know is really old, if that matters. I just tested with Java 11 and 15, and that didn't change the behavior.



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