[ANN] Apache Maven Doxia Sitetools 2.0.0-M19 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M19 https://maven.apache.org/doxia/doxia-sitetools/ Release Notes - Maven Doxia Sitetools - Version 2.0.0-M19 ** Improvement * [DOXIASITETOOLS-340] - Rearrange title order in Velocity context ** Dependency upgrade * [DOXIASITETOOLS-337] - Move maven-compat to test scope * [DOXIASITETOOLS-338] - Upgrade to Parent 42 and Maven 3.6.3 * [DOXIASITETOOLS-341] - Upgrade plugins and components (in ITs) * [DOXIASITETOOLS-342] - Upgrade to Maven Fluido Skin 2.0.0-M9 in default site descriptor Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M12. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M12 ** Dependency upgrade * [MSHARED-1392] - Upgrade to Parent 42 and Maven 3.6.3 * [MSHARED-1396] - Upgrade to Doxia 2.0.0-M11 * [MSHARED-1399] - Upgrade to Doxia 2.0.0-M12 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia version 2.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia, version 2.0.0-M12 https://maven.apache.org/doxia/ Release Notes - Maven Doxia - Version 2.0.0-M12 ** Bug * [DOXIA-737] - [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia version 2.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia, version 2.0.0-M11 https://maven.apache.org/doxia/ Release Notes - Maven Doxia - Version 2.0.0-M11 ** Dependency upgrade * [DOXIA-736] - Upgrade to Parent 42 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M14 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M14. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M14 ** Bug * [MSITE-1006] - MSITE-723 causes duplicate document rendering and log output ** Dependency upgrade * [MSITE-1003] - Upgrade plugins and components (in ITs) * [MSITE-1004] - Upgrade org.apache.maven:maven-archiver to 3.6.2 * [MSITE-1005] - Upgrade org.codehaus.plexus:plexus-archiver to 4.9.2 Please also note for this new major version: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Plugin Tools 3.13.0 released
The Apache Maven team is pleased to announce the release of the Apache Maven Plugin Tools, version 3.13.0. https://maven.apache.org/plugin-tools/ Release Notes - Maven Plugin Tools - Version 3.13.0 ** Bug * [MPLUGIN-517] - GoalRenderer renderParameterDetails() renders in wrong order * [MPLUGIN-521] - Nested types not properly extracted cause exception while generating Javadoc URLs ** Improvement * [MPLUGIN-520] - Get rid of maven-compat classes use ** Dependency upgrade * [MPLUGIN-516] - Upgrade asmVersion from 9.6 to 9.7 * [MPLUGIN-519] - Update to Parent POM 42, prerequisite 3.6.3 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M13 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M13. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M13 ** Task * [MSHARED-1387] - Clean up dependencies ** Dependency upgrade * [MSHARED-1362] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M14 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M14. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M14 ** Dependency upgrade * [MSHARED-1348] - Upgrade plugins and components (in ITs) * [MSHARED-1361] - Upgrade plugins and components (in ITs) (2) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia Sitetools 2.0.0-M18 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M18 https://maven.apache.org/doxia/doxia-sitetools/ Release Notes - Maven Doxia Sitetools - Version 2.0.0-M18 ** New Feature * [DOXIASITETOOLS-324] - Allow configuration of parser per markup ** Improvement * [DOXIASITETOOLS-332] - Create anchors for indexable entries automatically * [DOXIASITETOOLS-334] - Pass project relative source path to Parser.parse(...) as reference argument * [DOXIASITETOOLS-336] - Make SiteRenderingContext#siteDirectories editable aware ** Dependency upgrade * [DOXIASITETOOLS-321] - Upgrade htmlunit 2.x to 3.x * [DOXIASITETOOLS-322] - Upgrade to Doxia 2.0.0-M9 * [DOXIASITETOOLS-323] - Upgrade components * [DOXIASITETOOLS-325] - Upgrade to Maven Reporting API 4.0.0-M10 * [DOXIASITETOOLS-326] - Update org.codehaus.plexus:plexus-component-metadata to 2.2.0 * [DOXIASITETOOLS-331] - Upgrade to htmlunit 3.11.0 * [DOXIASITETOOLS-333] - Upgrade commons-io:commons-io to 2.16.1 * [DOXIASITETOOLS-335] - Upgrade to Doxia 2.0.0-M10 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: doxia-maven-plugin stale / dead?
On 2024/04/16 09:48:51 nino martinez wael wrote: > Hi, > > I was looking for a maven plugin that would help me generate guides and > small books as part of our maven release etc. Doxia-maven-plugin seemed > like the way to go, but the last release is extremely old and not working > with the current maven 3 release. > > I would suggest that either update the plugin or remove the guides using > the plugin here: > https://maven.apache.org/doxia/book/index.html > > If you are looking for contributors, I'd be happy to take a look at it. You are better off with the asciidoctor-maven-plugin. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M11. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M11 ** Dependency upgrade * [MSHARED-1379] - Upgrade to Doxia 2.0.0-M10 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven SCM 2.1.0 released
The Apache Maven team is pleased to announce the release of the Apache Maven SCM, version 2.1.0. https://maven.apache.org/scm/ Release Notes - Maven SCM - Version 2.1.0 ** Bug * [SCM-914] - InfoItem.lastChangedDate is leaky abstraction * [SCM-939] - Assume SCM is present * [SCM-1016] - Build fails with JDK21 * [SCM-1022] - jgit push failure is not failing the build * [SCM-1024] - maven-scm-plugin tests do not properly check for existence of svn command ** Dependency upgrade * [SCM-1017] - Update commons-io:commons-io to 2.16.0 * [SCM-1018] - Require Maven 3.6.3+ * [SCM-1019] - Update org.codehaus.plexus:plexus-classworlds to 2.8.0 * [SCM-1020] - Update org.apache.commons:commons-text 1.11.0 * [SCM-1021] - Update org.apache.commons:commons-lang3 3.14.0 * [SCM-1023] - Upgrade components Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia version 2.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia, version 2.0.0-M10 https://maven.apache.org/doxia/ Release Notes - Maven Doxia - Version 2.0.0-M10 ** Bug * [DOXIA-724] - Sink pipeline returned by AbstractParser.getWrappedSink(...) has wrong order * [DOXIA-726] - MarkdownSink: Incorrect escaping of <,>,",' and & * [DOXIA-727] - MarkdownSink: Incorrect escaping inside code spans * [DOXIA-734] - XHTML 1.0 elements/attributes which are obsolete in XHTML5 no longer detected by XdocParser/FmlParser ** Improvement * [DOXIA-723] - Optionally expose document location in Sink * [DOXIA-728] - MarkdownSink: Support blockquotes * [DOXIA-730] - Update Asciidoctor Doxia Modules in doxia-site * [DOXIA-731] - Simplify HTML emitted from Sink.verbatim(...) * [DOXIA-732] - Do not fail for duplicate anchor names ** Dependency upgrade * [DOXIA-735] - Upgrade commons-io:commons-io to 2.16.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Changing site output location using system property
On 2024/03/27 21:23:30 Louis Bourdages wrote:
> Hi,
>
> I'm trying to generate a failsafe report in a different location than the
> standard one. Since this is to be used in a generic CI pipeline, I want to
> avoid having to modify the plugin config in every repo.
>
> I found this page which shows a system property that would appear to do
> exactly what I need:
> https://maven.apache.org/surefire/maven-surefire-report-plugin/examples/report-custom-location.html
>
> I have however been unable to reproduce the behaviour. Running `mvn
> surefire-report:report -DoutputDirectory=newpath` as per the example still
> generates the reports in their normal location (`${basedir}/target/site`). Is
> this documentation page outdated? Is there any way I can change the output
> directory without requiring modifications in every repo?
>
> I am using Maven 3.9.1 and surefire-report 3.2.5.
There are a few issues here, first of all use the lastest patch version of your
minor Maven version.
The parameter you are trying to set is read-only:
https://github.com/apache/maven-reporting-impl/blob/967e756d41c00c123c5c545676b5bffd35918970/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java#L79-L80
the next major version of maven-reporting-impl will fix this:
https://github.com/apache/maven-reporting-impl/blob/8464ab92499b37677eadf60ef4661bd9c847b0ac/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java#L87-L88
If you are truly curious please build Surefire from this branch and try again:
https://github.com/apache/maven-surefire/tree/doxia-2.0.0
Let me know,
Michael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [DISCUSS] Maven Dependency Plugin
Many downstream package maintainers use :go-offline to build packages offline in a container w/o outbound network access. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to suppress meta tags 'generator', 'date' in Doxia Site Renderer?
Yes, read here please: https://lists.apache.org/thread/vj7twmhm4b10zk0smko4tw8b4klto4bj On 2024/03/09 08:26:10 Alexander Kriegisch wrote: > I would have mentioned Asciidoctor, had I believed that it was related > to the problem. Besides, the Doxia version in the 'generator' tag is > Doxia-related and so is the 'date' one. So, it came as somewhat of a > surprise that Asciidoctor, while not messing with the former, overrules > the setting for the latter, because it has its own timestamp setting. > That it has it makes sense, because it is also a stand-alone docs > generator with Doxia out of the picture. That setting just happens to > write the identical tag. It was hard to diagnose, so it took me a while. > > Do you think, you can do something about making the Doxia version or the > whole 'generator' tag optional? > > Regards > -- > Alexander Kriegisch > https://scrum-master.de > > > Michael Osipov schrieb am 08.03.2024 um 20:48: > > On 2024/03/07 10:24:07 Alexander Kriegisch wrote: > >> Thanks, Michael, > >> > >> for challenging my problem description and asking for a reproducer. When > >> trying to reproduce in a green-field project, skipGenerationDate=true > >> was actually enough to suppress the timestamp meta tag on pages in > >> default formats. As soon, however, as HTML pages generated from asciidoc > >> sources using asciidoctor-maven-plugin come into play, the pages will > >> contain timestamps. I think, I will investigate further in that > >> direction about why that happens and whether it can be suppressed. > > > > You should have mentioned Asciidoctor much much earlier then I would have > > told you that it completely circumvents the Doxia Sink API and does its own > > thing with direct passthrough. Therefore, the output is out of our control. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to suppress meta tags 'generator', 'date' in Doxia Site Renderer?
On 2024/03/07 10:24:07 Alexander Kriegisch wrote: > Thanks, Michael, > > for challenging my problem description and asking for a reproducer. When > trying to reproduce in a green-field project, skipGenerationDate=true > was actually enough to suppress the timestamp meta tag on pages in > default formats. As soon, however, as HTML pages generated from asciidoc > sources using asciidoctor-maven-plugin come into play, the pages will > contain timestamps. I think, I will investigate further in that > direction about why that happens and whether it can be suppressed. You should have mentioned Asciidoctor much much earlier then I would have told you that it completely circumvents the Doxia Sink API and does its own thing with direct passthrough. Therefore, the output is out of our control. Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to suppress meta tags 'generator', 'date' in Doxia Site Renderer?
On 2024/03/02 06:44:17 Alexander Kriegisch wrote: > Michael, > > did you read my original message? Everything is described quite > precisely and concisely there. > > > I already use this in my site.xml: > > > > > > > > true > > > > > > > > Unfortunately, I found no way to suppress these generated tags on each > > single page: > > > > > > > > I.e., that setting does *not* stop timestamp meta tags from being > generated, only timestamps visible on generated pages. This is why the > subject of this thread is: "How to suppress meta tags 'generator', > 'date' in Doxia Site Renderer?" I was asking, because I was hoping that > somebody could tell me if there were any existing options to suppress > those meta tags. If you know one, your insights are most welcome. > Please, just tell me what I missed and which setting to tweak to > suppress the tag(s). Please provide a sample project for the "date" issue. I does not compile for me logically. Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to suppress meta tags 'generator', 'date' in Doxia Site Renderer?
On 2024/03/01 15:34:42 Alexander Kriegisch wrote: > Sorry for replying slowly due to intercontinental travel. > > What sebb said is just one issue. The other, even more obviuous one is > that a timestamp is a tinmestamp is a timestamp and hence therefore > changes each time I generate the site. Which exact? The generation date can be skipped, there are no other skin-supplied dates or timestamps embedded. M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to suppress meta tags 'generator', 'date' in Doxia Site Renderer?
On 2024/02/28 14:01:42 sebb wrote: > On Wed, 28 Feb 2024 at 13:40, Michael Osipov wrote: > > > > On 2024/02/22 06:59:01 Alexander Kriegisch wrote: > > > Hello Maven community. > > > > > > When generating Maven sites, I like to keep the diffs to previous > > > version to the absolute minimum before committing changes to a published > > > site. My commits should only contain content changes. Therefore, I > > > already use this in my site.xml: > > > > > > > > > > > > true > > > > > > > > > > > > Unfortunately, I found no way to suppress these generated tags on each > > > single page: > > > > > > > > > > > > > > > They constitute about 90% of my commit diffs, making it look like all > > > pages have changed in the commit log, even though maybe I just fixed a > > > typo on a single page. How can I customise that behaviour? > > > > I do not fully understand which problem you have. As long as you stay on > > the same version of all affected components there should be no diff, but > > only your content change. Can you elaborate? What do you exactly change? > > Suppose you release version 1.2.2 of a project using Doxia 1.11.0 > Later you would like to release version 1.2.3, by then Doxia 1.11.1 is out. > > As part of checking the release, you would like to check that the > Javadoc changes properly reflect the code changes. > However the Doxia version change generates tons of spurious output. True, that is what I wanted to hear. I have/had the same problem during dev/testing. Raise an issue with the skin, please. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to suppress meta tags 'generator', 'date' in Doxia Site Renderer?
On 2024/02/22 06:59:01 Alexander Kriegisch wrote: > Hello Maven community. > > When generating Maven sites, I like to keep the diffs to previous > version to the absolute minimum before committing changes to a published > site. My commits should only contain content changes. Therefore, I > already use this in my site.xml: > > > > true > > > > Unfortunately, I found no way to suppress these generated tags on each > single page: > > > > > They constitute about 90% of my commit diffs, making it look like all > pages have changed in the commit log, even though maybe I just fixed a > typo on a single page. How can I customise that behaviour? I do not fully understand which problem you have. As long as you stay on the same version of all affected components there should be no diff, but only your content change. Can you elaborate? What do you exactly change? The source of that metadata is stable from: * https://github.com/apache/maven-fluido-skin/blob/7cb683f5505badcb7ecac9569c8445ae435377d8/src/main/resources/META-INF/maven/site.vm#L20-L43 * https://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/index.html M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Configuring canonical URL link elements for maven-site-plugin generated pages
If you use the Maven Fluido Skin /site/body/head is passed to Velocity's RenderTool with '#eval()' and eventuall VTL markup will be rendered. Logically, you should have access to all context attributes including the HTML page name and all other stuff. Give it a try. M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M10. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M10 ** Task * [MSHARED-1326] - Improve (documentation on) MavenReport interface/AbstractMavenReport class ** Dependency upgrade * [MSHARED-1349] - Upgrade to Doxia 2.0.0-M9 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Plugin Tools 3.11.0 released
The Apache Maven team is pleased to announce the release of the Apache Maven Plugin Tools, version 3.11.0. https://maven.apache.org/plugin-tools/ Release Notes - Maven Plugin Tools - Version 3.11.0 ** Bug * [MPLUGIN-496] - Translation for keys report.plugin.goal.yes,no are missing * [MPLUGIN-499] - Deprecate descriptions are missing in description table ** Improvement * [MPLUGIN-450] - Make goal prefix mandatory by default * [MPLUGIN-474] - Improve descriptor docs for requiredJavaVersion * [MPLUGIN-492] - Documentation for plugins in general: Goals comprises more than that * [MPLUGIN-495] - WARNINGs based on usage of @Component for MavenSession/MavenProject instead of @Parameter ** Task * [MPLUGIN-493] - Consistently evaluate skip parameter in MavenReport#canGenerateReport() * [MPLUGIN-498] - Move section rendering to separate methods ** Dependency upgrade * [MPLUGIN-494] - Upgrade to Parent 41 * [MPLUGIN-497] - Upgrade components Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia version 2.0.0-M9 released
** Bug * [DOXIA-695] - Support of h6 in xhtml output is broken * [DOXIA-699] - Xhtml5Parser may emit sectionX() without sectionX_() when using both and * [DOXIA-714] - MarkdownSink: Fix table justification and figures * [DOXIA-715] - Sink.text(String, SinkEventAttributes) not properly supported by AptSink and MarkdownSink ** New Feature * [DOXIA-722] - Optionally create anchors for indexable entries (used in TOC macro) ** Improvement * [DOXIA-709] - Clarify usage of overlapping Sink methods * [DOXIA-711] - Introduce SinkWrapper with factory * [DOXIA-716] - Update and unify XMLReader creation and configuration ** Dependency upgrade * [DOXIA-717] - Upgrade to org.codehaus.plexus:plexus-testing 1.3.0 * [DOXIA-719] - Properly manage Commons IO/Lang 3 * [DOXIA-720] - Upgrade to Parent 41 * [DOXIA-721] - Upgrade to JUnit 5.10.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Surefire 3.2.5 released
The Apache Maven team is pleased to announce the release of the Maven Surefire version 3.2.5. https://maven.apache.org/surefire/ Release Notes - Maven Surefire - Version 3.2.5 ** Bug * [SUREFIRE-2223] - Surefire evaluates parameter jvm before skip * [SUREFIRE-2224] - StatelessXmlReporter#getTestProblems() does not properly reflect report schema structure * [SUREFIRE-2225] - Surefire ITs fail when project directory contains space * [SUREFIRE-2229] - [REGRESSION] SUREFIRE-2224 causes stack trace to be omitted for errors and failures * [SUREFIRE-2231] - JaCoCo 0.8.11 fails with old TestNG releases on Java 17+ ** Improvement * [SUREFIRE-1345] - Support flakyFailure and flakyError in TestSuiteXmlParser * [SUREFIRE-2221] - Document minimum supported Java version for Toolchains Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven JXR 3.3.2 released
The Apache Maven team is pleased to announce the release of the Apache Maven JXR version 3.3.2 This module generates browsable HTML pages from Java source code. https://maven.apache.org/jxr/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jxr-plugin 3.3.2 Release Notes - Maven JXR - Version 3.3.2 ** Bug * [JXR-183] - Plugin Documentation not generated ** Task * [JXR-185] - Consistently evaluate skip parameter in MavenReport#canGenerateReport() ** Dependency upgrade * [JXR-186] - Upgrade to Parent 41 * [JXR-187] - Upgrade components Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M13 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M13. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M13 ** Bug * [MSITE-997] - Non-localized site directory DocumentRenderingContext passed * [MSITE-998] - MavenReport#setReportOutputDirectory(File) is called too late ** Dependency upgrade * [MSITE-999] - Upgrade plugins and components (in ITs) Please also note for this new major version: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M13 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M13. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M13 ** Improvement * [MSHARED-1327] - Change default value of output directory in AbstractMavenReport * [MSHARED-1343] - Make parameter outputDirectory read/write in AbstractMavenReport ** Dependency upgrade * [MSHARED-1342] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Surefire 3.2.3 released
The Apache Maven team is pleased to announce the release of the Maven Surefire version 3.2.3. https://maven.apache.org/surefire/ Release Notes - Maven Surefire - Version 3.2.3 ** Bug * [SUREFIRE-2210] - Additional class path ordering broken since 3.2.0 * [SUREFIRE-2211] - additionalClasspathElement with UNC path not working with Maven Failsafe Plugin * [SUREFIRE-2212] - OutOfMemoryError raised when parsing files with huge stderr/stdout output in surefire-report-parser * [SUREFIRE-2220] - SurefireForkChannel#getForkNodeConnectionString() returns invalid URI string if localHost resolves to IPv6 address ** Dependency upgrade * [SUREFIRE-2214] - Upgrade to HtmlUnit 3.8.0 * [SUREFIRE-2215] - Upgrade to Parent 41 * [SUREFIRE-2216] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: creating a source directory on the fly
On 2023/12/06 03:34:58 Dave Dyer wrote: > > I'm trying to tune up my maven build, which requires that I construct > a source directory on the fly by copying from the canonical location. > > The best advice I've found is to use mavin-resources-plugin, but > that's a bit inelegant because it copies everything, not just the > sources. That the wrong approach. > Is there a better approach? The right approach: https://www.mojohaus.org/build-helper-maven-plugin/add-source-mojo.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Javadoc Plugin 3.6.3 released
The Apache Maven team is pleased to announce the release of the Maven Javadoc Plugin, version 3.6.3. This module generates browsable HTML pages from Java source code. https://maven.apache.org/plugins/maven-javadoc-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-javadoc-plugin 3.6.3 Release Notes - Maven Javadoc Plugin - Version 3.6.3 ** Bug * [MJAVADOC-682] - Reactor builds fail when multiple modules with same groupId:artifactId, but different versions * [MJAVADOC-780] - Unit tests create null-null.jar in build root directory ** Improvement * [MJAVADOC-779] - Upgrade maven-plugin parent to 41 ** Task * [MJAVADOC-782] - Align read-only parameters naming with other plugins ** Dependency upgrade * [MJAVADOC-781] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generate soft-links as part of site build
On 2023/11/28 17:35:40 sebb wrote: > Is it possible to generate soft-links as part of a site build? > > I tried adding them to the resources/ folder, but they were ignored. While I haven't tried explicitly, what about https://github.com/apache/maven-site/blob/c9e53bb488964ec2236688db41f9ddc90e642702/pom.xml#L246-L264? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M12. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M12 ** Improvement * [MSITE-987] - Consistently log when skipping report goal execution ** Task * [MSITE-996] - Rewrite site.xml in ITs for new site model ** Dependency upgrade * [MSITE-991] - Upgrade to Parent 41 * [MSITE-992] - Upgrade to Doxia Sitetools 2.0.0-M16 * [MSITE-993] - Upgrade to Maven Reporting API 4.0.0-M9 * [MSITE-994] - Upgrade to Maven Reporting Exec 4.0.0-M12 * [MSITE-995] - Upgrade plugins and components (in ITs) Please also note for this new major version: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M12. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M12 ** Improvement * [MSHARED-1329] - Add field to MavenReportExecution whether it is user-defined or autodetected ** Dependency upgrade * [MSHARED-1334] - Upgrade to Parent 41 * [MSHARED-1335] - Upgrade to Maven Reporting API 4.0.0-M9 * [MSHARED-1337] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M12. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M12 ** Improvement * [MSHARED-1328] - Consistently log when skipping report goal execution ** Task * [MSHARED-1326] - Improve MavenReport interface/AbstractMavenReport class API ** Dependency upgrade * [MSHARED-1334] - Upgrade to Parent 41 * [MSHARED-1335] - Upgrade to Maven Reporting API 4.0.0-M9 * [MSHARED-1336] - Upgrade to Doxia Sitetools 2.0.0-M16 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: .sha256 artifact checksums on Central
Look at this: https://repo.maven.apache.org/maven2/com/microsoft/sqlserver/mssql-jdbc/12.4.2.jre11/ Whatever they did, they did wrong. It is pointless to upload hashes for signatures. Moreover, MD5 and SHA1 are missing. They are mandatory, at least on oss.sonatype.org. They have just failed. Good luck in complaining: The pom.properties says: #Created by Apache Maven 3.8.1 artifactId=mssql-jdbc groupId=com.microsoft.sqlserver version=12.4.2 Can't stop laughing... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia Sitetools 2.0.0-M16 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M16 https://maven.apache.org/doxia/doxia-sitetools/ Release Notes - Maven Doxia Sitetools - Version 2.0.0-M16 ** Task * [DOXIASITETOOLS-319] - Improve DocumentRenderer interface/DocumentRenderingContext class API ** Dependency upgrade * [DOXIASITETOOLS-317] - Upgrade to Parent 41 * [DOXIASITETOOLS-318] - Upgrade to Maven Reporting API 4.0.0-M9 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Project Info Reports Plugin 3.5.0 released
The Apache Maven team is pleased to announce the release of the Maven Project Info Reports Plugin version 3.5.0. https://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-project-info-reports-plugin 3.5.0 Release Notes - Maven Project Info Reports Plugin - Version 3.5.0 ** Task * [MPIR-453] - Replace Commons IO in favor of standard APIs ** Dependency upgrade * [MPIR-446] - Update to Maven SCM 2.0.1 * [MPIR-452] - Upgrade to Parent 41 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M9 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M9. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M9 ** Task * [MSHARED-1326] - Improve (documentation on) MavenReport interface/AbstractMavenReport class ** Dependency upgrade * [MSHARED-1334] - Upgrade to Parent 41 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Javadoc Plugin 3.6.2 released
The Apache Maven team is pleased to announce the release of the Maven Javadoc Plugin, version 3.6.2. This module generates browsable HTML pages from Java source code. https://maven.apache.org/plugins/maven-javadoc-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-javadoc-plugin 3.6.2 Release Notes - Maven Javadoc Plugin - Version 3.6.2 ** Bug * [MJAVADOC-713] - Skipping Javadoc reportset leaves empty Javadoc link in site * [MJAVADOC-716] - The stale file detection does not work * [MJAVADOC-726] - Maven Java Doc Plugin downloads Log4j-1.2.12 dependency transitively * [MJAVADOC-762] - createTestRepo in JavaDocReportTest shares state * [MJAVADOC-774] - 3.6.0 release is not reproducible ** Improvement * [MJAVADOC-730] - Deprecate parameter "old" ** Dependency upgrade * [MJAVADOC-777] - Update org.codehaus.plexus:plexus-java from 1.1.2 to 1.2.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven PMD Plugin 3.21.2 released
The Apache Maven team is pleased to announce the release of the Maven PMD Plugin version 3.21.2. https://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.21.2 Release Notes - Maven PMD Plugin - Version 3.21.2 ** Bug * [MPMD-370] - Remove remaining uses of FileReader * [MPMD-371] - Using two ruleset files with same name in different directories * [MPMD-382] - Regression in report rendering * [MPMD-384] - maven-pmd-plugin is dowloading transitive dependencies of unmanaged version ** Dependency upgrade * [MPMD-380] - Prefer apache commons and JDK to Plexus utils * [MPMD-387] - Upgrade to Parent 40 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to set default directories when developing a reporting plugin?
On 2023/10/22 02:38:07 Alexander Kriegisch wrote:
> Hello Michael, hello community.
>
> I have decided to actually change the plugin's behaviour the way I
> described:
>
> -- I overrode the default value of AbstractMavenReport.outputDirectory
> [1] by defining a setter method and adding a @Parameter annotation,
> specifying ${project.build.directory} as the base direcory for the
> report, because this is what I want to use when the mojo is
> executed directly. The abstract super class defaults to
> ${project.reporting.outputDirectory}, which is IMO suboptimal. In a
> site generation context, the report directory is set automatically
> anyway, because AbstractMavenReport.setReportOutputDirectory, as
> mentioned in my original message, sets both reportOutputDirectory
> and outputDirectory. BTW, is this "trick" to override an inherited
> property correct? Is there a canonical way to do that?
>
> -- Then, I introduced a new reportDirectory [2] property, whis is just
> a String, not a File. It specifies the subdirectory to be appended
> to outputDirectory [3]. This works in both use cases, stand-alone
> mojo execution and site generation.
>
> -- Hence, it is now possible to configure the base directory and the
> subdirectory name separately: The base directory is set in the
> identically named property outputDirectory, either in the plugin or
> in Maven Site, depending on the use case. The subdirectory is set
> in the new reportDirectory property. I.e., reports will end up in
> the following directories:
>** without configuration, stand-alone:
> target/aspectj-report
>** without configuration, site generation:
> target/site/aspectj-report
>** custom base directory, stand-alone: e.g.
> my-target/aspectj-report
>** custom base directory, site generation: e.g.
> target/my-site/aspectj-report
>** custom subdirectory, stand-alone: e.g.
> target/my-aspectj-report
>** custom subdirectory, site generation: e.g.
> target/site/my-aspectj-report
>** custom base + subdirectory, stand-alone: e.g.
> my-target/my-aspectj-report
>** custom base + subdirectory, site generation: e.g.
> target/my-site/my-aspectj-report
> Notably, the custom base directory for site generation should work
> for all plugins playing nicely, e.g. Javadoc or (now after my
> change) AspectJ. See the integration tests [4] for examples, namely
> CreateReport* test cases for stand-alone and CreateSite* ones for
> site generation use cases. For each test case, compare the
> differences in Maven Site and AspexctJ Maven settings and the
> corresponding checks in verify.groovy.
>
> [1]
> https://github.com/dev-aspectj/aspectj-maven-plugin/blob/9f2d0e97ed963c2b69a7fdf731a4c919a6bb56ef/src/main/java/org/codehaus/mojo/aspectj/AjcReportMojo.java#L90-L106
> [2]
> https://github.com/dev-aspectj/aspectj-maven-plugin/blob/9f2d0e97ed963c2b69a7fdf731a4c919a6bb56ef/src/main/java/org/codehaus/mojo/aspectj/AjcReportMojo.java#L57-L67
> [3]
> https://github.com/dev-aspectj/aspectj-maven-plugin/blob/9f2d0e97ed963c2b69a7fdf731a4c919a6bb56ef/src/main/java/org/codehaus/mojo/aspectj/AjcReportMojo.java#L255
> [4] https://github.com/dev-aspectj/aspectj-maven-plugin/tree/main/src/it
Just checked these. They look reasonable. I need to check MJAVADOC whether it
is reasonable or not. Let's continue with the open PRs.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Surefire 3.2.1 released
Good catch. This crept in in other builds as well :-(
On 2023/10/24 10:42:33 Thomas Broyer wrote:
> This is using plexus-xml 4.0.0 (from Parent 40). Shouldn't that be
> downgraded to 3.0.0?
> (
> https://github.com/apache/maven-parent/commit/096de2d1f79a1b692a112db16675ecc2ac013597
> says 4.0.0 is not compatible with Maven 3; maybe a Parent 41 should have
> been released after that commit?)
>
> Fwiw, I have a plugin that depends on surefire-common (maybe it shouldn't
> but that's another story) and this brings maven-xml-impl et al. that are
> flagged as not being in the correct scope (brought in as "compile", should
> be "provided"). My tests pass with that version, but I've explicitly
> downgraded to 3.0.0 (upgraded plexus-utils to 4.0.0 and added dependency on
> plexus-xml 3.0.0) and tests still pass, so I think I'm going to go with
> that.
>
> On Mon, Oct 23, 2023 at 10:00 PM Michael Osipov wrote:
>
> > The Apache Maven team is pleased to announce the release of the Maven
> > Surefire version 3.2.1.
> >
> > https://maven.apache.org/surefire/
> >
> >
> > Release Notes - Maven Surefire - Version 3.2.1
> >
> > ** Bug
> > * [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
> > surefire
> > * [SUREFIRE-2196] -
> > maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
> > braces in the pattern
> > * [SUREFIRE-2202] - NullPointerException if super class meets
> > specific condition
> >
> > ** New Feature
> > * [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
> > environmentVariables when used in parallel mvn builds
> >
> > ** Improvement
> > * [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5 versions
> > * [SUREFIRE-2178] - classpathDependencyExcludes should support
> > classifiers
> > * [SUREFIRE-2179] - additionalClasspathElements should support
> > Maven coordinates
> > * [SUREFIRE-2182] - Log starter implementation on DEBUG level
> >
> > ** Dependency upgrade
> > * [SUREFIRE-2188] - Upgrade to Parent 40
> >
> >
> > Enjoy,
> >
> > -The Apache Maven team
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
> --
> Thomas Broyer
> /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Checkstyle Plugin 3.3.1 released
The Apache Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 3.3.1. https://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins >maven-checkstyle-plugin 3.3.1 Release Notes - Maven Checkstyle Plugin - Version 3.3.1 ** Bug * [MCHECKSTYLE-403] - Goal checkstyle:checkstyle ignores testResources ** Improvement * [MCHECKSTYLE-412] - Add option to exclude generated sources/test-sources from default source/test-source directories ** Task * [MCHECKSTYLE-438] - Update and backfill release notes ** Dependency upgrade * [MCHECKSTYLE-439] - Upgrade to Parent 40 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven JXR 3.3.1 released
The Apache Maven team is pleased to announce the release of the Apache Maven JXR version 3.3.1 This module generates browsable HTML pages from Java source code. https://maven.apache.org/jxr/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jxr-plugin 3.3.1 Release Notes - Maven JXR - Version 3.3.1 ** Improvement * [JXR-175] - Support Java 14 record as class type in cross reference * [JXR-176] - Remove dependency org.apache.commons:commons-lang3 ** Dependency upgrade * [JXR-177] - Upgrade Plexus Utils to 3.5.0 * [JXR-178] - Update parent pom to 39 * [JXR-180] - commons-io to 2.14.0 * [JXR-181] - Upgrade to Parent 40 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Release Maven Dependency Plugin 3.6.1 released
The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.6.1. https://maven.apache.org/plugins/maven-dependency-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-dependency-plugin 3.6.1 Release Notes - Maven Dependency Plugin - Version 3.6.1 ** Bug * [MDEP-875] - Regression: list-repositories may produce NPE ** Dependency upgrade * [MDEP-868] - maven-shared-utils to 3.4.2 * [MDEP-872] - update commons-io to 2.13.0 * [MDEP-882] - Upgrade plexus-archiver due to CVE-2023-37460 * [MDEP-883] - Upgrade maven-plugin parent to 40 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Surefire 3.2.1 released
The Apache Maven team is pleased to announce the release of the Maven
Surefire version 3.2.1.
https://maven.apache.org/surefire/
Release Notes - Maven Surefire - Version 3.2.1
** Bug
* [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
surefire
* [SUREFIRE-2196] -
maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
braces in the pattern
* [SUREFIRE-2202] - NullPointerException if super class meets
specific condition
** New Feature
* [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
environmentVariables when used in parallel mvn builds
** Improvement
* [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5 versions
* [SUREFIRE-2178] - classpathDependencyExcludes should support
classifiers
* [SUREFIRE-2179] - additionalClasspathElements should support
Maven coordinates
* [SUREFIRE-2182] - Log starter implementation on DEBUG level
** Dependency upgrade
* [SUREFIRE-2188] - Upgrade to Parent 40
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: How to set default directories when developing a reporting plugin?
Alexander,
I have now read the code of all our reporting plugins,
maven-reporting-impl and maven-site-plugin.
Here is my understanding how I expect to work which it is not at the
moment and there is a flaw in the system were both MJXR and MJAVADOC
apply a hack and I will explain why they do.
We have
standalone execution:
@Parameter(defaultValue = "${project.reporting.outputDirectory}", readonly
= true, required = true)
protected File outputDirectory;
and
site execution:
@Parameter(property = "siteOutputDirectory", defaultValue =
"${project.reporting.outputDirectory}")
protected File outputDirectory;
both point to root directory where all reports put there files in, from
the simplest single page one, to multipage to those which are external
and operate in subdirectories. Everything below that output directory is
fixed and completely subject to the plugin.
Both o.a.m.reporting.AbstractMavenReport.getReportOutputDirectory() and
o.a.m.reporting.AbstractMavenReport.setReportOutputDirectory(File) exist
for the sole purpose to accomondate both execution styles. One value is
exected through DI (standalone) the other one set (through site).
Therefore, in both cases #getReportOutputDirectory() should be used to
get the right value to write to.
In any case #setReportOutputDirectory(File) does *not* contain a
directory for the reporting plugin only, but for the entire generated
tree of plugins, regardless of 'mvn site' /or/ 'mvn pmd:pmd
checkstyle:checkstyle'.
Now, o.a.m.reporting.MavenReport.getOutputName() has bad documentation
because it is actually a relative output *path* to the generated item
with the base/root path given by
o.a.m.reporting.MavenReport.getReportOutputDirectory(). Again, here is
the name completely deceiving. Needs doc update as well.
You might wonder, what to do now with:
@Override
public String getOutputName() {
return "xref/index";
}
and
@Override
public void setReportOutputDirectory(File reportOutputDirectory) {
if ((reportOutputDirectory != null)
&& (!reportOutputDirectory.getAbsolutePath().endsWith("xref")))
{
this.destDir = new File(reportOutputDirectory,
"xref").getAbsolutePath();
} else {
this.destDir = reportOutputDirectory.getAbsolutePath();
}
}
?
Well, while I consider the former is correct, the latter is not:
* Does one expect to pass *null* as reportOutputDirectory?
* Why is *this.reportOutputDirectory* never updated?
* It expects the report this live under *.../xref*, but ignores
/**
* Folder where the Xref files will be copied to.
*/
@Parameter(defaultValue = "${project.reporting.outputDirectory}/xref")
private String destDir;
* It mixes the the notion of a *pluginReportOutputDirectory* which is
passed to the external report generator as a root/base or a multi sink
if you want to generate multiple reports under one dir, but have the
starting point at *foo/index* (output name) and all resides under *foo/*.
MJAVADOC does the same trick although it has replaces the literal 'xref'
with a field, but the issue remains the same.
Whether the path component(s) between the root and *index* should be
flexible, is upto the plugin (e.g, xref, xref-test, apidocs, etc.), but
from my personal PoV changing it does not make:
* In site execution this has to be carried along
* If you need to change it otherwise you can rename/move it with an ant
task or a subprocessor.
What I will do not is to create a few issues and PRs to improve the
situation and create a PR for JXR on top of 'doxia-2.0.0' how I consider
it should be. Some of the method names are unfortunately, but I am
afraid it is too hard to change them given they have too widespread use.
I guess after all, I will need to perform another round of releases with
those PRs before I can start new reporting plugin releases. I think what
you have raised was long overdue and absoltuely legit.
Let me know what you think!
@Hervé, I would also appreciate to hear your opinion on this!
Michael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: How to set default directories when developing a reporting plugin?
On 2023/10/20 02:08:25 Alexander Kriegisch wrote:
Hello.
I am trying to improve a reporting mojo in a Maven plugin. The mojo
extends org.apache.maven.reporting.AbstractMavenReport. I recently
upgraded it to Doxia 2.0 - thanks again to Hervé B. and Michael O. for
their support - and cleaned out some cruft, removing redundant super
class fields and methods) in the mojo code. So far, so good.
My question is about the different behaviour for configuring the report
output directory when starting the mojo directly as a Maven goal
compared to it being started during Maven site generation. The Javadoc
is helpful and explains:
public abstract class AbstractMavenReport extends AbstractMojo
implements MavenMultiPageReport
{
/**
* The output directory for the report. Note that this parameter is
* only evaluated if the goal is run directly from the command line.
* If the goal is run indirectly as part of a site generation, the
* output directory configured in the Maven Site Plugin is used
* instead.
*/
@Parameter(defaultValue = "${project.reporting.outputDirectory}",
readonly = true, required = true)
protected File outputDirectory;
I.e., if the user sets the directory as a plugin option, she is fine
when using the plugin directly. If she uses it as a reporting plugin for
site generation, she needs to set 'outputDirectory' in Maven Site
Plugin. But actually, that is not the right approach, because my
understanding is that 'outputDirectory' should rather set a base
directory for *all* reporting plugins, if the default target/site is not
OK. In that case, any plugin-specific output directory ought to be
interpreted as a subdirectory of the general reporting
'outputDirectory', not simply be ignored. I saw that Maven Javadoc
Plugin has some logic that seems to handle that, using a separate
'destDir' property to recalculate the output directory in a reporting
context. From class JavadocReport:
/**
* @param theDestDir the destination directory
*/
public void setDestDir(String theDestDir) {
this.destDir = theDestDir;
updateReportOutputDirectory(reportOutputDirectory, theDestDir);
}
private void updateReportOutputDirectory(File reportOutputDirectory,
String destDir)
{
if (reportOutputDirectory != null
&& destDir != null
&& !reportOutputDirectory.getAbsolutePath().endsWith(destDir))
{
this.reportOutputDirectory =
new File(reportOutputDirectory, destDir);
} else {
this.reportOutputDirectory =
reportOutputDirectory;
}
}
Different Maven plugins seem to handle this situation differently. Is
this the suggested, canonical approach? What do you think is a user's
expectation for multi-page report mojos extending AbstractMavenReport?
Certainly not that three conflicting reporting plugins have to argue
about which one can use Maven Site's 'outputDirectory' proprty for its
private purposes, leaving the other reporting plugins falsely
configured. Do all reporting plugins need to provide a separate
'destDir' or 'reportingDir' property for that use case? WDYT?
Sorry for asking a long-winded question, but I think it is important for
me to provide some context for the benefit of everyone trying to answer.
This is, indeed, a good question. I have stumbled about similar during
Doxia 2.0.0 work, but didn't dare to touch it because I didn't want to
open too many construction sites. Let me go through to get a better
understanding.
Regarding Javadoc Plugin: I don't know whether is the perfect external
reporting plugin because it does not inherit from AbstractMavenReport.
M
[ANN] Apache Maven Plugin Tools 3.10.1 released
The Apache Maven team is pleased to announce the release of the Apache Maven Plugin Tools, version 3.10.1. https://maven.apache.org/plugin-tools/ Release Notes - Maven Plugin Tools - Version 3.10.1 ** Bug * [MPLUGIN-482] - JavadocSite.createLink() does not consider implicit module path prefix ** Improvement * [MPLUGIN-442] - Rewrite plugin goal documentation generation to use supplied sink instead of direct Xdoc * [MPLUGIN-475] - Upgrade to plexus-utils / plexus-xml 4.0.0 * [MPLUGIN-477] - Don't add a stray period ** Dependency upgrade * [MPLUGIN-478] - Upgrade org.junit:junit-bom from 5.9.3 to 5.10.0 * [MPLUGIN-479] - Bump org.codehaus.plexus:plexus-archiver from 4.7.1 to 4.8.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M11. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M11 ** Dependency upgrade * [MSHARED-1322] - Upgrade to Doxia 2.0.0-M8 * [MSHARED-1323] - Upgrade to Maven Reporting API 4.0.0-M8 * [MSHARED-1324] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia Sitetools 2.0.0-M13 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M13 https://maven.apache.org/doxia/doxia-sitetools/ Release Notes - Maven Doxia Sitetools - Version 2.0.0-M13 ** Dependency upgrade * [DOXIASITETOOLS-314] - Upgrade to Doxia 2.0.0-M8 * [DOXIASITETOOLS-315] - Upgrade to Maven Fluido Skin 2.0.0-M8 in default site descriptor * [DOXIASITETOOLS-316] - Upgrade to Maven Reporting API 4.0.0-M8 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M8. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M8 ** Dependency upgrade * [MSHARED-1316] - Upgrade to Parent 40 * [MSHARED-1317] - Upgrade to Doxia 2.0.0-M8 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M11. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M11 ** Dependency upgrade * [MSITE-981] - Upgrade to Doxia 2.0.0-M8 * [MSITE-982] - Upgrade to Doxia Sitetools 2.0.0-M13 * [MSITE-983] - Upgrade to Maven Reporting API 4.0.0-M8 * [MSITE-984] - Upgrade to Maven Reporting Impl/Exec 4.0.0-M11 * [MSITE-985] - Upgrade plugins and components (in ITs) Please also note for this new major version: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M11. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M11 ** Improvement * [MSHARED-1314] - mark execute() final to avoid users extending reporting-impl implementation ** Dependency upgrade * [MSHARED-1318] - Upgrade to Doxia 2.0.0-M8 * [MSHARED-1319] - Upgrade to Doxia Sitetools 2.0.0-M13 * [MSHARED-1320] - Upgrade to Maven Reporting API 4.0.0-M8 * [MSHARED-1321] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia version 2.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia, version 2.0.0-M8 https://maven.apache.org/doxia/ Release Notes - Maven Doxia - Version 2.0.0-M8 * Bug * [DOXIA-706] - Sink.text(String, SinkEventAttributes) not properly supported by Xhtml5BaseSink ** Dependency upgrade * [DOXIA-708] - Upgrade to Parent 40 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-doxia-sitetools] How to upgrade from old pre-version 2.0.0 model?
On 2023/10/15 17:50:15 Dave Wichers wrote: > Hello, > > I'm looking at this: > https://www.mail-archive.com/commits@maven.apache.org/msg114005.html > > And see the code change introducing this warning: > > +LOGGER.warn( > +"Site model of '" + project.getId() + "' for " > ++ (locale.equals(SiteTool.DEFAULT_LOCALE) > +? "default locale" > +: "locale '" + locale + "'") > ++ " is 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!"); > > > I have a project that is getting this warning, but I have no clue how > to address it. Is there a migration guide for Doxia for this? Or can > you explain to me how to address it? I imagine a number of people are > going to see this message, so a guide that people can easily find that > explains how to deal with it would be very helpful. Dave, you first should look in JIRA at all associated issues to understand the purpose of this change. Then the model (old and new one), are generated from a Modello model which generates a documentatation: * old: https://maven.apache.org/doxia/doxia-sitetools/doxia-site-model/decoration.html * new: https://maven.apache.org/doxia/doxia-sitetools/doxia-site-model/site.html then you can map from old to new easily. The change in Doxia Sitetools also contains a converter which can assist you as well, if the model overview is not sufficient. If you are looking for handwritten documentation, there is none yet. We are always short in docs. I am the only one basically working on this topic for almost two years. Let me know if this answers your question, Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Fluido Skin 2.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Fluido Skin, version 2.0.0-M8. https://maven.apache.org/skins/maven-fluido-skin/ You should specify the version in your project's site configuration: org.apache.maven.skins maven-fluido-skin 2.0.0-M8 Import: This release requires Maven Site Plugin 4.0.0-M10/Doxia Sitetools 2.0.0-M12 to run Release Notes - Maven Fluido Skin - Version 2.0.0-M8 ** Bug * [MSKINS-235] - wrong META-INF/LICENSE and META-INF/NOTICE in release jar ** Improvement * [MSKINS-170] - Allow to show name as headline in addition to bannerLeft ** Task * [MSKINS-237] - Rework skin for new site model ** Dependency upgrade * [MSKINS-238] - Upgrade to Parent 40 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: NPE in AbstractMavenReport.execute, because 'this.siteTool' is null
I had these NPEs when I started to migrate reporting plugins and both the plugin and the super class contained the same fields which created conflicts. After I have removed them from the plugin and used the super ones all went fine. In your case I would really do what Hervé proposes: * remove your execute() and retest with 1.x * in a branch try with 2.x I expect it to work. You can also look at all of your reporting plugins in branch doxia-2.0.0 you'll see all necessary migration magic from me. The PR with finalizing the method is good and already merged. M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Maven
Site Plugin, version 4.0.0-M10.
https://maven.apache.org/plugins/maven-site-plugin/
Release Notes - Maven Site Plugin - Version 4.0.0-M10
** Bug
* [MSITE-971] - Site generation not resolving git.commit.time
** Improvement
* [MSITE-973] - Have ${project.build.outputTimestamp} injected as
@Parameter
** Task
* [MSITE-975] - Use injected only properties in additional template
properties
** Dependency upgrade
* [MSITE-976] - Bump plexus-archiver from 4.7.1 to 4.8.0
* [MSITE-979] - Upgrade to Parent 40
* [MSITE-980] - Upgrade plugins and components (in ITs)
Please also note for this new major version:
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M10. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M10 ** Bug * [MSHARED-1298] - Missing site report should be detected ** Dependency upgrade * [MSHARED-1310] - Upgrade to Parent 40 * [MSHARED-1311] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia Sitetools 2.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M12 https://maven.apache.org/doxia/doxia-sitetools/ Release Notes - Maven Doxia Sitetools - Version 2.0.0-M12 ** Improvement * [DOXIASITETOOLS-253] - Clarify "border", "width" and "height" for Banner and LinkItem ** Wish * [DOXIASITETOOLS-174] - rename site.xml root tag from "project" to "site" ** Task * [DOXIASITETOOLS-254] - Clarify inconsistencies in Doxia site model * [DOXIASITETOOLS-311] - Rework and simplify the site model ** Dependency upgrade * [DOXIASITETOOLS-312] - Upgrade to Parent 40 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Maven
Reporting Impl version 4.0.0-M10.
https://maven.apache.org/shared/maven-reporting-impl/
Release Notes - Maven Shared Components - Version
maven-reporting-impl-4.0.0-M10
** Improvement
* [MSHARED-1295] - Have ${project.build.outputTimestamp} injected
as @Parameter
** Dependency upgrade
* [MSHARED-1308] - Upgrade to Parent 40
* [MSHARED-1309] - Upgrade to Doxia Sitetools 2.0.0-M12
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: NPE in AbstractMavenReport.execute, because 'this.siteTool' is null
On 2023/10/05 06:46:02 Hervé Boutemy wrote: > improvement proposed: review appreciated > https://github.com/apache/maven-reporting-impl/pull/24 Will try to look at the issue here and the proposed PR in the next couple of days... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 4 doesn't allow overriding user.language
The behavior is correct. You can only pass Maven user properties to CLI, *not* Java system properties. If you want to override them, use MAVEN_OPTS for this. It is an incorrect behavior from 3.x times where the notion between user properties and system properties was not properly defined. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Fluido Skin 2.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven Fluido Skin, version 2.0.0-M7. https://maven.apache.org/skins/maven-fluido-skin/ You should specify the version in your project's site configuration: org.apache.maven.skins maven-fluido-skin 2.0.0-M7 Import: This release requires Maven Site Plugin 4.0.0-M9/Doxia Sitetools 2.0.0-M11 to run Release Notes - Maven Fluido Skin - Version 2.0.0-M7 ** Bug * [MSKINS-230] - Text in / ignore default alignment * [MSKINS-231] - site.vm contains untranslated "External Links" label * [MSKINS-233] - site-macros.vm contains untranslated "Edit" label * [MSKINS-234] - Disabling 'topBarEnabled' doesn't remove padding ** Dependency upgrade * [MSKINS-232] - Upgrade to Doxia Sitetools 2.0.0-M11 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M9 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M9. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M9 ** Improvement * [MSITE-833] - Remove dependency to maven-compat ** Task * [MSITE-965] - add system requirements history ** Dependency upgrade * [MSITE-968] - Upgrade plugins and components (in ITs) * [MSITE-969] - Upgrade to Doxia 2.0.0-M7/Doxia Sitetools 2.0.0-M11 * [MSITE-970] - Upgrade to Maven Reporting API 4.0.0-M7, Maven Reporting Impl 4.0.0-M9, Maven Reporting Exec 2.0.0-M9 Please also note for this new major version: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M9 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M9. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M9 ** Dependency upgrade * [MSHARED-1281] - Upgrade to Doxia 2.0.0-M7 * [MSHARED-1282] - Upgrade plugins and components (in ITs) * [MSHARED-1283] - Upgrade to Maven Reporting API 4.0.0-M7/Maven Reporting Impl 4.0.0-M9 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M9 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M9. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M9 ** Bug * [MSHARED-1275] - MavenReport#canGenerateReport() is invoked twice ** Dependency upgrade * [MSHARED-1277] - Upgrade plugins and components (in ITs) * [MSHARED-1278] - Upgrade to Doxia 2.0.0-M7 * [MSHARED-1279] - Upgrade to Maven Reporting API 4.0.0-M7 * [MSHARED-1280] - Upgrade to Doxia Sitetools 2.0.0-M11 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia Sitetools 2.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M11 https://maven.apache.org/doxia/doxia-sitetools/ Release Notes - Maven Doxia Sitetools - Version 2.0.0-M11 ** Task * [DOXIASITETOOLS-309] - Add resource bundle property "External Links" to site-renderer.properties * [DOXIASITETOOLS-310] - Add resource bundle property "Edit" to site-renderer.properties ** Dependency upgrade * [DOXIASITETOOLS-308] - Upgrade to Doxia 2.0.0-M7 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Fluido Skin 1.12.0 released
Am 2023-07-09 um 15:29 schrieb Jeremy Landis: Notes here state this requires site 4 plugin. Believe this one is still for site 3 plugin, correct? You are totally right. This information is incorrect. My bad, I forgot to remove the note which only applies to version 2.0. Please ignore this piece of information. Maven Site Plugin 3.x is the required version. Thanks for being vigilant! M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Fluido Skin 1.12.0 released
The Apache Maven team is pleased to announce the release of the Maven Fluido Skin, version 1.12.0. https://maven.apache.org/skins/maven-fluido-skin/ You should specify the version in your project's site configuration: org.apache.maven.skins maven-fluido-skin 1.12.0 Import: This release requires Maven Site Plugin 4.0.0-M6/Doxia Sitetools 1.12.0 to run Release Notes - Maven Fluido Skin - Version 1.12.0 ** Bug * [MSKINS-217] - CSS shall only apply to and class="verbatim"> if they are immediate children of * [MSKINS-222] - Template does not properly escape reserved XML chars * [MSKINS-224] - Ampersand gets un-escaped in menu item * [MSKINS-230] - Text in / ignore default alignment * [MSKINS-234] - Disabling 'topBarEnabled' doesn't remove padding ** Improvement * [MSKINS-212] - Simplify IT verification with more Groovy features ** Dependency upgrade * [MSKINS-216] - Fix issue with missing dependency to plexus-utils in minify-maven-plugin and Maven 3.9.x * [MSKINS-227] - Upgrade to AnchorJS 4.3.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M7. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M7 ** Improvement * [MSHARED-193] - API change: let MavenReportRenderer#render() throw an exception * [MSHARED-1032] - API change: let MavenReport#canGenerateReport() throw an exception ** Dependency upgrade * [MSHARED-1276] - Upgrade to Doxia 2.0.0-M7 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia version 2.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia, version 2.0.0-M7 https://maven.apache.org/doxia/ Release Notes - Maven Doxia - Version 2.0.0-M7 ** Bug * [DOXIA-704] - style and class attributes not merged when user-supplied in XHTML5 sink ** Task * [DOXIA-705] - Remove remaining deprecated/duplicated code Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven WAR Plugin 3.4.0 released
The Apache Maven team is pleased to announce the release of the Maven WAR Plugin version 3.4.0. https://maven.apache.org/plugins/maven-war-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-war-plugin 3.4.0 Release Notes - Maven WAR Plugin - Version 3.4.0 ** Bug * [MWAR-456] - Latest maven-war-plugin causing vulnerable .jars to be downloaded ** Improvement * [MWAR-450] - ISO8859-1 properties files get changed into UTF-8 when filtered * [MWAR-452] - One page about Skinny WARs ** Task * [MWAR-444] - Update plugin (requires Maven 3.2.5+) * [MWAR-453] - Require Java 8 * [MWAR-457] - Update plexus-utils to 3.0.24 - in its * [MWAR-465] - Empty test classes cause dependency:analyze to fail * [MWAR-466] - Refresh download page ** Dependency upgrade * [MWAR-454] - Upgrade Parent to 36 * [MWAR-458] - Update maven-filtering to version 3.3.1 * [MWAR-459] - Bump plexus-archiver to 4.7.1 * [MWAR-460] - Bump maven-archiver from 3.5.1 to 3.6.0 * [MWAR-461] - Bump commons-io from 2.6 to 2.11.0 * [MWAR-462] - Bump plexus-utils from 3.3.0 to 3.5.1 * [MWAR-463] - Upgrade Parent to 39 * [MWAR-464] - Upgrade lifecycle mapping plugins * [MWAR-467] - Upgrade components Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Invoker Plugin 3.6.0 released
The Apache Maven team is pleased to announce the release of the Maven Invoker Plugin version 3.6.0. https://maven.apache.org/plugins/maven-invoker-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-invoker-plugin 3.6.0 Release Notes - Maven Invoker Plugin - Version 3.6.0 ** Sub-task * [MINVOKER-347] - Document upcoming report file name change ** Bug * [MINVOKER-340] - AbstractInvokerMojo/InvokerReport subclasses are not thread-safe due to use of DecimalFormat ** Improvement * [MINVOKER-341] - Make elapsed time field type consistent with Maven Surefire * [MINVOKER-342] - Use ChoiceFormat to selectively render elapsed time in AbstractInvokerMojo * [MINVOKER-345] - Use ChoiceFormat to selectively render percentage and elapsed time in InvokerReportRenderer ** Task * [MINVOKER-343] - Make elapsed time rendering consistent with Maven Surefire * [MINVOKER-344] - Move reporting rendering logic into a ReportRenderer class ** Dependency upgrade * [MINVOKER-338] - Bump groovy-bom from 4.0.10 to 4.0.12 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Surefire 3.1.2 released
The Apache Maven team is pleased to announce the release of the Maven Surefire version 3.1.2. https://maven.apache.org/surefire/ Release Notes - Maven Surefire - Version 3.1.2 ** Bug * [SUREFIRE-2163] - customBundle properly not subject to basedir alignment * [SUREFIRE-2165] - TestSuiteXmlParser does not capture text per element causing concatenated text produced * [SUREFIRE-2169] - Potential NPE in WrappedReportEntry when #getElapsed() is called * [SUREFIRE-2176] - Invalid formatting of time attribute ** Improvement * [SUREFIRE-1533] - surefire-test-report.xsd has too narrow a definition for testcase time attribute * [SUREFIRE-2164] - Simplify serialization of elapsed time in StatelessXmlReporter * [SUREFIRE-2166] - Use ChoiceFormat to selectively render percentage and elapsed time in SurefireReportRenderer * [SUREFIRE-2167] - Simplify deserialization of elapsed time in TestSuiteXmlParser * [SUREFIRE-2168] - Use proper en dash approximation for console report output * [SUREFIRE-2170] - Use ChoiceFormat to selectively render elapsed time in WrappedReportEntry * [SUREFIRE-2173] - Update compiler source/target in integration tests to version 8 ** Task * [SUREFIRE-2174] - Remove legacy Surefire test report schema file and make 3.0 default * [SUREFIRE-2175] - Turn time attribute to xs:float in Surefire test report schema ** Dependency upgrade * [SUREFIRE-2157] - Upgrade JUnit 5 to 5.9.3 (or 5.10.x..) * [SUREFIRE-2171] - Upgrade to Maven Surefire 3.1.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Project Info Reports Plugin 3.4.5 released
The Apache Maven team is pleased to announce the release of the Maven Project Info Reports Plugin version 3.4.5. https://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-project-info-reports-plugin 3.4.5 Release Notes - Maven Project Info Reports Plugin - Version 3.4.5 ** Bug * [MPIR-441] - Fix DependenciesReportTest * [MPIR-448] - [REGRESSION] DependenciesRenderer chokes on invalid scope with a NPE ** Improvement * [MPIR-447] - Gradle deprecates compile in favor of implementation * [MPIR-449] - Don't count and display debug information if dependency does not contain class files Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Release Maven Dependency Plugin 3.6.0 released
The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.6.0. https://maven.apache.org/plugins/maven-dependency-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-dependency-plugin 3.6.0 Release Notes - Maven Dependency Plugin - Version 3.6.0 ** Bug * [MDEP-630] - error dependency:list (caused by postgresql dependency) * [MDEP-842] - :list-classes does not skip if skip is set * [MDEP-843] - :list-classes does not use GAV parameters ** Improvement * [MDEP-853] - list-repositories - improvements * [MDEP-862] - warns about depending on plexus-container-default * [MDEP-864] - Replace AnalyzeReportView with a new AnalyzeReportRenderer ** Task * [MDEP-849] - Replace Maven shared StringUtils with Commons Lang3 * [MDEP-855] - Remove unused and ignored parameter - useJvmChmod * [MDEP-857] - Remove custom plexus configuration * [MDEP-859] - Code refactor - UnpackUtil * [MDEP-866] - Refresh download page ** Dependency upgrade * [MDEP-848] - Dependency Analysis does not work under Java 20 * [MDEP-850] - Upgrade Parent to 39 * [MDEP-851] - Bump plexus-archiver from 4.6.2 to 4.7.1 * [MDEP-854] - Bump jsoup from 1.15.3 to 1.16.1 * [MDEP-856] - Upgrade commons-text to 1.10.0 * [MDEP-860] - Bump maven-dependency-analyzer from 1.13.1 to 1.13.2 * [MDEP-867] - Upgrade plugins in ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Checkstyle Plugin 3.3.0 released
The Apache Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 3.3.0. https://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins >maven-checkstyle-plugin 3.3.0 Release Notes - Maven Checkstyle Plugin - Version 3.3.0 The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.6.0. https://maven.apache.org/plugins/maven-dependency-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-dependency-plugin 3.6.0 Release Notes - Maven Dependency Plugin - Version 3.6.0 ** Improvement * [MCHECKSTYLE-436] - Replace CheckstyleReportGenerator with a new CheckstyleReportRenderer ** Task * [MCHECKSTYLE-435] - Remove deprecated RSS feature ** Dependency upgrade * [MCHECKSTYLE-428] - Upgrade parent POM to version 39 * [MCHECKSTYLE-434] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Plugin Tools 3.9.0 released
The Apache Maven team is pleased to announce the release of the Apache Maven Plugin Tools, version 3.9.0. https://maven.apache.org/plugin-tools/ Release Notes - Maven Plugin Tools - Version 3.9.0 ** Bug * [MPLUGIN-470] - *-mojo.xml (in PluginXdocGenerator) is overwritten when multiple locales are defined * [MPLUGIN-471] - Generated table by PluginXdocGenerator does not contain default attributes ** Improvement * [MPLUGIN-469] - Omit empty line in generated help goal output if plugin description is empty * [MPLUGIN-472] - Use Plexus I18N rather than fiddling with resource bundles directly ** Task * [MPLUGIN-467] - Remove reporting from maven-plugin-plugin ** Dependency upgrade * [MPLUGIN-468] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven PMD Plugin 3.21.0 released
The Apache Maven team is pleased to announce the release of the Maven PMD Plugin version 3.21.0. https://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.21.0 Release Notes - Maven PMD Plugin - Version 3.21.0 ** Bug * [MPMD-369] - System encoding conflicts with XML encoding in CpdViolationCheckMojo * [MPMD-373] - System property java.version is overwritten in ITs as model property ** New Feature * [MPMD-365] - Support Java 20 ** Improvement * [MPMD-375] - Replace *ReportGenerators with new *ReportRenderers ** Task * [MPMD-374] - Remove deprecated and unused PmdCollectingRenderer ** Dependency upgrade * [MPMD-364] - Upgrade to PMD 6.55.0 * [MPMD-372] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Surefire 3.1.0 released
The Apache Maven team is pleased to announce the release of the Maven Surefire version 3.1.0. https://maven.apache.org/surefire/ Release Notes - Maven Surefire - Version 3.1.0 ** Sub-task * [SUREFIRE-2162] - Document upcoming mojo and file names change ** Bug * [SUREFIRE-2140] - Cannot release Surefire on Windows ** Improvement * [SUREFIRE-2153] - Replace SurefireReportGenerator with a new SurefireReportRenderer * [SUREFIRE-2160] - Replace LocalizedProperties with (Custom)I18N approach from MPIR ** Task * [SUREFIRE-2130] - Rewrite several test classes in report plugin for upcoming Doxia 2.0.0 stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M8. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M8 ** Bug * [MSITE-951] - Don't abuse report's symbolic output name as filename * [MSITE-952] - MultiPageSinkFactory does not strip output name for extension * [MSITE-959] - Incorrect assumption of default locale ** New Feature * [MSITE-953] - Log statistics about rendered non-Doxia documents * [MSITE-954] - Introduce SitePluginReportDocumentRenderer marker interface ** Improvement * [MSITE-873] - Mark SiteMojo and SiteJarMojo thread-safe * [MSITE-949] - Properly populate DocumentRenderingContext#generator for ReportDocumentRenderer * [MSITE-955] - Improve DoxiaFilter document source log message * [MSITE-956] - Pass a sub mojo execution to CategorySummaryDocumentRenderer * [MSITE-957] - Print generation log message in CategorySummaryDocumentRenderer like in ReportDocumentRenderer * [MSITE-958] - Rewrite sitemap generator to a rendender ** Dependency upgrade * [MSITE-950] - Upgrade to Doxia Sitetools to 2.0.0-M8, Maven Reporting API 4.0.0-M6, Maven Reporting Impl/Exec 4.0.0-M7 * [MSITE-962] - Upgrade to Doxia Sitetools to 2.0.0-M10, Maven Reporting Impl/Exec 4.0.0-M8, Maven Fluido Skin 2.0.0-M6 Please also note for this new major version: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia Sitetools 2.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M10 Doxia Sitetools is an extension of base Doxia component that generates text markup, consisting of decoration and content that was generated by Doxia. https://maven.apache.org/doxia/doxia-sitetools/ You can download the appropriate sources etc. from the download page: https://maven.apache.org/doxia/doxia-sitetools/download.cgi Release Notes - Maven Doxia Sitetools - Version 2.0.0-M10 ** Bug * [DOXIASITETOOLS-305] - Removal of 0-byte site descriptors from the local repo does not put remote repos into consideration ** Task * [DOXIASITETOOLS-306] - Clean up and simplify thrown exceptions ** Dependency upgrade * [DOXIASITETOOLS-307] - Upgrade to Maven Fluido Skin 2.0.0-M6 in default site descriptor Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Fluido Skin 2.0.0-M6 released
The Apache Maven team is pleased to announce the release of the Maven Fluido Skin, version 2.0.0-M6. https://maven.apache.org/skins/maven-fluido-skin/ You should specify the version in your project's site configuration: org.apache.maven.skins maven-fluido-skin 2.0.0-M6 Import: This release requires Maven Site Plugin 4.0.0-M6/Doxia Sitetools 2.0.0-M6 to run Release Notes - Maven Fluido Skin - Version 2.0.0-M6 ** Bug * [MSKINS-222] - Template does not properly escape reserved XML chars * [MSKINS-224] - Ampersand gets un-escaped in menu item ** Dependency upgrade * [MSKINS-216] - Fix issue with missing dependency to plexus-utils in minify-maven-plugin and Maven 3.9.x * [MSKINS-225] - Upgrade to Doxia Sitetools 2.0.0-M7 * [MSKINS-227] - Upgrade to AnchorJS 4.3.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 2.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M8. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M8 ** Dependency upgrade * [MSHARED-1245] - Upgrade to Doxia Sitetools 2.0.0-M10 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M8. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M8 ** Dependency upgrade * [MSHARED-1246] - Upgrade components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Checkstyle Plugin 3.2.2 released
The Apache Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 3.2.2. https://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins >maven-checkstyle-plugin 3.2.2 Release Notes - Maven Checkstyle Plugin - Version 3.2.2 ** Bug * [MCHECKSTYLE-432] - Inline configuration does not work when creating site reports with multiple locales ** Improvement * [MCHECKSTYLE-426] - Don't use Sink#figure()/Sink#figureCaption() since it distorts the output ** Dependency upgrade * [MCHECKSTYLE-427] - Upgrade m-invoker-plugin to 3.5.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: MavenCLI failing in Jenkins
On 2023/04/20 14:15:37 Javier Ortiz Bultron wrote: > So this is not official? It certainly looks that way. > > https://hub.docker.com/_/maven ...and this is exactly the problem. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: MavenCLI failing in Jenkins
On 2023/04/19 21:42:20 Javier Ortiz Bultron wrote: > Code works perfectly on my Mac but not on Jenkins. I'm running this on the > Maven official image: maven:3.9.1-eclipse-temurin-11 This is NOT official! Gosh, how I hate what Docker Hub does. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M7. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M7 ** Improvement * [MSHARED-1232] - Properly populate DocumentRenderingContext#generator when run in standalone mode ** Dependency upgrade * [MSHARED-1233] - Upgrade to Doxia Sitetools 2.0.0-M8 * [MSHARED-1234] - Upgrade to Maven Reporting API 4.0.0-M6 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M7. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M7 ** Improvement * [MSHARED-1236] - Supply execution id of caller (Maven Site Plugin) to MavenReportExecutorRequest ** Dependency upgrade * [MSHARED-1235] - Upgrade to Maven Reporting API 4.0.0-M6 * [MSHARED-1241] - Upgrade plugins and components in ITs * [MSHARED-1242] - Upgrade to Doxia Sitetools 2.0.0-M8 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Doxia Sitetools 2.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 2.0.0-M8 Doxia Sitetools is an extension of base Doxia component that generates text markup, consisting of decoration and content that was generated by Doxia. https://maven.apache.org/doxia/doxia-sitetools/ You can download the appropriate sources etc. from the download page: https://maven.apache.org/doxia/doxia-sitetools/download.cgi Release Notes - Maven Doxia Sitetools - Version 2.0.0-M8 ** Improvement * [DOXIASITETOOLS-301] - Automatically remove the 0-byte site descriptors from the local repo * [DOXIASITETOOLS-302] - Harmonize path separator in DocumentRenderingContext ** Task * [DOXIASITETOOLS-303] - Implement workaround for MNG-7758/MRESOLVER-335 ** Dependency upgrade * [DOXIASITETOOLS-304] - Upgrade to Maven Reporting API 4.0.0-M6 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Project Info Reports Plugin 3.4.3 released
The Apache Maven team is pleased to announce the release of the Maven Project Info Reports Plugin version 3.4.3. https://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-project-info-reports-plugin 3.4.3 Release Notes - Maven Project Info Reports Plugin - Version 3.4.3 ** Bug * [MPIR-429] - avoid warning on "Unknown packaging: bundle" ** Dependency upgrade * [MPIR-432] - Upgrade parent pom to 39 * [MPIR-433] - Bump bcel from 6.5.0 to 6.6.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M6 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M6. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M6 ** Task * [MSHARED-1231] - Remove unused default-report.xml file Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven
Site Plugin, version 4.0.0-M7.
https://maven.apache.org/plugins/maven-site-plugin/
Release Notes - Maven Site Plugin - Version 4.0.0-M7
** Bug
* [MSITE-226] - Missing escaping of ${project.name} for default
site descriptor
* [MSITE-934] - Log output of site:run does not show locale
* [MSITE-937] - Sitemap creates non-consecutive headings
* [MSITE-938] - Sitemap creates empty entry if href is null
although menu item name isn't
* [MSITE-941] - sitemap.xml is overwritten when multiple locales
are defined
* [MSITE-942] - Generated localized site content is ignored
* [MSITE-943] - Saved processed site content is overwritten when
multiple locales are defined
* [MSITE-944] - Site plugin fails if there's a & in the project
POM
** Task
* [MSITE-932] - Remove Maven 2 style reports element
* [MSITE-936] - Sort locale tests from non-default to default one
* [MSITE-939] - Replace StringUtils from Plexus Utils with Commons Lang
** Dependency upgrade
* [MSITE-935] - Upgrade to Doxia Sitetools 2.0.0-M7, Maven
Reporting Impl 4.0.0-M6, Maven Reporting Exec 2.0.0-M6
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M6 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M6. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M6 ** Dependency upgrade * [MSHARED-1222] - Upgrade to Doxia Sitetools 2.0.0-M7 * [MSHARED-1223] - Upgrade to Maven Reporting Impl 4.0.0-M6 in ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M6 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M6. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M6 ** Dependency upgrade * [MSHARED-1221] - Upgrade to Doxia Sitetools 2.0.0-M7 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
