This is an automated email from the ASF dual-hosted git repository.
mbuenger pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 1fe09f5f Fix class declaration syntax in common-bugs.md (#1476)
1fe09f5f is described below
commit 1fe09f5fc32808e2b7d050a5b4bedba9c95a9fff
Author: Mahied Maruf <[email protected]>
AuthorDate: Thu Dec 4 19:17:55 2025 +0000
Fix class declaration syntax in common-bugs.md (#1476)
Fixes: #1475
Signed-off-by: Mahied Mauf <[email protected]>
---
content/markdown/plugin-developers/common-bugs.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/markdown/plugin-developers/common-bugs.md
b/content/markdown/plugin-developers/common-bugs.md
index 02a50d3c..2abd57ef 100644
--- a/content/markdown/plugin-developers/common-bugs.md
+++ b/content/markdown/plugin-developers/common-bugs.md
@@ -153,7 +153,7 @@ Reporting plugins that suffer from this bug can easily be
detected by executing
Maven's command line supports the definition of system properties via
arguments of the form `-D key=value`. While these properties are called system
properties, plugins should never use
[`System.getProperty()`](http://java.sun.com/javase/6/docs/api/java/lang/System.html#getProperty(java.lang.String))
and related methods to query these properties. For example, the following code
snippet will not work reliably when Maven is embedded, say into an IDE or a CI
server:
```unknown
-public MyMojo extends AbstractMojo
+public class MyMojo extends AbstractMojo
{
public void execute()
{
@@ -172,7 +172,7 @@ The problem is that the properties managed by the `System`
class are global, i.e
People occasionally employ shutdown hooks to perform cleanup tasks, e.g. to
delete temporary files as shown in the example below:
```unknown
-public MyMojo extends AbstractMojo
+public class MyMojo extends AbstractMojo
{
public void execute()
{
@@ -213,7 +213,7 @@ At first glance, one might be tempted to argue that the
project base directory i
Hence this example code is prone to misbehave:
```unknown
-public MyMojo extends AbstractMojo
+public class MyMojo extends AbstractMojo
{
/**
* @parameter
@@ -250,7 +250,7 @@ Most reporting plugins inherit from `AbstractMavenReport`.
In doing so, they nee
Now, some plugins need to create additional files in the report output
directory that accompany the report generated via the sink interface. While it
is tempting to use either the method `getOutputDirectory()` or the field
`outputDirectory` directly in order to setup a path for the output files, this
leads most likely to a bug. More precisely, those plugins will not properly
output files when run by the Maven Site Plugin as part of the site lifecycle.
This is best noticed when the output [...]
```unknown
-public MyReportMojo extends AbstractMavenReport
+public class MyReportMojo extends AbstractMavenReport
{
/**
* @parameter default-value="${project.reporting.outputDirectory}"
