AppleOutlookDAVConfig.exe causing CPU fan running like...

AppleOutlookDAVConfig.exe causing high processing, fan keep working like freaking noise....

kill it in task manager by End Process Tree.

Guest what I found: java generate pojo from json

java generate pojo from json


http://www.jsonschema2pojo.org

relevant info:
https://stackoverflow.com/questions/1957406/generate-java-class-from-json

Maven: java.lang.NoClassDefFoundError: org/apache/maven/doxia/siterenderer/DocumentContent

tried is working


<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.1</version>
<configuration>
<!-- http://maven.apache.org/plugins/maven-compiler-plugin/ -->
<source>${version.jdk}</source>
<target>${version.jdk}</target>
</configuration>
</plugin>

<!-- https://www.mkyong.com/maven/mvn-site-java-lang-classnotfoundexception-org-apache-maven-doxia-siterenderer-documentcontent/ -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-site-plugin</artifactId>
                <version>3.7.1</version>
            </plugin>

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-project-info-reports-plugin</artifactId>
                <version>3.0.0</version>
            </plugin>
<!-- https://www.mkyong.com/maven/mvn-site-java-lang-classnotfoundexception-org-apache-maven-doxia-siterenderer-documentcontent/ -->
           
</plugins>
</build>

Maven: Project Inheritance vs Project Aggregation

Reference URL: https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance_vs_Project_Aggregation

Project Inheritance vs Project Aggregation

If you have several Maven projects, and they all have similar configurations, you can refactor your projects by pulling out those similar configurations and making a parent project. Thus, all you have to do is to let your Maven projects inherit that parent project, and those configurations would then be applied to all of them.

And if you have a group of projects that are built or processed together, you can create a parent project and have that parent project declare those projects as its modules. By doing so, you'd only have to build the parent and the rest will follow.

But of course, you can have both Project Inheritance and Project Aggregation. Meaning, you can have your modules specify a parent project, and at the same time, have that parent project specify those Maven projects as its modules. You'd just have to apply all three rules:

• Specify in every child POM who their parent POM is.
• Change the parent POMs packaging to the value "pom" .
• Specify in the parent POM the directories of its modules (children POMs)

Maven BOM file.

I was confused by this Maven BOM file & Maven POM file...

you won't find bom.xml trust me...

Look for more info to reference URL:
illustrates how a "bill of materials" (BOM) can be created for use by other projects



We could implement and get benefits with 2 ways:

1. Inherit
2. or import.

As mentioned by baeldung.com:

We can also import the BOM.

In larger projects, the approach of inheritance is not efficient because the project can inherit only a single parent. Importing is the alternative as we can import as many BOMs as we need.