Details
-
Task
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
0.1
-
None
Description
Build failed after updates of plugins:
* apply v2.0 of https://maven.apache.org/doxia/doxia-sitetools/doxia-site-model/site.htmlis still using the old pre-version 2.0.0 model.
You MUST migrate to the new model as soon as possible
otherwise your build will break in the future!
- need to define a skin
- tryout: reflow-maven-skin - not working
- old default skin is not working either:
<skin>
<groupId>org.apache.maven.skins</groupId>
<artifactId>maven-default-skin</artifactId>
<version>1.3</version>
</skin>
-
- resorting to defaults does not work: not defining a skin results in build failure
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on project apache-tentacles: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.20.0:site failed: skin cannot be null -> [Help 1]
- Using default/old skin results in next error - https://issues.apache.org/jira/projects/MSKINS/issues/MSKINS-196
- resorting to defaults does not work: not defining a skin results in build failure
- problem with jdepend-report: https://github.com/mojohaus/jdepend-maven-plugin/issues/39 - temporarily disabled jdepend
- https://github.com/mojohaus/jdepend-maven-plugin/issues/39
- https://issues.apache.org/jira/browse/MNG-8243 LinkageError during site builds
- 2.1-SNAPSHOT generates a report whose layout is broken - tables do not seem to be generated - https://github.com/mojohaus/jdepend-maven-plugin/issues/43
- update plugins
- https://issues.apache.org/jira/browse/MPIR-468 useless warning is printed during the site run
- will be fixed with a newer pmd-plugin version as it uses pmd >=7.4.0; currently used version 3.25.0 uses a pmd version that issues this warning
- https://github.com/pmd/pmd/pull/5102
- fix site build
- https://issues.apache.org/jira/browse/MSITE-1018 LastPubDate is always set fixed to 1970-01-01, although older versions rendered correctly (as can be seen at the whisker site)
- Remove project.build.outputTimestamp completely - timestamp is still wrong (e.g. 2024-07-04 instead of 2024-10-14)
- overwrite with 'a' in order to get the current date as timestamp and have valid entries in the JAR itself
Attachments
Issue Links
- causes
-
MSITE-1018 LastPublicationTimestamp shows a fixed timestamp instead of the last build date
- Closed
- is related to
-
WHISKER-26 Update to latest site-plugin and migrate to newer skins as necessary
- Open
- links to